Public report of github/CopilotForXcode, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 21:41 UTC · Survey ID cd_9e2704b34c644932a042300eec48148f
github/CopilotForXcode
Measured 14 November 2026, 21:39 UTC, at code version 258d457
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Up 2 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 73,217 lines of product code in 62 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Production Readiness, 46
Findings by how serious they are
9 critical487 serious67 minor
21 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 21:39 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
57of 57 dimensions measured by tools.
497of 563 findings point to an exact file and line, so you can open each one in the code. The other 66 concern the repository as a whole, such as missing documentation.
57dimensions across 8 lenses, read from 73,217 lines of product code in 62 projects.
github/CopilotForXcode falls short of our standard for a preview release, in part because we found no logging, tracing or health checks in the code. It scores 55 out of 100 and is rated Adequate, and five of its nine critical findings are security problems in the packages it uses.
Production Readiness, at 46, is the weakest lens and counts most in the score. The best first step is making the tests check their results, worth about 5 points. Adding a diagnostic log would lift Production Readiness itself, also worth about 5. Raising Production Readiness to 62 would lift the score to about 59.
Five known security holes in the packages the code depends on can be used by attackers. Updating the vulnerable packages would close this risk. The two pages that don't say their language need their language set.
The product code is 73,217 lines, about €78,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 46 to 62, the lowest score rated Strong, the score would rise from 55 to about 59.
Code composition: what the lines of code are
Product code 93%Tests 7%
New since the last survey: 128 findings
These 128 critical or serious findings weren't in the previous survey, on 28 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Code Duplication · Edited copy of a member (57 corresponding lines) Core/Sources/Service/XPCService.swift
Code Duplication · Edited copy of a member (42 corresponding lines) Tool/Sources/SuggestionBasic/Modification.swift
Code Duplication · Edited copy of a member (45 corresponding lines) Core/Sources/ConversationTab/Chat.swift
Code Duplication · Edited copy of a member (23 corresponding lines) Core/Sources/SuggestionWidget/ChatWindow/ChatHistoryView.swift
Code Duplication · Edited copy of a member (41 corresponding lines) Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift
Code Duplication · Edited copy of a member (42 corresponding lines) Core/Sources/SuggestionWidget/ChatWindow/ChatNoAXPermissionView.swift
Code Duplication · Edited copy of a member (34 corresponding lines) Core/Sources/Service/SuggestionCommandHandler/WindowBaseCommandHandler.swift
Code Duplication · Edited copy of a member (21 corresponding lines) Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift
Code Duplication · Edited copy of a member (35 corresponding lines) Tool/Sources/ConversationServiceProvider/ConversationServiceProvider.swift
Code Duplication · Edited copy of a member (16 corresponding lines) Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift
Code Duplication · Edited copy of a member (26 corresponding lines) Tool/Sources/XPCShared/XPCExtensionService.swift
Code Duplication · Edited copy of a member (40 corresponding lines) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift
Code Duplication · Edited copy of a member (39 corresponding lines) Core/Sources/HostApp/AdvancedSettings/ChatSection.swift
Code Duplication · Edited copy of a member (24 corresponding lines) Core/Sources/HostApp/ToolsSettings/BuiltInToolsListView.swift
Code Duplication · Edited copy of a member (20 corresponding lines) Core/Sources/Service/XPCService.swift
Code Duplication · Edited copy of a member (28 corresponding lines) Core/Sources/HostApp/CopilotPolicyManager.swift
Code Duplication · Edited copy of a member (27 corresponding lines) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift
Code Duplication · Edited copy of a member (30 corresponding lines) Core/Sources/SuggestionWidget/AgentConfigurationWidgetView.swift
Code Duplication · Edited copy of a member (22 corresponding lines) Tool/Sources/GitHubCopilotService/Services/GitHubCopilotConversationService.swift
Code Duplication · Edited copy of a member (26 corresponding lines) Core/Sources/HostApp/ToolsSettings/ToolRowView.swift
Code Duplication · Edited copy of a member (20 corresponding lines) Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift
Code Duplication · Edited copies of one member (6 members, 20+ corresponding lines) Core/Sources/Service/XPCService.swift
Code Duplication · Edited copy of a member (17 corresponding lines) Core/Sources/Service/GUI/GraphicalUserInterfaceController.swift
Code Duplication · Edited copy of a member (22 corresponding lines) Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift
Code Duplication · Edited copy of a member (12 corresponding lines) Tool/Sources/Preferences/Types/AutoApprovedMCPServers.swift
Code Duplication · Edited copy of a member (23 corresponding lines) Core/Sources/ConversationTab/TerminalViews/RunInTerminalToolView.swift
Code Duplication · Edited copy of a member (16 corresponding lines) Tool/Sources/StatusBarItemView/QuotaView.swift
Code Duplication · Edited copies of one member (5 members, 24+ corresponding lines) Tool/Sources/XPCShared/XPCExtensionService.swift
Code Duplication · Edited copy of a member (23 corresponding lines) Tool/Sources/TelemetryService/TelemetryService.swift
Code Duplication · Edited copy of a member (17 corresponding lines) Core/Sources/ConversationTab/ModeAndModelPicker/ModePicker/AgentModeButton.swift
Code Duplication · Edited copy of a member (23 corresponding lines) Core/Sources/SuggestionWidget/Extensions/WidgetWindowsController+FixErrorPanel.swift
Code Duplication · Edited copy of a member (24 corresponding lines) Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift
Code Duplication · Edited copy of a member (22 corresponding lines) Core/Sources/ConversationTab/ModeAndModelPicker/ModePicker/AgentModeMenu.swift
Code Duplication · Edited copy of a member (13 corresponding lines) Tool/Sources/ConversationServiceProvider/LSPTypes+AgentRound.swift
Code Duplication · Edited copy of a member (21 corresponding lines) Core/Sources/SuggestionService/SuggestionService.swift
Code Duplication · Edited copy of a member (13 corresponding lines) Core/Sources/Service/XPCService.swift
Code Duplication · Edited copy of a member (18 corresponding lines) Core/Sources/KeyBindingManager/TabToAcceptSuggestion.swift
Code Duplication · Edited copy of a member (12 corresponding lines) Tool/Sources/ConversationServiceProvider/LSPTypes+AgentRound.swift
Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) EditorExtension/AcceptNESSuggestionCommand.swift
Code Duplication · Edited copy of a member (13 corresponding lines) Tool/Sources/Workspace/FileChangeWatcher/FileChangeWatcherService.swift
Code Duplication · Edited copy of a member (14 corresponding lines) Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift
Code Duplication · Edited copy of a member (15 corresponding lines) Tool/Sources/SharedUIComponents/DownvoteButton.swift
Code Duplication · Edited copies of one member (5 members, 24+ corresponding lines) Tool/Sources/XPCShared/XPCExtensionService.swift
Code Duplication · Edited copy of a member (9 corresponding lines) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift
Code Duplication · Edited copy of a member (24 corresponding lines) Tool/Sources/XPCShared/XPCExtensionService.swift
Code Duplication · Edited copy of a member (17 corresponding lines) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift
Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift
Code Duplication · Edited copy of a member (12 corresponding lines) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift
Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) Tool/Sources/GitHubCopilotService/Conversation/ShowMessageRequestHandler.swift
Code Duplication · Edited copy of a member (14 corresponding lines) Tool/Sources/XcodeInspector/SourceEditor.swift
Code Duplication · Edited copy of a member (12 corresponding lines) Core/Sources/ChatService/ToolCalls/AutoApproval/MCPApprovalStorage.swift
Code Duplication · Edited copy of a member (13 corresponding lines) Core/Sources/SuggestionWidget/NES/NESDiffView.swift
Code Duplication · Edited copy of a member (22 corresponding lines) Tool/Sources/Workspace/WorkspaceDirectoryIndex.swift
Code Duplication · Edited copy of a member (19 corresponding lines) Tool/Sources/SharedUIComponents/CustomTextEditor.swift
Code Duplication · Edited copy of a member (14 corresponding lines) Core/Sources/SuggestionWidget/NES/NESMenu/NESMenuController.swift
Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) Tool/Sources/Persist/AppState.swift
Code Duplication · Edited copy of a member (7 corresponding lines) Tool/Sources/Persist/ConfigPathUtils.swift
Code Duplication · Edited copy of a member (11 corresponding lines) Tool/Sources/StatusBarItemView/QuotaView.swift
Code Duplication · Edited copies of one member (6 members, 19+ corresponding lines) Tool/Sources/XPCShared/XPCExtensionService.swift
Code Duplication · Edited copy of a member (18 corresponding lines) Core/Sources/ConversationTab/DiffViews/DiffWebView.swift
Code Duplication · Edited copy of a member (10 corresponding lines) Tool/Sources/ConversationServiceProvider/ConversationServiceProvider.swift
Code Duplication · Edited copy of a member (9 corresponding lines) Tool/Sources/Workspace/OpenedFileRocoverableStorage.swift
Code Duplication · Edited copy of a member (13 corresponding lines) Core/Sources/ChatService/ToolCalls/AutoApproval/MCPApprovalStorage.swift
Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift
Code Duplication · Edited copy of a member (15 corresponding lines) Tool/Sources/SuggestionProvider/PostProcessingSuggestionServiceMiddleware.swift
Code Duplication · Edited copy of a member (9 corresponding lines) Core/Sources/ChatService/ToolCalls/AutoApproval/SensitiveFileApprovalStorage.swift
Code Duplication · Edited copy of a member (12 corresponding lines) ExtensionService/AppDelegate+Menu.swift
Code Duplication · Edited copy of a member (11 corresponding lines) Tool/Sources/ChatTab/ChatTab.swift
Code Duplication · Edited copies of one member (4 members, 14+ corresponding lines) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift
Code Duplication · Edited copy of a member (11 corresponding lines) Core/Sources/SuggestionWidget/NES/NESDiffView.swift
Code Duplication · Edited copy of a member (12 corresponding lines) Tool/Sources/BuiltinExtension/BuiltinExtensionSuggestionServiceProvider.swift
Code Duplication · Edited copy of a member (9 corresponding lines) Tool/Sources/StatusBarItemView/AccountItemView.swift
Code Duplication · Edited copy of a member (12 corresponding lines) Core/Sources/ConversationTab/Chat.swift
Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) Tool/Sources/ChatTab/ChatTab.swift
Code Duplication · Edited copy of a member (11 corresponding lines) Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift
Code Duplication · Edited copies of one member (5 members, 11+ corresponding lines) Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift
Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) Core/Sources/ConversationTab/ChatPanel.swift
Code Duplication · Edited copy of a member (5 corresponding lines) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ConversationAgentProgressView.swift
Code Duplication · Edited copy of a member (16 corresponding lines) Core/Sources/HostApp/ToolsSettings/CopilotBuiltInToolManagerObservable.swift
Code Duplication · Edited copies of one member (4 members, 10+ corresponding lines) Core/Sources/Service/SuggestionCommandHandler/WindowBaseCommandHandler.swift
Code Duplication · Edited copy of a member (11 corresponding lines) Tool/Sources/GitHubCopilotService/GitHubCopilotExtension.swift
Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift
Code Duplication · Edited copy of a member (17 corresponding lines) Core/Sources/HostApp/ToolsSettings/AutoApprove/AutoApprovalDisableView.swift
Code Duplication · Edited copy of a member (6 corresponding lines) Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift
Code Duplication · Edited copy of a member (16 corresponding lines) Tool/Sources/Logger/Logger.swift
Code Duplication · Edited copy of a member (9 corresponding lines) Tool/Sources/Persist/Storage/ConversationStorage/Model.swift
Code Duplication · Edited copy of a member (10 corresponding lines) Tool/Sources/GitHubCopilotService/LanguageServer/CustomJSONRPCServerConnection.swift
Code Duplication · Edited copy of a member (6 corresponding lines) Tool/Sources/GitHubCopilotService/Services/GitHubCopilotConversationService.swift
Code Duplication · Edited copy of a member (12 corresponding lines) Tool/Sources/Persist/Storage/ConversationStorageService.swift
Code Duplication · Edited copy of a member (11 corresponding lines) Tool/Sources/WorkspaceSuggestionService/SuggestionWorkspacePlugin.swift
Code Duplication · Edited copy of a member (9 corresponding lines) Core/Sources/ConversationTab/ChatContextMenu.swift
Code Duplication · Edited copy of a member (5 corresponding lines) Core/Sources/ConversationTab/TerminalViews/RunInTerminalToolView.swift
Code Duplication · Edited copy of a member (8 corresponding lines) Core/Sources/HostApp/SharedComponents/Badge.swift
Code Duplication · Edited copy of a member (11 corresponding lines) Core/Sources/SuggestionWidget/AgentConfigurationWidgetView.swift
Code Duplication · Edited copy of a member (8 corresponding lines) Tool/Sources/AXExtension/AXUIElement.swift
Code Duplication · Edited copy of a member (13 corresponding lines) Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPRegistryURLInputField.swift
Code Duplication · Edited copies of one member (8 members, 11+ corresponding lines) Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift
Code Duplication · Edited copy of a member (16 corresponding lines) EditorExtension/OpenChat.swift
Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) Tool/Sources/Preferences/UserDefaults.swift
Code Duplication · Edited copy of a member (12 corresponding lines) Core/Sources/ConversationTab/ModeAndModelPicker/ModePicker/AgentModeButtonMenuItem.swift
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 22 findings
These 22 critical or serious findings were in the previous survey, on 28 October 2026, and are gone from this one.
Code Duplication · Members sharing a duplicated core (10 members, 50+ identical tokens) Core/Sources/ConversationTab/Chat.swift
A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €78,000 · Estimate
Cost to rebuild
€26,000 to €130,000, for 431 to 1,369 hours of work, about 0.5 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.8 at a score of 55. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 73,217 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with SwiftFocusedCodeFinderTests.swift.
Raises the score by about 5 points · Low effort · Test Quality
2
Resolve the 9 Floating branch dependency finding(s) in Dependency Hygiene.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj.
Raises the score by about 3 points · Low effort · ADR Quality
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €78,000 to build again, about 0.5 person-years of work. Its weakest lens is Production Readiness, at 46 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No assertions (empty test) finding(s) in Test Quality. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for low effort, because it clears the 1 Test Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.6 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 3% to 8% on every change. The history of the code shows how much it changes: about 362 lines over the last 90 days, which is about 1,468 lines a year. At that pace, the extra work comes to an estimated 0.1 to 0.7 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
63 modules, with 295 dependencies between them. One loop runs through 35 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 23 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
Uses a module listed above itPart of a loopThe module itself
1→22 Tool~Preferences uses Tool~FileSystempart of a loop✕
Connections
2 pairs of types, where a type in Tool~Preferences uses a type in Tool~FileSystem.
The types involved
Tool~Preferences.Digest → Tool~FileSystem.UInt8
Tool~Preferences.Double → Tool~FileSystem.Date
Direction
Tool~Preferences uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~Preferences, while a change to Tool~Preferences can't break Tool~FileSystem.
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.
1→30 Tool~Preferences uses Core~HostApppart of a loop✕
Connections
13 pairs of types, where a type in Tool~Preferences uses a type in Core~HostApp.
Tool~Preferences uses Core~HostApp, so a change to Core~HostApp can break Tool~Preferences, while a change to Tool~Preferences can't break Core~HostApp.
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.
1→35 Tool~Preferences uses Core~ConversationTabpart of a loop✕
Connections
1 pair of types, where a type in Tool~Preferences uses a type in Core~ConversationTab.
Tool~Preferences uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~Preferences, while a change to Tool~Preferences can't break Core~ConversationTab.
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.
Core~LaunchAgentManager uses Tool~Preferences, so a change to Tool~Preferences can break Core~LaunchAgentManager, while a change to Core~LaunchAgentManager can't break Tool~Preferences.
Position
Below the diagonal: Core~LaunchAgentManager uses a module listed above it, which is the healthy direction.
2→30 Core~LaunchAgentManager uses Core~HostApppart of a loop✕
Connections
3 pairs of types, where a type in Core~LaunchAgentManager uses a type in Core~HostApp.
Core~LaunchAgentManager uses Core~HostApp, so a change to Core~HostApp can break Core~LaunchAgentManager, while a change to Core~LaunchAgentManager can't break Core~HostApp.
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.
2→35 Core~LaunchAgentManager uses Core~ConversationTabpart of a loop✕
Connections
1 pair of types, where a type in Core~LaunchAgentManager uses a type in Core~ConversationTab.
Core~LaunchAgentManager uses Core~ConversationTab, so a change to Core~ConversationTab can break Core~LaunchAgentManager, while a change to Core~LaunchAgentManager can't break Core~ConversationTab.
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.
Tool~ActiveApplicationMonitor uses Tool~Preferences, so a change to Tool~Preferences can break Tool~ActiveApplicationMonitor, while a change to Tool~ActiveApplicationMonitor can't break Tool~Preferences.
Position
Below the diagonal: Tool~ActiveApplicationMonitor uses a module listed above it, which is the healthy direction.
3→9 Tool~ActiveApplicationMonitor uses repositorypart of a loop✕
Connections
2 pairs of types, where a type in Tool~ActiveApplicationMonitor uses a type in repository.
Tool~ActiveApplicationMonitor uses repository, so a change to repository can break Tool~ActiveApplicationMonitor, while a change to Tool~ActiveApplicationMonitor can't break repository.
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.
3→22 Tool~ActiveApplicationMonitor uses Tool~FileSystempart of a loop✕
Connections
1 pair of types, where a type in Tool~ActiveApplicationMonitor uses a type in Tool~FileSystem.
Tool~ActiveApplicationMonitor uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~ActiveApplicationMonitor, while a change to Tool~ActiveApplicationMonitor can't break Tool~FileSystem.
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.
3→30 Tool~ActiveApplicationMonitor uses Core~HostApppart of a loop✕
Connections
1 pair of types, where a type in Tool~ActiveApplicationMonitor uses a type in Core~HostApp.
Tool~ActiveApplicationMonitor uses Core~HostApp, so a change to Core~HostApp can break Tool~ActiveApplicationMonitor, while a change to Tool~ActiveApplicationMonitor can't break Core~HostApp.
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.
3→35 Tool~ActiveApplicationMonitor uses Core~ConversationTabpart of a loop✕
Connections
1 pair of types, where a type in Tool~ActiveApplicationMonitor uses a type in Core~ConversationTab.
Tool~ActiveApplicationMonitor uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~ActiveApplicationMonitor, while a change to Tool~ActiveApplicationMonitor can't break Core~ConversationTab.
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.
1 pair of types, where a type in Tool~GitHelper uses a type in Tool~Preferences.
The types involved
Tool~GitHelper.GitHunk → Tool~Preferences.Int
Direction
Tool~GitHelper uses Tool~Preferences, so a change to Tool~Preferences can break Tool~GitHelper, while a change to Tool~GitHelper can't break Tool~Preferences.
Position
Below the diagonal: Tool~GitHelper uses a module listed above it, which is the healthy direction.
4→30 Tool~GitHelper uses Core~HostApppart of a loop✕
Connections
7 pairs of types, where a type in Tool~GitHelper uses a type in Core~HostApp.
Tool~GitHelper uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~GitHelper, while a change to Tool~GitHelper can't break Core~ConversationTab.
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.
Tool~Status uses Tool~GitHubCopilotService, so a change to Tool~GitHubCopilotService can break Tool~Status, while a change to Tool~Status can't break Tool~GitHubCopilotService.
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 Tool~Status uses Tool~FileSystempart of a loop✕
Connections
1 pair of types, where a type in Tool~Status uses a type in Tool~FileSystem.
Tool~Toast uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~Toast, while a change to Tool~Toast can't break Core~ConversationTab.
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.
Tool~XPCShared uses Tool~Preferences, so a change to Tool~Preferences can break Tool~XPCShared, while a change to Tool~XPCShared can't break Tool~Preferences.
Position
Below the diagonal: Tool~XPCShared uses a module listed above it, which is the healthy direction.
Tool~XPCShared uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Tool~XPCShared, while a change to Tool~XPCShared can't break Tool~SuggestionBasic.
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→13 Tool~XPCShared uses Tool~ConversationServiceProviderpart of a loop✕
Connections
5 pairs of types, where a type in Tool~XPCShared uses a type in Tool~ConversationServiceProvider.
Tool~XPCShared uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Tool~XPCShared, while a change to Tool~XPCShared can't break Tool~ConversationServiceProvider.
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→21 Tool~XPCShared uses Tool~GitHubCopilotServicepart of a loop✕
Connections
17 pairs of types, where a type in Tool~XPCShared uses a type in Tool~GitHubCopilotService.
Tool~XPCShared uses Tool~GitHubCopilotService, so a change to Tool~GitHubCopilotService can break Tool~XPCShared, while a change to Tool~XPCShared can't break Tool~GitHubCopilotService.
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→30 Tool~XPCShared uses Core~HostApppart of a loop✕
Connections
14 pairs of types, where a type in Tool~XPCShared uses a type in Core~HostApp.
repository uses Tool~ActiveApplicationMonitor, so a change to Tool~ActiveApplicationMonitor can break repository, while a change to repository can't break Tool~ActiveApplicationMonitor.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
repository uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break repository, while a change to repository can't break Tool~SuggestionBasic.
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.
27 pairs of types, where a type in repository uses a type in Core~HostApp. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
repository uses Core~ConversationTab, so a change to Core~ConversationTab can break repository, while a change to repository can't break Core~ConversationTab.
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.
Tool~AXExtension uses Tool~Preferences, so a change to Tool~Preferences can break Tool~AXExtension, while a change to Tool~AXExtension can't break Tool~Preferences.
Position
Below the diagonal: Tool~AXExtension uses a module listed above it, which is the healthy direction.
Tool~AXExtension uses Core~HostApp, so a change to Core~HostApp can break Tool~AXExtension, while a change to Tool~AXExtension can't break Core~HostApp.
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→35 Tool~AXExtension uses Core~ConversationTabpart of a loop✕
Connections
1 pair of types, where a type in Tool~AXExtension uses a type in Core~ConversationTab.
Tool~AXExtension uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~AXExtension, while a change to Tool~AXExtension can't break Core~ConversationTab.
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.
Tool~SuggestionBasic uses Tool~Preferences, so a change to Tool~Preferences can break Tool~SuggestionBasic, while a change to Tool~SuggestionBasic can't break Tool~Preferences.
Position
Below the diagonal: Tool~SuggestionBasic uses a module listed above it, which is the healthy direction.
Tool~SuggestionBasic uses Tool~AXExtension, so a change to Tool~AXExtension can break Tool~SuggestionBasic, while a change to Tool~SuggestionBasic can't break Tool~AXExtension.
Position
Below the diagonal: Tool~SuggestionBasic uses a module listed above it, which is the healthy direction.
11→30 Tool~SuggestionBasic uses Core~HostApppart of a loop✕
Connections
9 pairs of types, where a type in Tool~SuggestionBasic uses a type in Core~HostApp.
Tool~SuggestionBasic uses Core~HostApp, so a change to Core~HostApp can break Tool~SuggestionBasic, while a change to Tool~SuggestionBasic can't break Core~HostApp.
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→35 Tool~SuggestionBasic uses Core~ConversationTabpart of a loop✕
Connections
3 pairs of types, where a type in Tool~SuggestionBasic uses a type in Core~ConversationTab.
Tool~SuggestionBasic uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~SuggestionBasic, while a change to Tool~SuggestionBasic can't break Core~ConversationTab.
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.
Core~PromptToCodeService uses Tool~Preferences, so a change to Tool~Preferences can break Core~PromptToCodeService, while a change to Core~PromptToCodeService can't break Tool~Preferences.
Position
Below the diagonal: Core~PromptToCodeService uses a module listed above it, which is the healthy direction.
Core~PromptToCodeService uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Core~PromptToCodeService, while a change to Core~PromptToCodeService can't break Tool~SuggestionBasic.
Position
Below the diagonal: Core~PromptToCodeService uses a module listed above it, which is the healthy direction.
12→30 Core~PromptToCodeService uses Core~HostApppart of a loop✕
Connections
4 pairs of types, where a type in Core~PromptToCodeService uses a type in Core~HostApp.
Core~PromptToCodeService uses Core~HostApp, so a change to Core~HostApp can break Core~PromptToCodeService, while a change to Core~PromptToCodeService can't break Core~HostApp.
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→35 Core~PromptToCodeService uses Core~ConversationTabpart of a loop✕
Connections
1 pair of types, where a type in Core~PromptToCodeService uses a type in Core~ConversationTab.
Core~PromptToCodeService uses Core~ConversationTab, so a change to Core~ConversationTab can break Core~PromptToCodeService, while a change to Core~PromptToCodeService can't break Core~ConversationTab.
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.
36 pairs of types, where a type in Tool~ConversationServiceProvider uses a type in Tool~Preferences. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Tool~ConversationServiceProvider uses Tool~Preferences, so a change to Tool~Preferences can break Tool~ConversationServiceProvider, while a change to Tool~ConversationServiceProvider can't break Tool~Preferences.
Position
Below the diagonal: Tool~ConversationServiceProvider uses a module listed above it, which is the healthy direction.
Tool~ConversationServiceProvider uses Tool~GitHelper, so a change to Tool~GitHelper can break Tool~ConversationServiceProvider, while a change to Tool~ConversationServiceProvider can't break Tool~GitHelper.
Position
Below the diagonal: Tool~ConversationServiceProvider uses a module listed above it, which is the healthy direction.
Tool~ConversationServiceProvider uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Tool~ConversationServiceProvider, while a change to Tool~ConversationServiceProvider can't break Tool~SuggestionBasic.
Position
Below the diagonal: Tool~ConversationServiceProvider uses a module listed above it, which is the healthy direction.
13→30 Tool~ConversationServiceProvider uses Core~HostApppart of a loop✕
Connections
82 pairs of types, where a type in Tool~ConversationServiceProvider uses a type in Core~HostApp. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Tool~ConversationServiceProvider uses Core~HostApp, so a change to Core~HostApp can break Tool~ConversationServiceProvider, while a change to Tool~ConversationServiceProvider can't break Core~HostApp.
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→35 Tool~ConversationServiceProvider uses Core~ConversationTabpart of a loop✕
Connections
9 pairs of types, where a type in Tool~ConversationServiceProvider uses a type in Core~ConversationTab.
Tool~ConversationServiceProvider uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~ConversationServiceProvider, while a change to Tool~ConversationServiceProvider can't break Core~ConversationTab.
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.
Tool~Persist uses Tool~Preferences, so a change to Tool~Preferences can break Tool~Persist, while a change to Tool~Persist can't break Tool~Preferences.
Position
Below the diagonal: Tool~Persist uses a module listed above it, which is the healthy direction.
Tool~Persist uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Tool~Persist, while a change to Tool~Persist can't break Tool~ConversationServiceProvider.
Position
Below the diagonal: Tool~Persist uses a module listed above it, which is the healthy direction.
14→22 Tool~Persist uses Tool~FileSystempart of a loop✕
Connections
3 pairs of types, where a type in Tool~Persist uses a type in Tool~FileSystem.
Tool~Persist uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~Persist, while a change to Tool~Persist can't break Core~ConversationTab.
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.
Tool~SuggestionProvider uses Tool~Preferences, so a change to Tool~Preferences can break Tool~SuggestionProvider, while a change to Tool~SuggestionProvider can't break Tool~Preferences.
Position
Below the diagonal: Tool~SuggestionProvider uses a module listed above it, which is the healthy direction.
Tool~SuggestionProvider uses Tool~XPCShared, so a change to Tool~XPCShared can break Tool~SuggestionProvider, while a change to Tool~SuggestionProvider can't break Tool~XPCShared.
Position
Below the diagonal: Tool~SuggestionProvider uses a module listed above it, which is the healthy direction.
Tool~SuggestionProvider uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Tool~SuggestionProvider, while a change to Tool~SuggestionProvider can't break Tool~SuggestionBasic.
Position
Below the diagonal: Tool~SuggestionProvider uses a module listed above it, which is the healthy direction.
Tool~SuggestionProvider uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Tool~SuggestionProvider, while a change to Tool~SuggestionProvider can't break Tool~ConversationServiceProvider.
Position
Below the diagonal: Tool~SuggestionProvider uses a module listed above it, which is the healthy direction.
15→30 Tool~SuggestionProvider uses Core~HostApppart of a loop✕
Connections
2 pairs of types, where a type in Tool~SuggestionProvider uses a type in Core~HostApp.
Tool~SuggestionProvider uses Core~HostApp, so a change to Core~HostApp can break Tool~SuggestionProvider, while a change to Tool~SuggestionProvider can't break Core~HostApp.
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→35 Tool~SuggestionProvider uses Core~ConversationTabpart of a loop✕
Connections
1 pair of types, where a type in Tool~SuggestionProvider uses a type in Core~ConversationTab.
Tool~SuggestionProvider uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~SuggestionProvider, while a change to Tool~SuggestionProvider can't break Core~ConversationTab.
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.
Tool~TelemetryServiceProvider uses Tool~Preferences, so a change to Tool~Preferences can break Tool~TelemetryServiceProvider, while a change to Tool~TelemetryServiceProvider can't break Tool~Preferences.
Position
Below the diagonal: Tool~TelemetryServiceProvider uses a module listed above it, which is the healthy direction.
Tool~TelemetryServiceProvider uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Tool~TelemetryServiceProvider, while a change to Tool~TelemetryServiceProvider can't break Tool~ConversationServiceProvider.
Position
Below the diagonal: Tool~TelemetryServiceProvider uses a module listed above it, which is the healthy direction.
16→30 Tool~TelemetryServiceProvider uses Core~HostApppart of a loop✕
Connections
5 pairs of types, where a type in Tool~TelemetryServiceProvider uses a type in Core~HostApp.
Tool~TelemetryServiceProvider uses Core~HostApp, so a change to Core~HostApp can break Tool~TelemetryServiceProvider, while a change to Tool~TelemetryServiceProvider can't break Core~HostApp.
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.
Core~SuggestionService uses Tool~Preferences, so a change to Tool~Preferences can break Core~SuggestionService, while a change to Core~SuggestionService can't break Tool~Preferences.
Position
Below the diagonal: Core~SuggestionService uses a module listed above it, which is the healthy direction.
Core~SuggestionService uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Core~SuggestionService, while a change to Core~SuggestionService can't break Tool~SuggestionBasic.
Position
Below the diagonal: Core~SuggestionService uses a module listed above it, which is the healthy direction.
Core~SuggestionService uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Core~SuggestionService, while a change to Core~SuggestionService can't break Tool~ConversationServiceProvider.
Position
Below the diagonal: Core~SuggestionService uses a module listed above it, which is the healthy direction.
Core~SuggestionService uses Tool~SuggestionProvider, so a change to Tool~SuggestionProvider can break Core~SuggestionService, while a change to Core~SuggestionService can't break Tool~SuggestionProvider.
Position
Below the diagonal: Core~SuggestionService uses a module listed above it, which is the healthy direction.
Tool~WorkspaceSuggestionService uses Tool~Preferences, so a change to Tool~Preferences can break Tool~WorkspaceSuggestionService, while a change to Tool~WorkspaceSuggestionService can't break Tool~Preferences.
Position
Below the diagonal: Tool~WorkspaceSuggestionService uses a module listed above it, which is the healthy direction.
Tool~WorkspaceSuggestionService uses Tool~XPCShared, so a change to Tool~XPCShared can break Tool~WorkspaceSuggestionService, while a change to Tool~WorkspaceSuggestionService can't break Tool~XPCShared.
Position
Below the diagonal: Tool~WorkspaceSuggestionService uses a module listed above it, which is the healthy direction.
Tool~WorkspaceSuggestionService uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Tool~WorkspaceSuggestionService, while a change to Tool~WorkspaceSuggestionService can't break Tool~SuggestionBasic.
Position
Below the diagonal: Tool~WorkspaceSuggestionService uses a module listed above it, which is the healthy direction.
Tool~WorkspaceSuggestionService uses Tool~SuggestionProvider, so a change to Tool~SuggestionProvider can break Tool~WorkspaceSuggestionService, while a change to Tool~WorkspaceSuggestionService can't break Tool~SuggestionProvider.
Position
Below the diagonal: Tool~WorkspaceSuggestionService uses a module listed above it, which is the healthy direction.
18→19 Tool~WorkspaceSuggestionService uses Tool~Workspacepart of a loop✕
Connections
4 pairs of types, where a type in Tool~WorkspaceSuggestionService uses a type in Tool~Workspace.
Tool~WorkspaceSuggestionService uses Tool~Workspace, so a change to Tool~Workspace can break Tool~WorkspaceSuggestionService, while a change to Tool~WorkspaceSuggestionService can't break Tool~Workspace.
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→30 Tool~WorkspaceSuggestionService uses Core~HostApppart of a loop✕
Connections
2 pairs of types, where a type in Tool~WorkspaceSuggestionService uses a type in Core~HostApp.
Tool~WorkspaceSuggestionService uses Core~HostApp, so a change to Core~HostApp can break Tool~WorkspaceSuggestionService, while a change to Tool~WorkspaceSuggestionService can't break Core~HostApp.
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.
Tool~Workspace uses Tool~Preferences, so a change to Tool~Preferences can break Tool~Workspace, while a change to Tool~Workspace can't break Tool~Preferences.
Position
Below the diagonal: Tool~Workspace uses a module listed above it, which is the healthy direction.
Tool~Workspace uses Tool~XPCShared, so a change to Tool~XPCShared can break Tool~Workspace, while a change to Tool~Workspace can't break Tool~XPCShared.
Position
Below the diagonal: Tool~Workspace uses a module listed above it, which is the healthy direction.
Tool~Workspace uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Tool~Workspace, while a change to Tool~Workspace can't break Tool~SuggestionBasic.
Position
Below the diagonal: Tool~Workspace uses a module listed above it, which is the healthy direction.
Tool~Workspace uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Tool~Workspace, while a change to Tool~Workspace can't break Tool~ConversationServiceProvider.
Position
Below the diagonal: Tool~Workspace uses a module listed above it, which is the healthy direction.
Tool~Workspace uses Tool~SuggestionProvider, so a change to Tool~SuggestionProvider can break Tool~Workspace, while a change to Tool~Workspace can't break Tool~SuggestionProvider.
Position
Below the diagonal: Tool~Workspace uses a module listed above it, which is the healthy direction.
Tool~Workspace uses Tool~WorkspaceSuggestionService, so a change to Tool~WorkspaceSuggestionService can break Tool~Workspace, while a change to Tool~Workspace can't break Tool~WorkspaceSuggestionService.
Position
Below the diagonal: Tool~Workspace uses a module listed above it, which is the healthy direction.
19→21 Tool~Workspace uses Tool~GitHubCopilotServicepart of a loop✕
Connections
2 pairs of types, where a type in Tool~Workspace uses a type in Tool~GitHubCopilotService.
Tool~Workspace uses Tool~GitHubCopilotService, so a change to Tool~GitHubCopilotService can break Tool~Workspace, while a change to Tool~Workspace can't break Tool~GitHubCopilotService.
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→22 Tool~Workspace uses Tool~FileSystempart of a loop✕
Connections
1 pair of types, where a type in Tool~Workspace uses a type in Tool~FileSystem.
The types involved
Tool~Workspace.Filespace → Tool~FileSystem.Date
Direction
Tool~Workspace uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~Workspace, while a change to Tool~Workspace can't break Tool~FileSystem.
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→30 Tool~Workspace uses Core~HostApppart of a loop✕
Connections
12 pairs of types, where a type in Tool~Workspace uses a type in Core~HostApp.
Tool~Workspace uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~Workspace, while a change to Tool~Workspace can't break Core~ConversationTab.
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.
Tool~BuiltinExtension uses Tool~Preferences, so a change to Tool~Preferences can break Tool~BuiltinExtension, while a change to Tool~BuiltinExtension can't break Tool~Preferences.
Position
Below the diagonal: Tool~BuiltinExtension uses a module listed above it, which is the healthy direction.
Tool~BuiltinExtension uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Tool~BuiltinExtension, while a change to Tool~BuiltinExtension can't break Tool~SuggestionBasic.
Position
Below the diagonal: Tool~BuiltinExtension uses a module listed above it, which is the healthy direction.
Tool~BuiltinExtension uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Tool~BuiltinExtension, while a change to Tool~BuiltinExtension can't break Tool~ConversationServiceProvider.
Position
Below the diagonal: Tool~BuiltinExtension uses a module listed above it, which is the healthy direction.
Tool~BuiltinExtension uses Tool~SuggestionProvider, so a change to Tool~SuggestionProvider can break Tool~BuiltinExtension, while a change to Tool~BuiltinExtension can't break Tool~SuggestionProvider.
Position
Below the diagonal: Tool~BuiltinExtension uses a module listed above it, which is the healthy direction.
Tool~BuiltinExtension uses Tool~TelemetryServiceProvider, so a change to Tool~TelemetryServiceProvider can break Tool~BuiltinExtension, while a change to Tool~BuiltinExtension can't break Tool~TelemetryServiceProvider.
Position
Below the diagonal: Tool~BuiltinExtension uses a module listed above it, which is the healthy direction.
Tool~BuiltinExtension uses Tool~Workspace, so a change to Tool~Workspace can break Tool~BuiltinExtension, while a change to Tool~BuiltinExtension can't break Tool~Workspace.
Position
Below the diagonal: Tool~BuiltinExtension uses a module listed above it, which is the healthy direction.
20→30 Tool~BuiltinExtension uses Core~HostApppart of a loop✕
Connections
7 pairs of types, where a type in Tool~BuiltinExtension uses a type in Core~HostApp.
Tool~BuiltinExtension uses Core~HostApp, so a change to Core~HostApp can break Tool~BuiltinExtension, while a change to Tool~BuiltinExtension can't break Core~HostApp.
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→35 Tool~BuiltinExtension uses Core~ConversationTabpart of a loop✕
Connections
3 pairs of types, where a type in Tool~BuiltinExtension uses a type in Core~ConversationTab.
Tool~BuiltinExtension uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~BuiltinExtension, while a change to Tool~BuiltinExtension can't break Core~ConversationTab.
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.
69 pairs of types, where a type in Tool~GitHubCopilotService uses a type in Tool~Preferences. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Tool~GitHubCopilotService uses Tool~Preferences, so a change to Tool~Preferences can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Tool~Preferences.
Position
Below the diagonal: Tool~GitHubCopilotService uses a module listed above it, which is the healthy direction.
Tool~GitHubCopilotService uses Core~LaunchAgentManager, so a change to Core~LaunchAgentManager can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Core~LaunchAgentManager.
Position
Below the diagonal: Tool~GitHubCopilotService uses a module listed above it, which is the healthy direction.
Tool~GitHubCopilotService uses Tool~Status, so a change to Tool~Status can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Tool~Status.
Position
Below the diagonal: Tool~GitHubCopilotService uses a module listed above it, which is the healthy direction.
Tool~GitHubCopilotService uses repository, so a change to repository can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break repository.
Position
Below the diagonal: Tool~GitHubCopilotService uses a module listed above it, which is the healthy direction.
Tool~GitHubCopilotService uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Tool~SuggestionBasic.
Position
Below the diagonal: Tool~GitHubCopilotService uses a module listed above it, which is the healthy direction.
84 pairs of types, where a type in Tool~GitHubCopilotService uses a type in Tool~ConversationServiceProvider. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Tool~GitHubCopilotService uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Tool~ConversationServiceProvider.
Position
Below the diagonal: Tool~GitHubCopilotService uses a module listed above it, which is the healthy direction.
Tool~GitHubCopilotService uses Tool~Persist, so a change to Tool~Persist can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Tool~Persist.
Position
Below the diagonal: Tool~GitHubCopilotService uses a module listed above it, which is the healthy direction.
Tool~GitHubCopilotService uses Tool~SuggestionProvider, so a change to Tool~SuggestionProvider can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Tool~SuggestionProvider.
Position
Below the diagonal: Tool~GitHubCopilotService uses a module listed above it, which is the healthy direction.
Tool~GitHubCopilotService uses Tool~TelemetryServiceProvider, so a change to Tool~TelemetryServiceProvider can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Tool~TelemetryServiceProvider.
Position
Below the diagonal: Tool~GitHubCopilotService uses a module listed above it, which is the healthy direction.
Tool~GitHubCopilotService uses Core~SuggestionService, so a change to Core~SuggestionService can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Core~SuggestionService.
Position
Below the diagonal: Tool~GitHubCopilotService uses a module listed above it, which is the healthy direction.
Tool~GitHubCopilotService uses Tool~Workspace, so a change to Tool~Workspace can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Tool~Workspace.
Position
Below the diagonal: Tool~GitHubCopilotService uses a module listed above it, which is the healthy direction.
Tool~GitHubCopilotService uses Tool~BuiltinExtension, so a change to Tool~BuiltinExtension can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Tool~BuiltinExtension.
Position
Below the diagonal: Tool~GitHubCopilotService uses a module listed above it, which is the healthy direction.
21→30 Tool~GitHubCopilotService uses Core~HostApppart of a loop✕
Connections
113 pairs of types, where a type in Tool~GitHubCopilotService uses a type in Core~HostApp. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Tool~GitHubCopilotService uses Core~HostApp, so a change to Core~HostApp can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Core~HostApp.
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→35 Tool~GitHubCopilotService uses Core~ConversationTabpart of a loop✕
Connections
12 pairs of types, where a type in Tool~GitHubCopilotService uses a type in Core~ConversationTab.
Tool~GitHubCopilotService uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Core~ConversationTab.
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.
28 pairs of types, where a type in Tool~FileSystem uses a type in Tool~Preferences. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Tool~FileSystem uses Tool~Preferences, so a change to Tool~Preferences can break Tool~FileSystem, while a change to Tool~FileSystem can't break Tool~Preferences.
Position
Below the diagonal: Tool~FileSystem uses a module listed above it, which is the healthy direction.
Tool~FileSystem uses Tool~GitHubCopilotService, so a change to Tool~GitHubCopilotService can break Tool~FileSystem, while a change to Tool~FileSystem can't break Tool~GitHubCopilotService.
Position
Below the diagonal: Tool~FileSystem uses a module listed above it, which is the healthy direction.
22→30 Tool~FileSystem uses Core~HostApppart of a loop✕
Connections
22 pairs of types, where a type in Tool~FileSystem uses a type in Core~HostApp.
Tool~FileSystem uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~FileSystem, while a change to Tool~FileSystem can't break Core~ConversationTab.
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.
Core~GitHubCopilotViewModel uses Tool~Preferences, so a change to Tool~Preferences can break Core~GitHubCopilotViewModel, while a change to Core~GitHubCopilotViewModel can't break Tool~Preferences.
Position
Below the diagonal: Core~GitHubCopilotViewModel uses a module listed above it, which is the healthy direction.
Core~GitHubCopilotViewModel uses Tool~GitHubCopilotService, so a change to Tool~GitHubCopilotService can break Core~GitHubCopilotViewModel, while a change to Core~GitHubCopilotViewModel can't break Tool~GitHubCopilotService.
Position
Below the diagonal: Core~GitHubCopilotViewModel uses a module listed above it, which is the healthy direction.
Core~GitHubCopilotViewModel uses Tool~FileSystem, so a change to Tool~FileSystem can break Core~GitHubCopilotViewModel, while a change to Core~GitHubCopilotViewModel can't break Tool~FileSystem.
Position
Below the diagonal: Core~GitHubCopilotViewModel uses a module listed above it, which is the healthy direction.
23→30 Core~GitHubCopilotViewModel uses Core~HostApppart of a loop✕
Connections
2 pairs of types, where a type in Core~GitHubCopilotViewModel uses a type in Core~HostApp.
Core~GitHubCopilotViewModel uses Core~HostApp, so a change to Core~HostApp can break Core~GitHubCopilotViewModel, while a change to Core~GitHubCopilotViewModel can't break Core~HostApp.
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→35 Core~GitHubCopilotViewModel uses Core~ConversationTabpart of a loop✕
Connections
1 pair of types, where a type in Core~GitHubCopilotViewModel uses a type in Core~ConversationTab.
Core~GitHubCopilotViewModel uses Core~ConversationTab, so a change to Core~ConversationTab can break Core~GitHubCopilotViewModel, while a change to Core~GitHubCopilotViewModel can't break Core~ConversationTab.
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.
Tool~ChatTab uses Tool~Preferences, so a change to Tool~Preferences can break Tool~ChatTab, while a change to Tool~ChatTab can't break Tool~Preferences.
Position
Below the diagonal: Tool~ChatTab uses a module listed above it, which is the healthy direction.
Tool~ChatTab uses Core~SuggestionWidget, so a change to Core~SuggestionWidget can break Tool~ChatTab, while a change to Tool~ChatTab can't break Core~SuggestionWidget.
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→30 Tool~ChatTab uses Core~HostApppart of a loop✕
Connections
9 pairs of types, where a type in Tool~ChatTab uses a type in Core~HostApp.
Tool~ChatTab uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~ChatTab, while a change to Tool~ChatTab can't break Core~ConversationTab.
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.
Tool~CustomAsyncAlgorithms uses repository, so a change to repository can break Tool~CustomAsyncAlgorithms, while a change to Tool~CustomAsyncAlgorithms can't break repository.
Position
Below the diagonal: Tool~CustomAsyncAlgorithms uses a module listed above it, which is the healthy direction.
Tool~CustomAsyncAlgorithms uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~CustomAsyncAlgorithms, while a change to Tool~CustomAsyncAlgorithms can't break Tool~FileSystem.
Position
Below the diagonal: Tool~CustomAsyncAlgorithms uses a module listed above it, which is the healthy direction.
Tool~DebounceFunction uses Tool~Preferences, so a change to Tool~Preferences can break Tool~DebounceFunction, while a change to Tool~DebounceFunction can't break Tool~Preferences.
Position
Below the diagonal: Tool~DebounceFunction uses a module listed above it, which is the healthy direction.
Tool~DebounceFunction uses repository, so a change to repository can break Tool~DebounceFunction, while a change to Tool~DebounceFunction can't break repository.
Position
Below the diagonal: Tool~DebounceFunction uses a module listed above it, which is the healthy direction.
Tool~DebounceFunction uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~DebounceFunction, while a change to Tool~DebounceFunction can't break Tool~FileSystem.
Position
Below the diagonal: Tool~DebounceFunction uses a module listed above it, which is the healthy direction.
38 pairs of types, where a type in Tool~SharedUIComponents uses a type in Tool~Preferences. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Tool~SharedUIComponents uses Tool~Preferences, so a change to Tool~Preferences can break Tool~SharedUIComponents, while a change to Tool~SharedUIComponents can't break Tool~Preferences.
Position
Below the diagonal: Tool~SharedUIComponents uses a module listed above it, which is the healthy direction.
Tool~SharedUIComponents uses Tool~Status, so a change to Tool~Status can break Tool~SharedUIComponents, while a change to Tool~SharedUIComponents can't break Tool~Status.
Position
Below the diagonal: Tool~SharedUIComponents uses a module listed above it, which is the healthy direction.
Tool~SharedUIComponents uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Tool~SharedUIComponents, while a change to Tool~SharedUIComponents can't break Tool~ConversationServiceProvider.
Position
Below the diagonal: Tool~SharedUIComponents uses a module listed above it, which is the healthy direction.
Tool~SharedUIComponents uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~SharedUIComponents, while a change to Tool~SharedUIComponents can't break Tool~FileSystem.
Position
Below the diagonal: Tool~SharedUIComponents uses a module listed above it, which is the healthy direction.
27→30 Tool~SharedUIComponents uses Core~HostApppart of a loop✕
Connections
21 pairs of types, where a type in Tool~SharedUIComponents uses a type in Core~HostApp.
Tool~SharedUIComponents uses Core~HostApp, so a change to Core~HostApp can break Tool~SharedUIComponents, while a change to Tool~SharedUIComponents can't break Core~HostApp.
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.
27→35 Tool~SharedUIComponents uses Core~ConversationTabpart of a loop✕
Connections
43 pairs of types, where a type in Tool~SharedUIComponents uses a type in Core~ConversationTab. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Tool~SharedUIComponents uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~SharedUIComponents, while a change to Tool~SharedUIComponents can't break Core~ConversationTab.
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.
Tool~XcodeInspector uses Tool~Preferences, so a change to Tool~Preferences can break Tool~XcodeInspector, while a change to Tool~XcodeInspector can't break Tool~Preferences.
Position
Below the diagonal: Tool~XcodeInspector uses a module listed above it, which is the healthy direction.
Tool~XcodeInspector uses Tool~Status, so a change to Tool~Status can break Tool~XcodeInspector, while a change to Tool~XcodeInspector can't break Tool~Status.
Position
Below the diagonal: Tool~XcodeInspector uses a module listed above it, which is the healthy direction.
Tool~XcodeInspector uses Tool~Toast, so a change to Tool~Toast can break Tool~XcodeInspector, while a change to Tool~XcodeInspector can't break Tool~Toast.
Position
Below the diagonal: Tool~XcodeInspector uses a module listed above it, which is the healthy direction.
Tool~XcodeInspector uses repository, so a change to repository can break Tool~XcodeInspector, while a change to Tool~XcodeInspector can't break repository.
Position
Below the diagonal: Tool~XcodeInspector uses a module listed above it, which is the healthy direction.
Tool~XcodeInspector uses Tool~AXExtension, so a change to Tool~AXExtension can break Tool~XcodeInspector, while a change to Tool~XcodeInspector can't break Tool~AXExtension.
Position
Below the diagonal: Tool~XcodeInspector uses a module listed above it, which is the healthy direction.
Tool~XcodeInspector uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Tool~XcodeInspector, while a change to Tool~XcodeInspector can't break Tool~SuggestionBasic.
Position
Below the diagonal: Tool~XcodeInspector uses a module listed above it, which is the healthy direction.
Tool~XcodeInspector uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~XcodeInspector, while a change to Tool~XcodeInspector can't break Tool~FileSystem.
Position
Below the diagonal: Tool~XcodeInspector uses a module listed above it, which is the healthy direction.
28→29 Tool~XcodeInspector uses Core~SuggestionWidgetpart of a loop✕
Connections
1 pair of types, where a type in Tool~XcodeInspector uses a type in Core~SuggestionWidget.
Tool~XcodeInspector uses Core~SuggestionWidget, so a change to Core~SuggestionWidget can break Tool~XcodeInspector, while a change to Tool~XcodeInspector can't break Core~SuggestionWidget.
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.
28→30 Tool~XcodeInspector uses Core~HostApppart of a loop✕
Connections
7 pairs of types, where a type in Tool~XcodeInspector uses a type in Core~HostApp.
Tool~XcodeInspector uses Core~HostApp, so a change to Core~HostApp can break Tool~XcodeInspector, while a change to Tool~XcodeInspector can't break Core~HostApp.
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.
28→35 Tool~XcodeInspector uses Core~ConversationTabpart of a loop✕
Connections
5 pairs of types, where a type in Tool~XcodeInspector uses a type in Core~ConversationTab.
Tool~XcodeInspector uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~XcodeInspector, while a change to Tool~XcodeInspector can't break Core~ConversationTab.
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.
74 pairs of types, where a type in Core~SuggestionWidget uses a type in Tool~Preferences. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Core~SuggestionWidget uses Tool~Preferences, so a change to Tool~Preferences can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~Preferences.
Position
Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
Core~SuggestionWidget uses Tool~Status, so a change to Tool~Status can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~Status.
Position
Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
Core~SuggestionWidget uses repository, so a change to repository can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break repository.
Position
Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
Core~SuggestionWidget uses Tool~AXExtension, so a change to Tool~AXExtension can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~AXExtension.
Position
Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
Core~SuggestionWidget uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~SuggestionBasic.
Position
Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
Core~SuggestionWidget uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~ConversationServiceProvider.
Position
Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
Core~SuggestionWidget uses Tool~WorkspaceSuggestionService, so a change to Tool~WorkspaceSuggestionService can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~WorkspaceSuggestionService.
Position
Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
Core~SuggestionWidget uses Tool~GitHubCopilotService, so a change to Tool~GitHubCopilotService can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~GitHubCopilotService.
Position
Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
Core~SuggestionWidget uses Tool~FileSystem, so a change to Tool~FileSystem can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~FileSystem.
Position
Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
Core~SuggestionWidget uses Core~GitHubCopilotViewModel, so a change to Core~GitHubCopilotViewModel can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Core~GitHubCopilotViewModel.
Position
Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
Core~SuggestionWidget uses Tool~ChatTab, so a change to Tool~ChatTab can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~ChatTab.
Position
Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
Core~SuggestionWidget uses Tool~SharedUIComponents, so a change to Tool~SharedUIComponents can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~SharedUIComponents.
Position
Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
Core~SuggestionWidget uses Tool~XcodeInspector, so a change to Tool~XcodeInspector can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~XcodeInspector.
Position
Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
29→30 Core~SuggestionWidget uses Core~HostApppart of a loop✕
Connections
42 pairs of types, where a type in Core~SuggestionWidget uses a type in Core~HostApp. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Core~SuggestionWidget uses Core~HostApp, so a change to Core~HostApp can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Core~HostApp.
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.
29→35 Core~SuggestionWidget uses Core~ConversationTabpart of a loop✕
Connections
95 pairs of types, where a type in Core~SuggestionWidget uses a type in Core~ConversationTab. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Core~SuggestionWidget uses Core~ConversationTab, so a change to Core~ConversationTab can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Core~ConversationTab.
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.
73 pairs of types, where a type in Core~HostApp uses a type in Tool~Preferences. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Core~HostApp uses Tool~Preferences, so a change to Tool~Preferences can break Core~HostApp, while a change to Core~HostApp can't break Tool~Preferences.
Position
Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
Core~HostApp uses Tool~ActiveApplicationMonitor, so a change to Tool~ActiveApplicationMonitor can break Core~HostApp, while a change to Core~HostApp can't break Tool~ActiveApplicationMonitor.
Position
Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
Core~HostApp uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Core~HostApp, while a change to Core~HostApp can't break Tool~SuggestionBasic.
Position
Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
Core~HostApp uses Core~PromptToCodeService, so a change to Core~PromptToCodeService can break Core~HostApp, while a change to Core~HostApp can't break Core~PromptToCodeService.
Position
Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
Core~HostApp uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Core~HostApp, while a change to Core~HostApp can't break Tool~ConversationServiceProvider.
Position
Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
41 pairs of types, where a type in Core~HostApp uses a type in Tool~GitHubCopilotService. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Core~HostApp uses Tool~GitHubCopilotService, so a change to Tool~GitHubCopilotService can break Core~HostApp, while a change to Core~HostApp can't break Tool~GitHubCopilotService.
Position
Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
Core~HostApp uses Core~GitHubCopilotViewModel, so a change to Core~GitHubCopilotViewModel can break Core~HostApp, while a change to Core~HostApp can't break Core~GitHubCopilotViewModel.
Position
Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
Core~HostApp uses Tool~SharedUIComponents, so a change to Tool~SharedUIComponents can break Core~HostApp, while a change to Core~HostApp can't break Tool~SharedUIComponents.
Position
Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
Core~HostApp uses Tool~XcodeInspector, so a change to Tool~XcodeInspector can break Core~HostApp, while a change to Core~HostApp can't break Tool~XcodeInspector.
Position
Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
Core~HostApp uses Core~SuggestionWidget, so a change to Core~SuggestionWidget can break Core~HostApp, while a change to Core~HostApp can't break Core~SuggestionWidget.
Position
Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
30→35 Core~HostApp uses Core~ConversationTabpart of a loop✕
Connections
77 pairs of types, where a type in Core~HostApp uses a type in Core~ConversationTab. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Core~HostApp uses Core~ConversationTab, so a change to Core~ConversationTab can break Core~HostApp, while a change to Core~HostApp can't break Core~ConversationTab.
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.
30→37 Core~HostApp uses Core~ChatServicepart of a loop✕
Connections
1 pair of types, where a type in Core~HostApp uses a type in Core~ChatService.
The types involved
Core~HostApp.String → Core~ChatService.Array
Direction
Core~HostApp uses Core~ChatService, so a change to Core~ChatService can break Core~HostApp, while a change to Core~HostApp can't break Core~ChatService.
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.
Core~SuggestionInjector uses Tool~Preferences, so a change to Tool~Preferences can break Core~SuggestionInjector, while a change to Core~SuggestionInjector can't break Tool~Preferences.
Position
Below the diagonal: Core~SuggestionInjector uses a module listed above it, which is the healthy direction.
Core~SuggestionInjector uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Core~SuggestionInjector, while a change to Core~SuggestionInjector can't break Tool~SuggestionBasic.
Position
Below the diagonal: Core~SuggestionInjector uses a module listed above it, which is the healthy direction.
Core~SuggestionInjector uses Core~HostApp, so a change to Core~HostApp can break Core~SuggestionInjector, while a change to Core~SuggestionInjector can't break Core~HostApp.
Position
Below the diagonal: Core~SuggestionInjector uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in Tool~AXHelper uses a type in Tool~Preferences.
The types involved
Tool~AXHelper.AXHelper → Tool~Preferences.Double
Tool~AXHelper.AXHelper → Tool~Preferences.Int
Direction
Tool~AXHelper uses Tool~Preferences, so a change to Tool~Preferences can break Tool~AXHelper, while a change to Tool~AXHelper can't break Tool~Preferences.
Position
Below the diagonal: Tool~AXHelper uses a module listed above it, which is the healthy direction.
Tool~AXHelper uses Tool~AXExtension, so a change to Tool~AXExtension can break Tool~AXHelper, while a change to Tool~AXHelper can't break Tool~AXExtension.
Position
Below the diagonal: Tool~AXHelper uses a module listed above it, which is the healthy direction.
Tool~AXNotificationStream uses repository, so a change to repository can break Tool~AXNotificationStream, while a change to Tool~AXNotificationStream can't break repository.
Position
Below the diagonal: Tool~AXNotificationStream uses a module listed above it, which is the healthy direction.
Tool~AXNotificationStream uses Tool~AXExtension, so a change to Tool~AXExtension can break Tool~AXNotificationStream, while a change to Tool~AXNotificationStream can't break Tool~AXExtension.
Position
Below the diagonal: Tool~AXNotificationStream uses a module listed above it, which is the healthy direction.
Tool~AXNotificationStream uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~AXNotificationStream, while a change to Tool~AXNotificationStream can't break Tool~FileSystem.
Position
Below the diagonal: Tool~AXNotificationStream uses a module listed above it, which is the healthy direction.
Tool~AXNotificationStream uses Tool~CustomAsyncAlgorithms, so a change to Tool~CustomAsyncAlgorithms can break Tool~AXNotificationStream, while a change to Tool~AXNotificationStream can't break Tool~CustomAsyncAlgorithms.
Position
Below the diagonal: Tool~AXNotificationStream uses a module listed above it, which is the healthy direction.
Tool~AXNotificationStream uses Core~HostApp, so a change to Core~HostApp can break Tool~AXNotificationStream, while a change to Tool~AXNotificationStream can't break Core~HostApp.
Position
Below the diagonal: Tool~AXNotificationStream uses a module listed above it, which is the healthy direction.
Tool~ChatAPIService uses Tool~Preferences, so a change to Tool~Preferences can break Tool~ChatAPIService, while a change to Tool~ChatAPIService can't break Tool~Preferences.
Position
Below the diagonal: Tool~ChatAPIService uses a module listed above it, which is the healthy direction.
Tool~ChatAPIService uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Tool~ChatAPIService, while a change to Tool~ChatAPIService can't break Tool~ConversationServiceProvider.
Position
Below the diagonal: Tool~ChatAPIService uses a module listed above it, which is the healthy direction.
Tool~ChatAPIService uses Tool~Persist, so a change to Tool~Persist can break Tool~ChatAPIService, while a change to Tool~ChatAPIService can't break Tool~Persist.
Position
Below the diagonal: Tool~ChatAPIService uses a module listed above it, which is the healthy direction.
Tool~ChatAPIService uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~ChatAPIService, while a change to Tool~ChatAPIService can't break Tool~FileSystem.
Position
Below the diagonal: Tool~ChatAPIService uses a module listed above it, which is the healthy direction.
Tool~ChatAPIService uses Tool~CustomAsyncAlgorithms, so a change to Tool~CustomAsyncAlgorithms can break Tool~ChatAPIService, while a change to Tool~ChatAPIService can't break Tool~CustomAsyncAlgorithms.
Position
Below the diagonal: Tool~ChatAPIService uses a module listed above it, which is the healthy direction.
Tool~ChatAPIService uses Core~HostApp, so a change to Core~HostApp can break Tool~ChatAPIService, while a change to Tool~ChatAPIService can't break Core~HostApp.
Position
Below the diagonal: Tool~ChatAPIService uses a module listed above it, which is the healthy direction.
34→35 Tool~ChatAPIService uses Core~ConversationTabpart of a loop✕
Connections
2 pairs of types, where a type in Tool~ChatAPIService uses a type in Core~ConversationTab.
Tool~ChatAPIService uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~ChatAPIService, while a change to Tool~ChatAPIService can't break Core~ConversationTab.
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.
120 pairs of types, where a type in Core~ConversationTab uses a type in Tool~Preferences. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Core~ConversationTab uses Tool~Preferences, so a change to Tool~Preferences can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~Preferences.
Position
Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
Core~ConversationTab uses Tool~Status, so a change to Tool~Status can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~Status.
Position
Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
Core~ConversationTab uses repository, so a change to repository can break Core~ConversationTab, while a change to Core~ConversationTab can't break repository.
Position
Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
Core~ConversationTab uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~SuggestionBasic.
Position
Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
69 pairs of types, where a type in Core~ConversationTab uses a type in Tool~ConversationServiceProvider. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Core~ConversationTab uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~ConversationServiceProvider.
Position
Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
Core~ConversationTab uses Tool~GitHubCopilotService, so a change to Tool~GitHubCopilotService can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~GitHubCopilotService.
Position
Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
Core~ConversationTab uses Tool~FileSystem, so a change to Tool~FileSystem can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~FileSystem.
Position
Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
Core~ConversationTab uses Tool~ChatTab, so a change to Tool~ChatTab can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~ChatTab.
Position
Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
Core~ConversationTab uses Tool~DebounceFunction, so a change to Tool~DebounceFunction can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~DebounceFunction.
Position
Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
Core~ConversationTab uses Tool~SharedUIComponents, so a change to Tool~SharedUIComponents can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~SharedUIComponents.
Position
Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
Core~ConversationTab uses Tool~XcodeInspector, so a change to Tool~XcodeInspector can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~XcodeInspector.
Position
Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
Core~ConversationTab uses Core~SuggestionWidget, so a change to Core~SuggestionWidget can break Core~ConversationTab, while a change to Core~ConversationTab can't break Core~SuggestionWidget.
Position
Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
65 pairs of types, where a type in Core~ConversationTab uses a type in Core~HostApp. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Core~ConversationTab uses Core~HostApp, so a change to Core~HostApp can break Core~ConversationTab, while a change to Core~ConversationTab can't break Core~HostApp.
Position
Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
Core~ConversationTab uses Tool~ChatAPIService, so a change to Tool~ChatAPIService can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~ChatAPIService.
Position
Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
35→37 Core~ConversationTab uses Core~ChatServicepart of a loop✕
Connections
5 pairs of types, where a type in Core~ConversationTab uses a type in Core~ChatService.
Core~ConversationTab uses Core~ChatService, so a change to Core~ChatService can break Core~ConversationTab, while a change to Core~ConversationTab can't break Core~ChatService.
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.
Core~PersistMiddleware uses Tool~Persist, so a change to Tool~Persist can break Core~PersistMiddleware, while a change to Core~PersistMiddleware can't break Tool~Persist.
Position
Below the diagonal: Core~PersistMiddleware uses a module listed above it, which is the healthy direction.
Core~PersistMiddleware uses Tool~ChatTab, so a change to Tool~ChatTab can break Core~PersistMiddleware, while a change to Core~PersistMiddleware can't break Tool~ChatTab.
Position
Below the diagonal: Core~PersistMiddleware uses a module listed above it, which is the healthy direction.
Core~PersistMiddleware uses Core~HostApp, so a change to Core~HostApp can break Core~PersistMiddleware, while a change to Core~PersistMiddleware can't break Core~HostApp.
Position
Below the diagonal: Core~PersistMiddleware uses a module listed above it, which is the healthy direction.
Core~PersistMiddleware uses Tool~ChatAPIService, so a change to Tool~ChatAPIService can break Core~PersistMiddleware, while a change to Core~PersistMiddleware can't break Tool~ChatAPIService.
Position
Below the diagonal: Core~PersistMiddleware uses a module listed above it, which is the healthy direction.
29 pairs of types, where a type in Core~ChatService uses a type in Tool~Preferences. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Core~ChatService uses Tool~Preferences, so a change to Tool~Preferences can break Core~ChatService, while a change to Core~ChatService can't break Tool~Preferences.
Position
Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
Core~ChatService uses Tool~GitHelper, so a change to Tool~GitHelper can break Core~ChatService, while a change to Core~ChatService can't break Tool~GitHelper.
Position
Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
Core~ChatService uses Tool~AXExtension, so a change to Tool~AXExtension can break Core~ChatService, while a change to Core~ChatService can't break Tool~AXExtension.
Position
Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
Core~ChatService uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Core~ChatService, while a change to Core~ChatService can't break Tool~SuggestionBasic.
Position
Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
29 pairs of types, where a type in Core~ChatService uses a type in Tool~ConversationServiceProvider. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Core~ChatService uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Core~ChatService, while a change to Core~ChatService can't break Tool~ConversationServiceProvider.
Position
Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
Core~ChatService uses Tool~Persist, so a change to Tool~Persist can break Core~ChatService, while a change to Core~ChatService can't break Tool~Persist.
Position
Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
Core~ChatService uses Tool~GitHubCopilotService, so a change to Tool~GitHubCopilotService can break Core~ChatService, while a change to Core~ChatService can't break Tool~GitHubCopilotService.
Position
Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
Core~ChatService uses Tool~FileSystem, so a change to Tool~FileSystem can break Core~ChatService, while a change to Core~ChatService can't break Tool~FileSystem.
Position
Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
Core~ChatService uses Tool~ChatTab, so a change to Tool~ChatTab can break Core~ChatService, while a change to Core~ChatService can't break Tool~ChatTab.
Position
Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
Core~ChatService uses Tool~XcodeInspector, so a change to Tool~XcodeInspector can break Core~ChatService, while a change to Core~ChatService can't break Tool~XcodeInspector.
Position
Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
28 pairs of types, where a type in Core~ChatService uses a type in Core~HostApp. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Core~ChatService uses Core~HostApp, so a change to Core~HostApp can break Core~ChatService, while a change to Core~ChatService can't break Core~HostApp.
Position
Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
Core~ChatService uses Tool~ChatAPIService, so a change to Tool~ChatAPIService can break Core~ChatService, while a change to Core~ChatService can't break Tool~ChatAPIService.
Position
Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
Core~ChatService uses Core~ConversationTab, so a change to Core~ConversationTab can break Core~ChatService, while a change to Core~ChatService can't break Core~ConversationTab.
Position
Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
Core~KeyBindingManager uses Tool~Preferences, so a change to Tool~Preferences can break Core~KeyBindingManager, while a change to Core~KeyBindingManager can't break Tool~Preferences.
Position
Below the diagonal: Core~KeyBindingManager uses a module listed above it, which is the healthy direction.
Core~KeyBindingManager uses Tool~Workspace, so a change to Tool~Workspace can break Core~KeyBindingManager, while a change to Core~KeyBindingManager can't break Tool~Workspace.
Position
Below the diagonal: Core~KeyBindingManager uses a module listed above it, which is the healthy direction.
Core~KeyBindingManager uses Core~SuggestionInjector, so a change to Core~SuggestionInjector can break Core~KeyBindingManager, while a change to Core~KeyBindingManager can't break Core~SuggestionInjector.
Position
Below the diagonal: Core~KeyBindingManager uses a module listed above it, which is the healthy direction.
Core~KeyBindingManager uses Core~ConversationTab, so a change to Core~ConversationTab can break Core~KeyBindingManager, while a change to Core~KeyBindingManager can't break Core~ConversationTab.
Position
Below the diagonal: Core~KeyBindingManager uses a module listed above it, which is the healthy direction.
Core~XcodeThemeController uses Tool~Preferences, so a change to Tool~Preferences can break Core~XcodeThemeController, while a change to Core~XcodeThemeController can't break Tool~Preferences.
Position
Below the diagonal: Core~XcodeThemeController uses a module listed above it, which is the healthy direction.
Core~XcodeThemeController uses repository, so a change to repository can break Core~XcodeThemeController, while a change to Core~XcodeThemeController can't break repository.
Position
Below the diagonal: Core~XcodeThemeController uses a module listed above it, which is the healthy direction.
Core~XcodeThemeController uses Core~SuggestionWidget, so a change to Core~SuggestionWidget can break Core~XcodeThemeController, while a change to Core~XcodeThemeController can't break Core~SuggestionWidget.
Position
Below the diagonal: Core~XcodeThemeController uses a module listed above it, which is the healthy direction.
Core~XcodeThemeController uses Core~HostApp, so a change to Core~HostApp can break Core~XcodeThemeController, while a change to Core~XcodeThemeController can't break Core~HostApp.
Position
Below the diagonal: Core~XcodeThemeController uses a module listed above it, which is the healthy direction.
Core~XcodeThemeController uses Core~ConversationTab, so a change to Core~ConversationTab can break Core~XcodeThemeController, while a change to Core~XcodeThemeController can't break Core~ConversationTab.
Position
Below the diagonal: Core~XcodeThemeController uses a module listed above it, which is the healthy direction.
Core~Service uses Tool~Preferences, so a change to Tool~Preferences can break Core~Service, while a change to Core~Service can't break Tool~Preferences.
Position
Below the diagonal: Core~Service uses a module listed above it, which is the healthy direction.
Core~Service uses Tool~AXExtension, so a change to Tool~AXExtension can break Core~Service, while a change to Core~Service can't break Tool~AXExtension.
Position
Below the diagonal: Core~Service uses a module listed above it, which is the healthy direction.
Core~Service uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Core~Service, while a change to Core~Service can't break Tool~SuggestionBasic.
Position
Below the diagonal: Core~Service uses a module listed above it, which is the healthy direction.
Core~Service uses Tool~WorkspaceSuggestionService, so a change to Tool~WorkspaceSuggestionService can break Core~Service, while a change to Core~Service can't break Tool~WorkspaceSuggestionService.
Position
Below the diagonal: Core~Service uses a module listed above it, which is the healthy direction.
Core~Service uses Tool~XcodeInspector, so a change to Tool~XcodeInspector can break Core~Service, while a change to Core~Service can't break Tool~XcodeInspector.
Position
Below the diagonal: Core~Service uses a module listed above it, which is the healthy direction.
Core~Service uses Core~SuggestionWidget, so a change to Core~SuggestionWidget can break Core~Service, while a change to Core~Service can't break Core~SuggestionWidget.
Position
Below the diagonal: Core~Service uses a module listed above it, which is the healthy direction.
Core~Service uses Core~ConversationTab, so a change to Core~ConversationTab can break Core~Service, while a change to Core~Service can't break Core~ConversationTab.
Position
Below the diagonal: Core~Service uses a module listed above it, which is the healthy direction.
Core~Service uses Core~KeyBindingManager, so a change to Core~KeyBindingManager can break Core~Service, while a change to Core~Service can't break Core~KeyBindingManager.
Position
Below the diagonal: Core~Service uses a module listed above it, which is the healthy direction.
Core~Service uses Core~XcodeThemeController, so a change to Core~XcodeThemeController can break Core~Service, while a change to Core~Service can't break Core~XcodeThemeController.
Position
Below the diagonal: Core~Service uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
10
High / Critical
Roadmap
Top priorities: Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with SwiftFocusedCodeFinderTests.swift; Resolve the 9 Floating branch dependency finding(s) in Dependency Hygiene; Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with SwiftFocusedCodeFinderTests.swift.
Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 9
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 487
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 67
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 21
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 57 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 57 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 497 of 563 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in Core produced no coverage export. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.swift) and this repository declares a SwiftPM test suite (2 packages), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 6 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: cgeventoverride, copilotforxcodekit, highlightr, keyboardshortcuts, languageclient, swiftui-flow-layout.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its SwiftPM package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (6 contributor(s) across 115 commit(s) sampled, automation and bot accounts excluded). One of them holds 85% of the history; the other 5 hold 3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape 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. This says nothing about whether that surface is consistent.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `CommunicationBridge/ServiceDelegate.swift`, `Core/Sources/ChatService/ChatService.swift`, `Core/Sources/ChatService/CodeReview/CodeReviewProvider.swift`, `Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalParsingHelpers.swift`, `Core/Sources/ChatService/ToolCalls/InsertEditIntoFileTool.swift`, … (+56 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is swift-dependencies, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 2 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Python, Swift is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Python, Swift is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
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.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
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.
DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
46 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Chat.body at 151. A further 5 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 LanguageIdentifier.fileExtensions at 58 — they are counted neither in the figure above nor in this dimension's score. 4 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: Tool/Sources/SuggestionBasic/LanguageIdentifierFromFilePath.swift (LanguageIdentifier.fileExtensions at 58), Tool/Sources/GitHubCopilotService/LanguageServer/CustomJSONRPCServerConnection.swift (CustomJSONRPCServerConnection.sendRequest at 50), Tool/Sources/SharedUIComponents/Base/FileIcon.swift (FileIcon.swift.drawFileIcon at 23), Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift (GitHubCopilotError.errorDescription at 19). 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.
+ 41 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with Chat.body (cyclomatic 151), ChatPanelFeature.body (cyclomatic 72). — 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 2 together lifts Cyclomatic Complexity from 5.6 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 89 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 5 bodies over 60 down to 60 or less in Cognitive Complexity — start with Chat.body (cognitive 186), ChatMessage.mergeEditAgentRounds (cognitive 158), ChatMemory.appendMessage (cognitive 130). — 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 Cognitive Complexity from 5.4 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.3 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 13 MethodTooLong finding(s) in God Classes — start with Chat.swift, ChatPanelFeature.swift, WidgetFeature.swift. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 11 FileTooLong finding(s) in God Classes — start with GitHubCopilotService.swift, Chat.swift, ChatService.swift. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 8 TooManyMethods finding(s) in God Classes — start with ChatService.swift, GitHubCopilotService.swift, XPCExtensionService.swift. — One of this dimension's main actionable groups (8 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
77 duplicated block group(s) detected. 7.5 % of the production lines (5,468 of 73,217) are in a reported copy. A further 135 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
Edited copy of a member (12 corresponding lines) · ×10Tool/Sources/Preferences/Types/AutoApprovedMCPServers.swift:20
Edited copy of a member (11 corresponding lines) · ×8Tool/Sources/StatusBarItemView/QuotaView.swift:333
Edited copy of a member (13 corresponding lines) · ×7Tool/Sources/ConversationServiceProvider/LSPTypes+AgentRound.swift:104
Edited copy of a member (9 corresponding lines) · ×7Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:341
+ 83 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with AutoApprovedMCPServers.swift, LSPTypes+AgentRound.swift, GitHubCopilotService.swift. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 8 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with QuotaView.swift, ChatTab.swift, NESDiffView.swift. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 7 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with LSPTypes+AgentRound.swift, XPCService.swift, FileChangeWatcherService.swift. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling6.5 / 10Adequate✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
62 production modules (npm+SwiftPM+Xcode), 0 dependency cycle(s), 7 unstable depended-on module(s). Read from the build's own module declarations; a workspace's implicit (product-name) dependency is not visible there; 18 module(s) off the main sequence, with abstractness counted on 58 of the 62 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: ActiveApplicationMonitor · ×18
Unstable project ChatService
Unstable project ConversationTab
Unstable project KeyBindingManager
Unstable project SuggestionService
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 18 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (18 warning-level).
Resolve the 1 Unstable project ChatService finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project ConversationTab finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 15 Low cohesion finding(s) in Cohesion (LCOM4) — start with ChatService.swift (2), Styles.swift, GitHubCopilotService.swift. — One of this dimension's main actionable groups (15 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.7 / 10Adequategated by 1 critical finding✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 13 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 219 tests (1 harness-style project(s) excluded from the assertion penalty).
No assertions (empty test): test_selecting_a_line_in_freestanding_macro_the_scope_should_be_the_macroTool/Tests/FocusedCodeFinderTests/SwiftFocusedCodeFinderTests.swift:345
No assertions: test_breakLines · ×2Tool/Tests/SuggestionBasicTests/BreakLinePerformanceTests.swift:6
No direct assertions: test_should_accept · ×10Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:10
Test project verifies nothing: KeyBindingManagerTestsCore/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:10
What to do
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with SwiftFocusedCodeFinderTests.swift. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 10 No direct assertions finding(s) in Test Quality — start with TabToAcceptSuggestionTests.swift (10). — One of this dimension's main actionable groups (10 recommendation-level).
Resolve the 2 No assertions finding(s) in Test Quality — start with BreakLinePerformanceTests.swift, SourceEditorCachePerformanceTests.swift. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
24 outdated direct SwiftPM dependencies, 9 pinning defect(s). 34 of 61 direct dependencies had their releases listed (0 naming no readable repository, 27 pinned to a branch or a revision rather than a version). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 32 SwiftPM package(s) use a banned license. SwiftPM has no package registry, so each package's licence is the one its repository declares: 18 of them read from the licence file the repository carries at the revision REDACTED pins, and 14 — 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 REDACTED pins, direct and transitive, and every declared dependency none pins. 23 of them are declared by a manifest that commits no REDACTED (a library, whose resolution is its consumer's), so their own dependencies are resolved by whoever builds it and are not in this verdict. 1 of them declare no licence that matches a known SPDX licence; that is missing data, not a violation, and none of them is charged. ★ 6 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: `cgeventoverride`, `copilotforxcodekit`, `highlightr`, `keyboardshortcuts`, `languageclient`, `swiftui-flow-layout`. ★ COVERAGE OF THIS VERDICT: it grades this repository's SwiftPM package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
29 deducted task-comment markers across 73217 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
TodoComment · ×29Tool/Package.swift:73
What to do
Resolve the 29 TodoComment finding(s) in Explicit Debt — start with ChatService.swift (3), Package.swift (2), terminalAddon.ts (2). — One of this dimension's main actionable groups (29 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 5 document(s) read across 2 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
No ADRs foundCopilot for Xcode.xcodeproj/project.pbxproj:1
What to do
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
1 naming inconsistencies among 30 declarations measured against a convention their peers follow.
`originalMcpRegistryBaseURL` spells `Mcp` where 34 names in the project spell it `MCP`Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPRegistryURLSheet.swift:9
What to do
Resolve the 1 `originalMcpRegistryBaseURL` spells `Mcp` where 34 names in the project… finding(s) in Naming Consistency — start with MCPRegistryURLSheet.swift. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the namesServer/src/diffView/js/api.ts:105
What to do
Resolve the 2 redundant comment finding(s) in Comment Value — start with api.ts, terminalAddon.ts. — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
2 of 4 build units (SwiftPM, Xcode, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
18 % of calls cross a namespace and 15 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
semgrep found no security issues. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 278 of the 502 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
No dependency in any ecosystem this repository declares is published as malicious.
✓ On the Gold path — maintain.
Detailed fixes: d43_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Do you agree with this assessment?
AC3 · Page structure3.1 / 10Weak✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — Server/src/diffView/diffView.html:2, Server/src/terminal/terminal.html:2
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — Server/src/diffView/diffView.html:2
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — Server/src/terminal/terminal.html:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.action-button.secondary` sets color: #DFDEDF on background-color: #6E6D70 — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — Server/src/diffView/css/style.css:94
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Do you agree with this assessment?
DM4 · Rich vs anemic domain model10.0 / 10Exemplary✓ Tool-verified
Other · Domain Modelling — Whether domain entities own their behaviour — a data-only reference entity whose logic lives in a foreign service is anemic. Rich models enforce their own invariants.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
Other · Domain Modelling — Whether a reference entity protects its own invariants — a class whose identity is a computed content hash but whose hashed fields are publicly mutable bypasses that invariant. Encapsulated state keeps identity-bearing fields immutable.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
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.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Do you agree with this assessment?
P1 · CI/CD gates8.5 / 10Exemplary✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
What to do
Run the test suite in CI via an explicit runner step (`xcodebuild test` for the toolchain this pipeline already uses) and gate merges on it.
Do you agree with this assessment?
P10 · Library API & versioning9.8 / 10Exemplary✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
11 public types in `Tool~GitHubCopilotService` are marked as implementation by their own namespace, folder or name: `ClientToolHandlerImpl` (Tool/Sources/GitHubCopilotService/Conversation/ClientToolHandler.swift:13, name ends in `Impl`), `CompressionHandlerImpl` (Tool/Sources/GitHubCopilotService/Conversation/CompressionHandler.swift:9, name ends in `Impl`), `ConversationContextHandlerImpl` (Tool/Sources/GitHubCopilotService/Conversation/ConversationContextHandler.swift:9, name ends in `Impl`), `ConversationProgressHandlerImpl` (Tool/Sources/GitHubCopilotService/Conversation/ConversationProgressHandler.swift:18, name ends in `Impl`), `DynamicOAuthRequestHandlerImpl` (Tool/Sources/GitHubCopilotService/Conversation/DynamicOAuthRequestHandler.swift:15, name ends in `Impl`), `ShowMessageRequestHandlerImpl` (Tool/Sources/GitHubCopilotService/Conversation/ShowMessageRequestHandler.swift:17, name ends in `Impl`), `WatchedFilesHandlerImpl` (Tool/Sources/GitHubCopilotService/Conversation/WatchedFilesHandler.swift:13, name ends in `Impl`), `CopilotPolicyNotifierImpl` (Tool/Sources/GitHubCopilotService/Services/CopilotPolicyNotifier.swift:32, name ends in `Impl`), and 3 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — Tool/Sources/GitHubCopilotService/Conversation/ClientToolHandler.swift:13
What to do
Hide `Tool~GitHubCopilotService` (`ClientToolHandlerImpl`, `CompressionHandlerImpl`, `ConversationContextHandlerImpl`, `ConversationProgressHandlerImpl`, `DynamicOAuthRequestHandlerImpl`, `ShowMessageRequestHandlerImpl`, `WatchedFilesHandlerImpl`, `CopilotPolicyNotifierImpl`, and 3 more) (Swift: leave it `internal` (the default) instead of `public`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Do you agree with this assessment?
P2 · Observability0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
`.github/dependabot.yml` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — .github/dependabot.yml:2
What to do
Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
Server/src/diffView/js/ui-controller.ts:84 · Server/src/diffView/js/ui-controller.ts:108 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — Server/src/diffView/js/ui-controller.ts:84
Server/src/diffView/js/api.ts:82 · Server/src/diffView/js/monaco-diff-editor.ts:243 — the two spans are one implementation copied and then locally edited — 106 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — Server/src/diffView/js/api.ts:82
Server/src/terminal/terminalAddon.ts:93 · Server/src/terminal/terminalAddon.ts:132 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — Server/src/terminal/terminalAddon.ts:93
Server/src/diffView/js/monaco-diff-editor.ts:61 · Server/src/diffView/js/monaco-diff-editor.ts:243 — the two spans are one implementation copied and then locally edited — 56 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — Server/src/diffView/js/monaco-diff-editor.ts:61
Server/src/terminal/terminalAddon.ts:132 · Server/src/terminal/terminalAddon.ts:142 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — Server/src/terminal/terminalAddon.ts:132
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
handleSingleLine has cyclomatic complexity 12 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Server/src/terminal/terminalAddon.ts:125
Do you agree with this assessment?
R3 · Large Files10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling3.3 / 10Weak✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✗ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add a test runner (vitest / jest / playwright) and eslint as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in Server/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×5) — Tool/Sources/XcodeInspector/SourceEditor.swift:92, Tool/Sources/XcodeInspector/Apps/XcodeAppInstanceInspector.swift:416, Tool/Sources/SharedUIComponents/SyntaxHighlighting.swift:152, …
`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. (×8) — Tool/Sources/XPCShared/XPCService.swift:150, Tool/Sources/FileSystem/FileSystem.swift:871, Tool/Sources/FileSystem/FileSystem.swift:884, …
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 16 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 72 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
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 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
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 — AX6 reached only 1% of this repository's production lines — swift (68,513 lines), python (50 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
D11 Test Reliability — Test reliability not included — the .swift suite was found but not re-run
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
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.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Swift surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 61 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files).
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
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 Aggregate boundaries — not scored for Swift: the sidecar flattens array/collection types (a child COLLECTION = legitimate membership vs a single embedded aggregate is indistinguishable), and aggregate-vs-value-object classification cannot be told apart in source (every struct-holding-struct reads alike) — reported as guidance rather than measured
DM2 Strongly-typed ids — no in-repo typed-id idiom — primitive-obsession recorded as advisory DM8, DM2 not gated
DM3 Integration-event coupling — not scored for Swift: a cross-SwiftPM-target domain leak cannot be told apart in source from a legitimate shared-kernel/contracts module, and most repositories ship a single module — reported as guidance rather than measured
DM6 Domain ↔ infrastructure boundary — this Swift package maps no type to a persistence framework and declares no domain-model type carrying a method of its own, so DM6's domain↔infrastructure boundary read has no population to be taken over
DM7 Repository granularity — not scored for Swift: 'a repository per CHILD entity' needs the aggregate-root structure, which is not source-resolvable — reported as guidance rather than measured
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 — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python, Swift source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — the JS/TS workspace (6 production file(s)) has no JavaScript/TypeScript test, but it is 1.31% of this repository's production source and the other 98.69% carries 5,332 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
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.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X12 Unreachable branch — X12 reached only 1% of this repository's production lines — swift (68,513 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 1% of this repository's production lines — swift (68,513 lines), python (50 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — X18 reached only 1% of this repository's production lines — swift (68,513 lines), python (50 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X21 Side-effecting pattern guard — X21 reached only 1% of this repository's production lines — swift (68,513 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
<html> without a lang Server/src/diffView/diffView.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang Server/src/terminal/terminal.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC3 · Page structure· Document without a <title> · ×1
Document without a <title> Server/src/terminal/terminal.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
D10 · Test Quality· No assertions (empty test) · ×1
No assertions (empty test): test_selecting_a_line_in_freestanding_macro_the_scope_should_be_the_macro Tool/Tests/FocusedCodeFinderTests/SwiftFocusedCodeFinderTests.swift:345— Test method has an empty body — it asserts nothing and exercises no code.
TodoComment Tool/Package.swift:73— // TODO: Update LanguageClient some day. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Tool/Package.swift:85— // TODO: remove CopilotForXcodeKit dependency once extension provider logic is removed. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Tool/Tests/FocusedCodeFinderTests/SwiftFocusedCodeFinderTests.swift:346— // TODO: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:126— // TODO: How to get the `limit reached` error? Same as Code Completion? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Tool/Sources/Workspace/Filespace.swift:139— // TODO: should distinguish code completion and NES? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Tool/Sources/Workspace/WorkspaceFile.swift:287— // TODO: implement — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Tool/Sources/Workspace/FileChangeWatcher/BatchingFileChangeWatcher.swift:24— /// TODO: set a proper value for stdio — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Tool/Sources/SuggestionProvider/PostProcessingSuggestionServiceMiddleware.swift:34— // TODO: If need to check? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Tool/Sources/Persist/Storage/ConversationStorage/ConversationStorage.swift:228— // TODO: handle exception — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Core/Sources/PersistMiddleware/Extensions/ChatMessage+Storage.swift:128— // TODO: handle exception — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Tool/Sources/GitHubCopilotService/LanguageServer/CustomJSONRPCServerConnection.swift:41— // TODO? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Tool/Sources/GitHelper/CurrentChange.swift:65— // TODO: Handle cases of multi-project and referenced file — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Tool/Sources/Cache/AvatarCache.swift:27— // TODO: when the `agent` feature added, the avatarUrl could be obtained from the response of GitHub LSP — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Tool/Sources/AXExtension/AXUIElement.swift:264— /// - todo: Make it not recursive. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Server/src/terminal/terminalAddon.ts:259— // TODO: Could implement command history here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Server/src/terminal/terminalAddon.ts:263— // TODO: Could implement command history here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Core/Sources/SuggestionWidget/CodeReviewPanelView.swift:425— // TODO: dynamic set height by font size — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Core/Sources/SuggestionWidget/FeatureReducers/NESSuggestionPanelFeature.swift:24— // TODO: handle warnings — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:221— // TODO: handle errorMessage if any — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Core/Sources/LaunchAgentManager/LaunchAgentManager.swift:117— // TODO: A more robust way to locate the executable. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift:485— // TODO: Consider surfacing error to user — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerGalleryViewModel.swift:124— // TODO: Consider adding error handling UI feedback here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerGalleryViewModel.swift:139— // TODO: Consider adding error handling UI feedback here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Core/Sources/ConversationTab/Chat.swift:1339— // TODO: if we need to switch to agent mode or keep the current mode — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Core/Sources/ConversationTab/ConversationTab.swift:29— // TODO: modify tab title dynamicly — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Off the main sequence: ActiveApplicationMonitor — ActiveApplicationMonitor: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: AsyncPassthroughSubject — AsyncPassthroughSubject: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: Cache — Cache: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: CustomAsyncAlgorithms — CustomAsyncAlgorithms: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: DebounceFunction — DebounceFunction: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: FileChangeChecker — FileChangeChecker: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: NotificationCenterCoordinator — NotificationCenterCoordinator: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: UserDefaultsObserver — UserDefaultsObserver: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
Off the main sequence: SuggestionBasic — SuggestionBasic: abstractness 0.00, instability 0.06, distance 0.94 — zone of pain — concrete and depended on by 15 project(s), so it's rigid to change.
Off the main sequence: Logger — Logger: abstractness 0.11, instability 0.00, distance 0.89 — zone of pain — concrete and depended on by 21 project(s), so it's rigid to change.
Off the main sequence: AppActivator — AppActivator: abstractness 0.00, instability 0.14, distance 0.86 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: ChatTab — ChatTab: abstractness 0.14, instability 0.00, distance 0.86 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: Status — Status: abstractness 0.00, instability 0.18, distance 0.82 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.
Off the main sequence: SystemUtils — SystemUtils: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: Preferences — Preferences: abstractness 0.19, instability 0.05, distance 0.76 — zone of pain — concrete and depended on by 18 project(s), so it's rigid to change.
Off the main sequence: ConversationServiceProvider — ConversationServiceProvider: abstractness 0.03, instability 0.22, distance 0.75 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: LaunchAgentManager — LaunchAgentManager: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: Toast — Toast: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Low cohesion: View (LCOM4 30) Core/Sources/ConversationTab/Styles.swift:36— View's methods fall into 30 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 30 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: GitHubCopilotService (LCOM4 14) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:442— GitHubCopilotService's methods fall into 14 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 14 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: String (LCOM4 12) Core/Sources/HostApp/ToolsConfigView.swift:267— String's methods fall into 12 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 12 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AppDelegate (LCOM4 10) CommunicationBridge/main.swift:5— AppDelegate's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AppDelegate (LCOM4 10) ExtensionService/AppDelegate.swift:33— AppDelegate's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Array (LCOM4 7) Core/Sources/ChatService/ChatService.swift:1422— Array's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Filespace (LCOM4 7) Tool/Sources/Workspace/Filespace.swift:64— Filespace's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AXUIElement (LCOM4 6) Tool/Sources/AXExtension/AXUIElement+Xcode.swift:5— AXUIElement's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BuiltinExtensionSuggestionServiceProvider (LCOM4 5) Tool/Sources/BuiltinExtension/BuiltinExtensionSuggestionServiceProvider.swift:8— BuiltinExtensionSuggestionServiceProvider's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ChatService (LCOM4 4) Core/Sources/ChatService/ChatService.swift:63— ChatService's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Coordinator (LCOM4 4) Core/Sources/ConversationTab/DiffViews/DiffWebView.swift:97— Coordinator's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ChatPanelWindow (LCOM4 4) Core/Sources/SuggestionWidget/ChatPanelWindow.swift:9— ChatPanelWindow's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AutoManagedChatMemory (LCOM4 4) Tool/Sources/ChatAPIService/Memory/AutoManagedChatMemory.swift:17— AutoManagedChatMemory's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: StatusObserver (LCOM4 4) Tool/Sources/Status/StatusObserver.swift:4— StatusObserver's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AccountItemView (LCOM4 4) Tool/Sources/StatusBarItemView/AccountItemView.swift:4— AccountItemView's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
MethodTooLong: Chat.body Core/Sources/ConversationTab/Chat.swift:689— MethodTooLong — body runs 560 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 460 over it, 5.60× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ChatPanelFeature.body Core/Sources/SuggestionWidget/FeatureReducers/ChatPanelFeature.swift:210— MethodTooLong — body runs 251 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 151 over it, 2.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WidgetFeature.body Core/Sources/SuggestionWidget/FeatureReducers/WidgetFeature.swift:145— MethodTooLong — body runs 214 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 114 over it, 2.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: XcodeThemeParser.parseXCColorTheme Core/Sources/XcodeThemeController/XcodeThemeParser.swift:116— MethodTooLong — parseXCColorTheme runs 175 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LanguageIdentifier.fileExtensions Tool/Sources/SuggestionBasic/LanguageIdentifierFromFilePath.swift:51— MethodTooLong — fileExtensions runs 132 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PanelFeature.body Core/Sources/SuggestionWidget/FeatureReducers/PanelFeature.swift:80— MethodTooLong — body runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GUI.body Core/Sources/Service/GUI/GraphicalUserInterfaceController.swift:65— MethodTooLong — body runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FixErrorPanelFeature.body Core/Sources/SuggestionWidget/FeatureReducers/FixErrorPanelFeature.swift:87— MethodTooLong — body runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ModelPickerDetailPanel.show Core/Sources/ConversationTab/ModeAndModelPicker/ModelPicker/ModelPickerDetailPanel.swift:398— MethodTooLong — show runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InputAreaTextEditor.body Core/Sources/ConversationTab/Views/ChatPanelInputArea/InputAreaTextEditor.swift:90— MethodTooLong — body runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppDelegate.buildStatusBarMenu ExtensionService/AppDelegate+Menu.swift:24— MethodTooLong — buildStatusBarMenu runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: HorizontalMovable.framesForWindows Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:197— MethodTooLong — framesForWindows runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CustomJSONRPCServerConnection.sendRequest Tool/Sources/GitHubCopilotService/LanguageServer/CustomJSONRPCServerConnection.swift:88— MethodTooLong — sendRequest runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FileTooLong: LanguageServer/GitHubCopilotService.swift Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift— FileTooLong — 1143 significant lines (blank, comment-only and punctuation-only lines excluded), about 70% of them inside a single declaration: GitHubCopilotService (442-1606). The bar is 500 significant lines; this is 643 over it, 2.29× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: ConversationTab/Chat.swift Core/Sources/ConversationTab/Chat.swift— FileTooLong — 1095 significant lines (blank, comment-only and punctuation-only lines excluded), about 82% of them inside a single declaration: Chat (180-1502). The bar is 500 significant lines; this is 595 over it, 2.19× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: ChatService/ChatService.swift Core/Sources/ChatService/ChatService.swift— FileTooLong — 1045 significant lines (blank, comment-only and punctuation-only lines excluded), about 74% of them inside a single declaration: ChatService (63-1310). The bar is 500 significant lines; this is 545 over it, 2.09× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: SuggestionWidget/WidgetWindowsController.swift Core/Sources/SuggestionWidget/WidgetWindowsController.swift— FileTooLong — 942 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 442 over it, 1.88× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: SuggestionWidget/AgentConfigurationWidgetView.swift Core/Sources/SuggestionWidget/AgentConfigurationWidgetView.swift— FileTooLong — 792 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: AgentConfigurationWidgetView (25-1190). The bar is 500 significant lines; this is 292 over it, 1.58× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: ConversationServiceProvider/LSPTypes.swift Tool/Sources/ConversationServiceProvider/LSPTypes.swift— FileTooLong — 586 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 86 over it, 1.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: XPCShared/XPCExtensionService.swift Tool/Sources/XPCShared/XPCExtensionService.swift— FileTooLong — 586 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 86 over it, 1.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: GitHubCopilotRequestTypes/MCPRegistry.swift Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift— FileTooLong — 538 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 38 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ConversationTab/ChatPanel.swift Core/Sources/ConversationTab/ChatPanel.swift— FileTooLong — 530 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 30 over it, 1.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Service/XPCService.swift Core/Sources/Service/XPCService.swift— FileTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: XPCService (15-766). The bar is 500 significant lines; this is 13 over it, 1.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: StatusBarItemView/QuotaView.swift Tool/Sources/StatusBarItemView/QuotaView.swift— FileTooLong — 505 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 5 over it, 1.01× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×10
Edited copy of a member (12 corresponding lines) Tool/Sources/Preferences/Types/AutoApprovedMCPServers.swift:20— Tool/Sources/Preferences/Types/AutoApprovedMCPServers.swift:20-35 | Tool/Sources/Preferences/Types/SensitiveFilesRules.swift:20-31 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) Tool/Sources/ConversationServiceProvider/LSPTypes+AgentRound.swift:118— Tool/Sources/ConversationServiceProvider/LSPTypes+AgentRound.swift:118-129 | Tool/Sources/ConversationServiceProvider/LSPTypes+AgentRound.swift:168-179 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:917— Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:917-928 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:1219-1242 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) Core/Sources/ChatService/ToolCalls/AutoApproval/MCPApprovalStorage.swift:41— Core/Sources/ChatService/ToolCalls/AutoApproval/MCPApprovalStorage.swift:41-52 | Core/Sources/ChatService/ToolCalls/AutoApproval/MCPApprovalStorage.swift:66-77 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) ExtensionService/AppDelegate+Menu.swift:313— ExtensionService/AppDelegate+Menu.swift:313-324 | ExtensionService/AppDelegate+Menu.swift:326-337 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) Tool/Sources/BuiltinExtension/BuiltinExtensionSuggestionServiceProvider.swift:42— Tool/Sources/BuiltinExtension/BuiltinExtensionSuggestionServiceProvider.swift:42-54 | Tool/Sources/BuiltinExtension/BuiltinExtensionSuggestionServiceProvider.swift:56-67 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) Core/Sources/ConversationTab/Chat.swift:1554— Core/Sources/ConversationTab/Chat.swift:1554-1565 | Tool/Sources/CustomAsyncAlgorithms/TimedDebounce.swift:16-28 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) Tool/Sources/Persist/Storage/ConversationStorageService.swift:87— Tool/Sources/Persist/Storage/ConversationStorageService.swift:87-98 | Tool/Sources/Persist/Storage/ConversationStorageService.swift:114-126 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) Core/Sources/ConversationTab/ModeAndModelPicker/ModePicker/AgentModeButtonMenuItem.swift:354— Core/Sources/ConversationTab/ModeAndModelPicker/ModePicker/AgentModeButtonMenuItem.swift:354-365 | Core/Sources/ConversationTab/ModeAndModelPicker/ModePicker/AgentModeButtonMenuItem.swift:367-378 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) ExtensionService/AppDelegate.swift:292— ExtensionService/AppDelegate.swift:292-303 | ExtensionService/AppDelegate.swift:401-413 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Floating branch dependency: keyboardshortcuts — Dependency `keyboardshortcuts` is declared in Core/Package.swift against branch `main` — the declaration pins no immutable point, so `swift package update` moves this dependency to whatever that branch holds at the time, which is code nobody reviewed. Pin it to a version requirement (`from:`, `.upToNextMajor(from:)`, `exact:`) or to a `revision:` commit SHA.
Floating branch dependency: cgeventoverride — Dependency `cgeventoverride` is declared in Core/Package.swift against branch `devm33/fix-stale-AXIsProcessTrusted` — the declaration pins no immutable point, so `swift package update` moves this dependency to whatever that branch holds at the time, which is code nobody reviewed. Pin it to a version requirement (`from:`, `.upToNextMajor(from:)`, `exact:`) or to a `revision:` commit SHA.
Floating branch dependency: highlightr — Dependency `highlightr` is declared in Core/Package.swift against branch `master` — the declaration pins no immutable point, so `swift package update` moves this dependency to whatever that branch holds at the time, which is code nobody reviewed. Pin it to a version requirement (`from:`, `.upToNextMajor(from:)`, `exact:`) or to a `revision:` commit SHA.
Floating branch dependency: highlightr — Dependency `highlightr` is declared in Tool/Package.swift against branch `master` — the declaration pins no immutable point, so `swift package update` moves this dependency to whatever that branch holds at the time, which is code nobody reviewed. Pin it to a version requirement (`from:`, `.upToNextMajor(from:)`, `exact:`) or to a `revision:` commit SHA.
Floating branch dependency: copilotforxcodekit — Dependency `copilotforxcodekit` is declared in Tool/Package.swift against branch `main` — the declaration pins no immutable point, so `swift package update` moves this dependency to whatever that branch holds at the time, which is code nobody reviewed. Pin it to a version requirement (`from:`, `.upToNextMajor(from:)`, `exact:`) or to a `revision:` commit SHA.
Floating branch dependency: cgeventoverride — Dependency `cgeventoverride` is resolved in REDACTED against branch `devm33/fix-stale-AXIsProcessTrusted` rather than a released version — the project pins no immutable point, so resolving the packages again moves this dependency to whatever that branch holds at the time. Change the dependency rule in Xcode to a version requirement, or to an exact commit.
Floating branch dependency: copilotforxcodekit — Dependency `copilotforxcodekit` is resolved in REDACTED against branch `main` rather than a released version — the project pins no immutable point, so resolving the packages again moves this dependency to whatever that branch holds at the time. Change the dependency rule in Xcode to a version requirement, or to an exact commit.
Floating branch dependency: highlightr — Dependency `highlightr` is resolved in REDACTED against branch `master` rather than a released version — the project pins no immutable point, so resolving the packages again moves this dependency to whatever that branch holds at the time. Change the dependency rule in Xcode to a version requirement, or to an exact commit.
Floating branch dependency: keyboardshortcuts — Dependency `keyboardshortcuts` is resolved in REDACTED against branch `main` rather than a released version — the project pins no immutable point, so resolving the packages again moves this dependency to whatever that branch holds at the time. Change the dependency rule in Xcode to a version requirement, or to an exact commit.
TooManyMethods: ChatService Core/Sources/ChatService/ChatService.swift:63— TooManyMethods — 67 methods, declared across 4 files: ChatService/ChatService.swift (58), Extensions/ChatService+FileEdit.swift (5), ToolCalls/ClientToolConfirmationEventHandler.swift (3), ToolCalls/ICopilotTool.swift (1). The bar is 30 methods; this is 37 over it, 2.23× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: GitHubCopilotService Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:442— TooManyMethods — 67 methods. The bar is 30 methods; this is 37 over it, 2.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: XPCExtensionService Tool/Sources/XPCShared/XPCExtensionService.swift:34— TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: XPCService Core/Sources/Service/XPCService.swift:15— TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. Most of these members implement Tool~XPCShared.XPCServiceProtocol (43 of 44 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: WidgetWindowsController Core/Sources/SuggestionWidget/WidgetWindowsController.swift:12— TooManyMethods — 43 methods, declared across 5 files: SuggestionWidget/WidgetWindowsController.swift (26), Extensions/WidgetWindowsController+NES.swift (7), Extensions/WidgetWindowsController+FixErrorPanel.swift (5), Extensions/WidgetWindowsController+AgentConfigurationWidget.swift (3), +1 more file(s). The bar is 30 methods; this is 13 over it, 1.43× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: QuotaView Tool/Sources/StatusBarItemView/QuotaView.swift:6— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: View Core/Sources/ConversationTab/Styles.swift:36— TooManyMethods — 35 methods, declared across 20 files: ConversationTab/ViewExtension.swift (8), ConversationTab/Styles.swift (4), ScaledComponent/ScaledModifier.swift (3), ConversationAgentProgressView/ToolStatusItemView.swift (2), +16 more file(s). The bar is 30 methods; this is 5 over it, 1.17× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ToolAutoApprovalManager Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalManager.swift:3— TooManyMethods — 33 methods, declared across 2 files: AutoApproval/ToolAutoApprovalManager.swift (20), AutoApproval/ToolAutoApprovalParsingHelpers.swift (13). The bar is 30 methods; this is 3 over it, 1.10× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×8
Edited copy of a member (11 corresponding lines) Tool/Sources/StatusBarItemView/QuotaView.swift:333— Tool/Sources/StatusBarItemView/QuotaView.swift:333-343 | Tool/Sources/StatusBarItemView/QuotaView.swift:345-356 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) Tool/Sources/ChatTab/ChatTab.swift:41— Tool/Sources/ChatTab/ChatTab.swift:41-52 | Tool/Sources/ChatTab/ChatTab.swift:55-65 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) Core/Sources/SuggestionWidget/NES/NESDiffView.swift:78— Core/Sources/SuggestionWidget/NES/NESDiffView.swift:78-91 | Core/Sources/SuggestionWidget/NES/NESDiffView.swift:113-123 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift:201— Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift:201-211 | Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift:251-264 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) Tool/Sources/GitHubCopilotService/GitHubCopilotExtension.swift:70— Tool/Sources/GitHubCopilotService/GitHubCopilotExtension.swift:70-80 | Tool/Sources/GitHubCopilotService/GitHubCopilotExtension.swift:82-92 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) Tool/Sources/WorkspaceSuggestionService/SuggestionWorkspacePlugin.swift:32— Tool/Sources/WorkspaceSuggestionService/SuggestionWorkspacePlugin.swift:32-49 | Tool/Sources/WorkspaceSuggestionService/SuggestionWorkspacePlugin.swift:51-61 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) Core/Sources/SuggestionWidget/AgentConfigurationWidgetView.swift:288— Core/Sources/SuggestionWidget/AgentConfigurationWidgetView.swift:288-298 | Core/Sources/SuggestionWidget/AgentConfigurationWidgetView.swift:1159-1173 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) Tool/Sources/ConversationServiceProvider/LSPTypes.swift:232— Tool/Sources/ConversationServiceProvider/LSPTypes.swift:232-242 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCP.swift:164-174 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Swallowed exception (caught, then discarded) Tool/Sources/XPCShared/XPCService.swift:150— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Tool/Sources/FileSystem/FileSystem.swift:871— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Tool/Sources/FileSystem/FileSystem.swift:884— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Tool/Sources/FileSystem/FileSystem.swift:897— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Tool/Sources/FileSystem/FileSystem.swift:910— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Tool/Sources/Cache/AvatarCache.swift:35— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift:399— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Core/Sources/HostApp/ToolsSettings/MCPRegistry/ServerInstallationOptionView.swift:168— `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.
ClassTooLong: Chat Core/Sources/ConversationTab/Chat.swift:179— ClassTooLong — 896 significant lines (blank, comment-only and punctuation-only lines excluded), 0 methods. The bar is 400 significant lines; this is 496 over it, 2.24× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: GitHubCopilotService Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:442— ClassTooLong — 805 significant lines (blank, comment-only and punctuation-only lines excluded), 67 methods. The bar is 400 significant lines; this is 405 over it, 2.01× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ChatService Core/Sources/ChatService/ChatService.swift:63— ClassTooLong — 775 significant lines (blank, comment-only and punctuation-only lines excluded), 67 methods. The bar is 400 significant lines; this is 375 over it, 1.94× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AgentConfigurationWidgetView Core/Sources/SuggestionWidget/AgentConfigurationWidgetView.swift:25— ClassTooLong — 773 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 373 over it, 1.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: XPCService Core/Sources/Service/XPCService.swift:15— ClassTooLong — 496 significant lines (blank, comment-only and punctuation-only lines excluded), 44 methods. The bar is 400 significant lines; this is 96 over it, 1.24× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: InputAreaTextEditor Core/Sources/ConversationTab/Views/ChatPanelInputArea/InputAreaTextEditor.swift:18— ClassTooLong — 441 significant lines (blank, comment-only and punctuation-only lines excluded), 12 methods. The bar is 400 significant lines; this is 41 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ModelPickerDetailPanel Core/Sources/ConversationTab/ModeAndModelPicker/ModelPicker/ModelPickerDetailPanel.swift:30— ClassTooLong — 436 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 36 over it, 1.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×7
Edited copy of a member (13 corresponding lines) Tool/Sources/ConversationServiceProvider/LSPTypes+AgentRound.swift:104— Tool/Sources/ConversationServiceProvider/LSPTypes+AgentRound.swift:104-116 | Tool/Sources/ConversationServiceProvider/LSPTypes+AgentRound.swift:154-166 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) Core/Sources/Service/XPCService.swift:441— Core/Sources/Service/XPCService.swift:441-453 | Core/Sources/Service/XPCService.swift:610-623 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) Tool/Sources/Workspace/FileChangeWatcher/FileChangeWatcherService.swift:149— Tool/Sources/Workspace/FileChangeWatcher/FileChangeWatcherService.swift:149-164 | Tool/Sources/Workspace/FileChangeWatcher/FileChangeWatcherService.swift:166-178 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) Core/Sources/SuggestionWidget/NES/NESDiffView.swift:62— Core/Sources/SuggestionWidget/NES/NESDiffView.swift:62-76 | Core/Sources/SuggestionWidget/NES/NESDiffView.swift:99-111 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) Core/Sources/ChatService/ToolCalls/AutoApproval/MCPApprovalStorage.swift:120— Core/Sources/ChatService/ToolCalls/AutoApproval/MCPApprovalStorage.swift:120-132 | Core/Sources/ChatService/ToolCalls/AutoApproval/MCPApprovalStorage.swift:134-146 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPRegistryURLInputField.swift:22— Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPRegistryURLInputField.swift:22-36 | Tool/Sources/Workspace/FileChangeWatcher/SingleFileWatcher.swift:15-27 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) CommunicationBridge/ServiceDelegate.swift:7— CommunicationBridge/ServiceDelegate.swift:7-22 | ExtensionService/ServiceDelegate.swift:6-18 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×7
Edited copy of a member (9 corresponding lines) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:341— Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:341-349 | Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:351-359 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) Tool/Sources/Workspace/OpenedFileRocoverableStorage.swift:13— Tool/Sources/Workspace/OpenedFileRocoverableStorage.swift:13-21 | Tool/Sources/Workspace/OpenedFileRocoverableStorage.swift:23-31 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) Core/Sources/ChatService/ToolCalls/AutoApproval/SensitiveFileApprovalStorage.swift:33— Core/Sources/ChatService/ToolCalls/AutoApproval/SensitiveFileApprovalStorage.swift:33-45 | Core/Sources/ChatService/ToolCalls/AutoApproval/SensitiveFileApprovalStorage.swift:64-72 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) Tool/Sources/StatusBarItemView/AccountItemView.swift:115— Tool/Sources/StatusBarItemView/AccountItemView.swift:115-123 | Tool/Sources/StatusBarItemView/AccountItemView.swift:125-133 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) Tool/Sources/Persist/Storage/ConversationStorage/Model.swift:12— Tool/Sources/Persist/Storage/ConversationStorage/Model.swift:12-20 | Tool/Sources/Persist/Storage/ConversationStorage/Model.swift:32-40 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) Core/Sources/ConversationTab/ChatContextMenu.swift:45— Core/Sources/ConversationTab/ChatContextMenu.swift:45-53 | Core/Sources/ConversationTab/ChatContextMenu.swift:56-64 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) Tool/Sources/ConversationServiceProvider/ConversationServiceProvider.swift:294— Tool/Sources/ConversationServiceProvider/ConversationServiceProvider.swift:294-302 | Tool/Sources/TelemetryServiceProvider/TelemetryServiceProvider.swift:143-151 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (8 lines × 2) Core/Sources/ConversationTab/ChatPanel.swift:627— Core/Sources/ConversationTab/ChatPanel.swift:627-634 | Core/Sources/ConversationTab/Views/WorkingSetView.swift:38-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/ConversationTab/ChatPanel.swift:627` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Core/Sources/ConversationTab/ChatPanel.swift:635` calls `padding` and `Core/Sources/ConversationTab/Views/WorkingSetView.swift:46` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) Core/Sources/ConversationTab/Styles.swift:7— Core/Sources/ConversationTab/Styles.swift:7-14 | Core/Sources/ConversationTab/Styles.swift:16-23 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:92— Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:92-99 | Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:166-173 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) Tool/Sources/ConversationServiceProvider/LSPTypes+AgentRound.swift:104— Tool/Sources/ConversationServiceProvider/LSPTypes+AgentRound.swift:104-111 | Tool/Sources/ConversationServiceProvider/LSPTypes+AgentRound.swift:154-161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/ConversationServiceProvider/LSPTypes+AgentRound.swift:104` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:342— Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:342-349 | Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:352-359 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) Core/Sources/ChatService/ToolCalls/AutoApproval/MCPApprovalStorage.swift:79— Core/Sources/ChatService/ToolCalls/AutoApproval/MCPApprovalStorage.swift:79-86 | Core/Sources/ChatService/ToolCalls/AutoApproval/SensitiveFileApprovalStorage.swift:74-81 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) Core/Sources/UserDefaultsObserver/UserDefaultsObserver.swift:27— Core/Sources/UserDefaultsObserver/UserDefaultsObserver.swift:27-34 | Tool/Sources/UserDefaultsObserver/UserDefaultsObserver.swift:27-34 — before extracting anything, compare `Core/Sources/UserDefaultsObserver/UserDefaultsObserver.swift` and `Tool/Sources/UserDefaultsObserver/UserDefaultsObserver.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) Core/Sources/ConversationTab/Chat.swift:77— Core/Sources/ConversationTab/Chat.swift:77-89 | Tool/Sources/ChatAPIService/Models.swift:230-242 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note what the matched lines are: every one of them assigns one field to another, so the block is a hand-written mapper between two data shapes rather than behaviour with a helper inside it. Extracting one shared function only works if both sites map the SAME pair of types in the same direction — check that first, because inverse or differently-typed mappers have no single function they can both call. Where they do not, the moves that exist are a generated or reflective mapper, a common embedded/base type the fields live on once, or accepting the run and covering it with a test that fails when a field is added to one side only.
Duplicated block (13 lines × 2) Core/Sources/HostApp/ToolsSettings/BuiltInToolsListView.swift:58— Core/Sources/HostApp/ToolsSettings/BuiltInToolsListView.swift:58-70 | Core/Sources/HostApp/ToolsSettings/MCPToolsListView.swift:21-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) Core/Sources/SuggestionWidget/ChatWindow/ChatNoAXPermissionView.swift:8— Core/Sources/SuggestionWidget/ChatWindow/ChatNoAXPermissionView.swift:8-20 | Core/Sources/SuggestionWidget/ChatWindow/ChatNoSubscriptionView.swift:10-22 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/SuggestionWidget/ChatWindow/ChatNoAXPermissionView.swift:8` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/Telemetry.swift:11— Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/Telemetry.swift:11-23 | Tool/Sources/TelemetryServiceProvider/TelemetryServiceProvider.swift:29-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:170— Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:170-182 | Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:195-207 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:170` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) Core/Sources/HostApp/SidebarTabView.swift:37— Core/Sources/HostApp/SidebarTabView.swift:37-49 | Core/Sources/HostApp/TabContainer.swift:162-174 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) Core/Sources/ConversationTab/ModeAndModelPicker/ModePicker/AgentModeButton.swift:46— Core/Sources/ConversationTab/ModeAndModelPicker/ModePicker/AgentModeButton.swift:46-55 | Core/Sources/ConversationTab/ModeAndModelPicker/ModelPicker/ModelPickerButton.swift:18-27 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) Core/Sources/HostApp/ToolsSettings/BuiltInToolsListView.swift:178— Core/Sources/HostApp/ToolsSettings/BuiltInToolsListView.swift:178-187 | Core/Sources/HostApp/ToolsSettings/MCPServerToolsSection.swift:419-428 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/HostApp/ToolsSettings/BuiltInToolsListView.swift:178` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) Core/Sources/Service/Service.swift:172— Core/Sources/Service/Service.swift:172-181 | Tool/Sources/Workspace/WorkspaceFile.swift:184-193 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) Core/Sources/Service/XPCService.swift:349— Core/Sources/Service/XPCService.swift:349-358 | Core/Sources/Service/XPCService.swift:495-504 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/Service/XPCService.swift:349` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Core/Sources/Service/XPCService.swift:505` calls `JSONEncoder`, `encode`, `reply` and `Core/Sources/Service/XPCService.swift:359` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) Tool/Sources/SuggestionProvider/PostProcessingSuggestionServiceMiddleware.swift:8— Tool/Sources/SuggestionProvider/PostProcessingSuggestionServiceMiddleware.swift:8-17 | Tool/Sources/SuggestionProvider/PostProcessingSuggestionServiceMiddleware.swift:24-33 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/SuggestionProvider/PostProcessingSuggestionServiceMiddleware.swift:8` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Tool/Sources/SuggestionProvider/PostProcessingSuggestionServiceMiddleware.swift:18` calls `checkIfSuggestionHasNoEffect` and `Tool/Sources/SuggestionProvider/PostProcessingSuggestionServiceMiddleware.swift:36` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) Tool/Sources/TelemetryService/TelemetryService.swift:76— Tool/Sources/TelemetryService/TelemetryService.swift:76-85 | Tool/Sources/TelemetryService/TelemetryService.swift:101-110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/TelemetryService/TelemetryService.swift:76` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×5
Edited copy of a member (16 corresponding lines) Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift:278— Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift:278-293 | Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift:317-332 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) Tool/Sources/StatusBarItemView/QuotaView.swift:529— Tool/Sources/StatusBarItemView/QuotaView.swift:529-552 | Tool/Sources/StatusBarItemView/QuotaView.swift:563-578 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) Core/Sources/HostApp/ToolsSettings/CopilotBuiltInToolManagerObservable.swift:14— Core/Sources/HostApp/ToolsSettings/CopilotBuiltInToolManagerObservable.swift:14-29 | Core/Sources/HostApp/ToolsSettings/CopilotMCPToolManagerObservable.swift:14-31 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) Tool/Sources/Logger/Logger.swift:112— Tool/Sources/Logger/Logger.swift:112-127 | Tool/Sources/Logger/Logger.swift:129-145 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) EditorExtension/OpenChat.swift:9— EditorExtension/OpenChat.swift:9-24 | EditorExtension/ToggleRealtimeSuggestionsCommand.swift:9-24 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×5
Edited copy of a member (17 corresponding lines) Core/Sources/Service/GUI/GraphicalUserInterfaceController.swift:450— Core/Sources/Service/GUI/GraphicalUserInterfaceController.swift:450-467 | Core/Sources/Service/GUI/GraphicalUserInterfaceController.swift:469-485 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) Core/Sources/ConversationTab/ModeAndModelPicker/ModePicker/AgentModeButton.swift:258— Core/Sources/ConversationTab/ModeAndModelPicker/ModePicker/AgentModeButton.swift:258-274 | Core/Sources/ConversationTab/ModeAndModelPicker/ModePicker/AgentModeButtonMenuItem.swift:228-244 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:230— Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:230-246 | Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:248-264 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) Core/Sources/HostApp/ToolsSettings/AutoApprove/AutoApprovalDisableView.swift:8— Core/Sources/HostApp/ToolsSettings/AutoApprove/AutoApprovalDisableView.swift:8-24 | Core/Sources/HostApp/ToolsSettings/MCPIntroView.swift:14-34 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) Core/Sources/Service/TelemetryLogger.swift:6— Core/Sources/Service/TelemetryLogger.swift:6-22 | Core/Sources/Service/TelemetryLogger.swift:24-41 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×5
Edited copy of a member (8 corresponding lines) Core/Sources/HostApp/SharedComponents/Badge.swift:42— Core/Sources/HostApp/SharedComponents/Badge.swift:42-49 | Core/Sources/HostApp/SharedComponents/Badge.swift:51-58 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) Tool/Sources/AXExtension/AXUIElement.swift:297— Tool/Sources/AXExtension/AXUIElement.swift:297-304 | Tool/Sources/AXExtension/AXUIElement.swift:306-322 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) Core/Sources/HostApp/ToolsSettings/AppState+LanguageModelTools.swift:8— Core/Sources/HostApp/ToolsSettings/AppState+LanguageModelTools.swift:8-15 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:1395-1402 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) Tool/Sources/GitHubCopilotService/Services/CopilotPolicyNotifier.swift:45— Tool/Sources/GitHubCopilotService/Services/CopilotPolicyNotifier.swift:45-52 | Tool/Sources/GitHubCopilotService/Services/FeatureFlagNotifier.swift:111-119 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) Core/Sources/HostApp/ToolsSettings/BuiltInToolsListView.swift:116— Core/Sources/HostApp/ToolsSettings/BuiltInToolsListView.swift:116-125 | Core/Sources/HostApp/ToolsSettings/MCPServerToolsSection.swift:309-316 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (9 lines × 2) Core/Sources/HostApp/BYOKSettings/ApiKeySheet.swift:67— Core/Sources/HostApp/BYOKSettings/ApiKeySheet.swift:67-75 | Core/Sources/HostApp/BYOKSettings/ProviderConfigView.swift:162-171 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/HostApp/BYOKSettings/ApiKeySheet.swift:67` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) Core/Sources/Service/GUI/GraphicalUserInterfaceController.swift:459— Core/Sources/Service/GUI/GraphicalUserInterfaceController.swift:459-467 | Core/Sources/Service/GUI/GraphicalUserInterfaceController.swift:477-485 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/Service/GUI/GraphicalUserInterfaceController.swift:459` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) Core/Sources/Service/SuggestionCommandHandler/WindowBaseCommandHandler.swift:178— Core/Sources/Service/SuggestionCommandHandler/WindowBaseCommandHandler.swift:178-186 | Core/Sources/Service/SuggestionCommandHandler/WindowBaseCommandHandler.swift:215-223 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) Tool/Sources/StatusBarItemView/QuotaView.swift:335— Tool/Sources/StatusBarItemView/QuotaView.swift:335-343 | Tool/Sources/StatusBarItemView/QuotaView.swift:348-356 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/StatusBarItemView/QuotaView.swift:335` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (9 lines × 2) Tool/Sources/StatusBarItemView/QuotaView.swift:596— Tool/Sources/StatusBarItemView/QuotaView.swift:596-604 | Tool/Sources/StatusBarItemView/QuotaView.swift:624-632 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/StatusBarItemView/QuotaView.swift:596` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift:296— Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift:296-301 | Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift:335-340 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift:304— Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift:304-309 | Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift:343-348 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) Tool/Sources/XPCShared/XPCExtensionService.swift:430— Tool/Sources/XPCShared/XPCExtensionService.swift:430-435 | Tool/Sources/XPCShared/XPCExtensionService.swift:584-589 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/XPCShared/XPCExtensionService.swift:430` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) Core/Sources/ChatService/ChatService.swift:897— Core/Sources/ChatService/ChatService.swift:897-902 | Core/Sources/ChatService/ChatService.swift:932-937 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/ChatService/ChatService.swift:897` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) Core/Sources/ConversationTab/ModeAndModelPicker/ModelPicker/ModelPickerDetailPanel.swift:279— Core/Sources/ConversationTab/ModeAndModelPicker/ModelPicker/ModelPickerDetailPanel.swift:279-284 | Core/Sources/ConversationTab/ModeAndModelPicker/ModelPicker/ModelPickerDetailPanel.swift:369-374 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPRegistryInstallation.swift:395— Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPRegistryInstallation.swift:395-399 | Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPRegistryInstallation.swift:412-416 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPRegistryInstallation.swift:395` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) Tool/Sources/SharedUIComponents/QuotaPopoverView.swift:150— Tool/Sources/SharedUIComponents/QuotaPopoverView.swift:150-154 | Tool/Sources/StatusBarItemView/QuotaView.swift:670-674 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) Tool/Sources/Workspace/WorkspaceDirectoryIndex.swift:61— Tool/Sources/Workspace/WorkspaceDirectoryIndex.swift:61-65 | Tool/Sources/Workspace/WorkspaceFileIndex.swift:55-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:155— Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:155-159 | Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:206-210 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:155` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:488— Core/Sources/SuggestionWidget/WidgetWindowsController.swift:488-492 | Core/Sources/SuggestionWidget/WidgetWindowsController.swift:516-520 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Swallowed exception (empty catch) Tool/Sources/XcodeInspector/SourceEditor.swift:92— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Tool/Sources/XcodeInspector/Apps/XcodeAppInstanceInspector.swift:416— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Tool/Sources/SharedUIComponents/SyntaxHighlighting.swift:152— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift:484— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift:124— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×4
Edited copy of a member (23 corresponding lines) Core/Sources/SuggestionWidget/ChatWindow/ChatHistoryView.swift:259— Core/Sources/SuggestionWidget/ChatWindow/ChatHistoryView.swift:259-281 | Core/Sources/SuggestionWidget/ChatWindowView.swift:689-714 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) Core/Sources/ConversationTab/TerminalViews/RunInTerminalToolView.swift:47— Core/Sources/ConversationTab/TerminalViews/RunInTerminalToolView.swift:47-69 | Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:16-39 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) Tool/Sources/TelemetryService/TelemetryService.swift:74— Tool/Sources/TelemetryService/TelemetryService.swift:74-96 | Tool/Sources/TelemetryService/TelemetryService.swift:99-121 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) Core/Sources/SuggestionWidget/Extensions/WidgetWindowsController+FixErrorPanel.swift:25— Core/Sources/SuggestionWidget/Extensions/WidgetWindowsController+FixErrorPanel.swift:25-47 | Core/Sources/SuggestionWidget/WidgetWindowsController.swift:108-130 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×4
Edited copy of a member (22 corresponding lines) Tool/Sources/GitHubCopilotService/Services/GitHubCopilotConversationService.swift:43— Tool/Sources/GitHubCopilotService/Services/GitHubCopilotConversationService.swift:43-65 | Tool/Sources/GitHubCopilotService/Services/GitHubCopilotConversationService.swift:67-88 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift:77— Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift:77-98 | Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift:100-121 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) Core/Sources/ConversationTab/ModeAndModelPicker/ModePicker/AgentModeMenu.swift:83— Core/Sources/ConversationTab/ModeAndModelPicker/ModePicker/AgentModeMenu.swift:83-104 | Core/Sources/ConversationTab/ModeAndModelPicker/ModePicker/AgentModeMenu.swift:106-137 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) Tool/Sources/Workspace/WorkspaceDirectoryIndex.swift:33— Tool/Sources/Workspace/WorkspaceDirectoryIndex.swift:33-58 | Tool/Sources/Workspace/WorkspaceFileIndex.swift:31-52 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×4
Edited copy of a member (6 corresponding lines) Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift:395— Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift:395-402 | Core/Sources/HostApp/ToolsSettings/MCPRegistry/ServerInstallationOptionView.swift:164-169 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) Tool/Sources/GitHubCopilotService/Services/GitHubCopilotConversationService.swift:112— Tool/Sources/GitHubCopilotService/Services/GitHubCopilotConversationService.swift:112-117 | Tool/Sources/GitHubCopilotService/Services/GitHubCopilotConversationService.swift:119-126 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) Core/Sources/SuggestionWidget/AgentConfigurationWidgetView.swift:644— Core/Sources/SuggestionWidget/AgentConfigurationWidgetView.swift:644-649 | Core/Sources/SuggestionWidget/AgentConfigurationWidgetView.swift:837-843 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) Tool/Sources/Preferences/UserDefaults.swift:146— Tool/Sources/Preferences/UserDefaults.swift:146-151 | Tool/Sources/Preferences/UserDefaults.swift:293-299 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (12 lines × 2) Core/Sources/ConversationTab/TerminalViews/RunInTerminalToolView.swift:57— Core/Sources/ConversationTab/TerminalViews/RunInTerminalToolView.swift:57-68 | Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:26-37 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/ConversationTab/TerminalViews/RunInTerminalToolView.swift:57` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) Core/Sources/ConversationTab/Views/BotMessage.swift:290— Core/Sources/ConversationTab/Views/BotMessage.swift:290-301 | Core/Sources/ConversationTab/Views/BotMessage.swift:303-314 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `spacing` to `0` in one and `4` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (12 lines × 2) Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:376— Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:376-387 | Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:394-405 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) Core/Sources/UserDefaultsObserver/UserDefaultsObserver.swift:8— Core/Sources/UserDefaultsObserver/UserDefaultsObserver.swift:8-19 | Tool/Sources/UserDefaultsObserver/UserDefaultsObserver.swift:8-19 — before extracting anything, compare `Core/Sources/UserDefaultsObserver/UserDefaultsObserver.swift` and `Tool/Sources/UserDefaultsObserver/UserDefaultsObserver.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×3
Edited copy of a member (24 corresponding lines) Core/Sources/HostApp/ToolsSettings/BuiltInToolsListView.swift:178— Core/Sources/HostApp/ToolsSettings/BuiltInToolsListView.swift:178-201 | Core/Sources/HostApp/ToolsSettings/MCPServerToolsSection.swift:419-449 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:168— Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:168-191 | Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:193-216 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) Tool/Sources/XPCShared/XPCExtensionService.swift:376— Tool/Sources/XPCShared/XPCExtensionService.swift:376-399 | Tool/Sources/XPCShared/XPCExtensionService.swift:512-535 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×3
Edited copy of a member (14 corresponding lines) Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift:22— Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift:22-39 | Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift:41-54 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) Tool/Sources/XcodeInspector/SourceEditor.swift:47— Tool/Sources/XcodeInspector/SourceEditor.swift:47-60 | Tool/Sources/XcodeInspector/SourceEditor.swift:66-83 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) Core/Sources/SuggestionWidget/NES/NESMenu/NESMenuController.swift:137— Core/Sources/SuggestionWidget/NES/NESMenu/NESMenuController.swift:137-150 | Core/Sources/SuggestionWidget/NES/NESMenu/NESMenuController.swift:209-226 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×3
Edited copies of one member (3 members, 11+ corresponding lines) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift:114— Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift:114-124 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift:172-184 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift:220-232 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 11+ corresponding lines) Tool/Sources/ChatTab/ChatTab.swift:138— Tool/Sources/ChatTab/ChatTab.swift:138-148 | Tool/Sources/ChatTab/ChatTab.swift:152-162 | Tool/Sources/ChatTab/ChatTab.swift:187-197 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 11+ corresponding lines) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift:102— Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift:102-112 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift:158-170 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift:206-218 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×3
Edited copy of a member (10 corresponding lines) Tool/Sources/ConversationServiceProvider/ConversationServiceProvider.swift:283— Tool/Sources/ConversationServiceProvider/ConversationServiceProvider.swift:283-292 | Tool/Sources/TelemetryServiceProvider/TelemetryServiceProvider.swift:124-133 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) Tool/Sources/GitHubCopilotService/LanguageServer/CustomJSONRPCServerConnection.swift:194— Tool/Sources/GitHubCopilotService/LanguageServer/CustomJSONRPCServerConnection.swift:194-204 | Tool/Sources/GitHubCopilotService/LanguageServer/CustomJSONRPCServerConnection.swift:264-273 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) Core/Sources/HostApp/CopilotPolicyManager.swift:46— Core/Sources/HostApp/CopilotPolicyManager.swift:46-55 | Core/Sources/HostApp/FeatureFlagManager.swift:48-57 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×3
Edited copy of a member (5 corresponding lines) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ConversationAgentProgressView.swift:510— Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ConversationAgentProgressView.swift:510-514 | Core/Sources/ConversationTab/Views/FunctionMessage.swift:154-162 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) Core/Sources/ConversationTab/TerminalViews/RunInTerminalToolView.swift:313— Core/Sources/ConversationTab/TerminalViews/RunInTerminalToolView.swift:313-317 | Core/Sources/ConversationTab/TerminalViews/RunInTerminalToolView.swift:337-344 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ExpandableFileListView.swift:213— Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ExpandableFileListView.swift:213-218 | Tool/Sources/SharedUIComponents/OverlayScrollView.swift:40-44 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×3
Edited copy of a member (3 corresponding lines) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:765— Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:765-767 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCP.swift:133-135 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) Core/Sources/SuggestionWidget/ChatWindow/CopilotIntroView.swift:52— Core/Sources/SuggestionWidget/ChatWindow/CopilotIntroView.swift:52-58 | Tool/Sources/SharedUIComponents/CopilotIntroSheet.swift:13-15 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) Core/Sources/SuggestionWidget/ChatWindow/CopilotIntroView.swift:44— Core/Sources/SuggestionWidget/ChatWindow/CopilotIntroView.swift:44-50 | Tool/Sources/SharedUIComponents/CopilotIntroSheet.swift:9-11 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×3
Edited copy of a member (4 corresponding lines) Core/Sources/PersistMiddleware/Stores/ChatMessageStore.swift:12— Core/Sources/PersistMiddleware/Stores/ChatMessageStore.swift:12-15 | Core/Sources/PersistMiddleware/Stores/ChatTabInfoStore.swift:11-16 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) Tool/Sources/GitHubCopilotService/Services/GitHubCopilotConversationService.swift:96— Tool/Sources/GitHubCopilotService/Services/GitHubCopilotConversationService.swift:96-100 | Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift:72-75 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) Tool/Sources/DebounceFunction/DebounceFunction.swift:9— Tool/Sources/DebounceFunction/DebounceFunction.swift:9-12 | Tool/Sources/DebounceFunction/ThrottleFunction.swift:11-14 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (12–13 lines × 2) Core/Sources/ConversationTab/DiffViews/DiffWebView.swift:77— Core/Sources/ConversationTab/DiffViews/DiffWebView.swift:77-89 | Core/Sources/ConversationTab/DiffViews/DiffWebView.swift:147-158 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–13 lines × 2) Core/Sources/HostApp/BYOKSettings/ApiKeySheet.swift:23— Core/Sources/HostApp/BYOKSettings/ApiKeySheet.swift:23-34 | Core/Sources/HostApp/BYOKSettings/ModelSheet.swift:29-41 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/HostApp/BYOKSettings/ApiKeySheet.swift:23` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 2) Core/Sources/SuggestionWidget/WidgetView.swift:77— Core/Sources/SuggestionWidget/WidgetView.swift:77-89 | Core/Sources/SuggestionWidget/WidgetView.swift:94-105 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/SuggestionWidget/WidgetView.swift:77` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
No assertions: test_breakLines Tool/Tests/SuggestionBasicTests/BreakLinePerformanceTests.swift:6— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: test_source_editor_cache_get_content_comparison Tool/Tests/XcodeInspectorTests/SourceEditorCachePerformanceTests.swift:7— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D4 · Code Duplication· Edited copy of a member (42 corresponding lines) · ×2
Edited copy of a member (42 corresponding lines) Tool/Sources/SuggestionBasic/Modification.swift:10— Tool/Sources/SuggestionBasic/Modification.swift:10-51 | Tool/Sources/SuggestionBasic/Modification.swift:61-110 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (42 corresponding lines) Core/Sources/SuggestionWidget/ChatWindow/ChatNoAXPermissionView.swift:8— Core/Sources/SuggestionWidget/ChatWindow/ChatNoAXPermissionView.swift:8-49 | Core/Sources/SuggestionWidget/ChatWindow/ChatNoSubscriptionView.swift:10-63 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×2
Edited copy of a member (21 corresponding lines) Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift:295— Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift:295-315 | Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift:334-354 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) Core/Sources/SuggestionService/SuggestionService.swift:46— Core/Sources/SuggestionService/SuggestionService.swift:46-66 | Core/Sources/SuggestionService/SuggestionService.swift:68-88 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×2
Edited copy of a member (26 corresponding lines) Tool/Sources/XPCShared/XPCExtensionService.swift:423— Tool/Sources/XPCShared/XPCExtensionService.swift:423-448 | Tool/Sources/XPCShared/XPCExtensionService.swift:577-613 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) Core/Sources/HostApp/ToolsSettings/ToolRowView.swift:14— Core/Sources/HostApp/ToolsSettings/ToolRowView.swift:14-42 | Core/Sources/SuggestionWidget/AgentConfigurationWidgetView.swift:1004-1029 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×2
Edited copy of a member (20 corresponding lines) Core/Sources/Service/XPCService.swift:231— Core/Sources/Service/XPCService.swift:231-250 | Core/Sources/Service/XPCService.swift:252-273 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift:416— Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift:416-437 | Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift:449-468 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 24+ corresponding lines) · ×2
Edited copies of one member (5 members, 24+ corresponding lines) Tool/Sources/XPCShared/XPCExtensionService.swift:734— Tool/Sources/XPCShared/XPCExtensionService.swift:734-757 | Tool/Sources/XPCShared/XPCExtensionService.swift:759-782 | Tool/Sources/XPCShared/XPCExtensionService.swift:784-807 | Tool/Sources/XPCShared/XPCExtensionService.swift:809-832 | Tool/Sources/XPCShared/XPCExtensionService.swift:864-887 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
Edited copies of one member (5 members, 24+ corresponding lines) Tool/Sources/XPCShared/XPCExtensionService.swift:452— Tool/Sources/XPCShared/XPCExtensionService.swift:452-480 | Tool/Sources/XPCShared/XPCExtensionService.swift:482-510 | Tool/Sources/XPCShared/XPCExtensionService.swift:655-679 | Tool/Sources/XPCShared/XPCExtensionService.swift:708-731 | Tool/Sources/XPCShared/XPCExtensionService.swift:834-862 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) Core/Sources/KeyBindingManager/TabToAcceptSuggestion.swift:199— Core/Sources/KeyBindingManager/TabToAcceptSuggestion.swift:199-216 | Core/Sources/KeyBindingManager/TabToAcceptSuggestion.swift:218-235 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) Core/Sources/ConversationTab/DiffViews/DiffWebView.swift:74— Core/Sources/ConversationTab/DiffViews/DiffWebView.swift:74-91 | Core/Sources/ConversationTab/DiffViews/DiffWebView.swift:146-164 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×2
Edited copy of a member (15 corresponding lines) Tool/Sources/SharedUIComponents/DownvoteButton.swift:13— Tool/Sources/SharedUIComponents/DownvoteButton.swift:13-27 | Tool/Sources/SharedUIComponents/UpvoteButton.swift:13-27 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) Tool/Sources/SuggestionProvider/PostProcessingSuggestionServiceMiddleware.swift:7— Tool/Sources/SuggestionProvider/PostProcessingSuggestionServiceMiddleware.swift:7-21 | Tool/Sources/SuggestionProvider/PostProcessingSuggestionServiceMiddleware.swift:23-38 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×2
Edited copy of a member (7 corresponding lines) Tool/Sources/Persist/ConfigPathUtils.swift:12— Tool/Sources/Persist/ConfigPathUtils.swift:12-18 | Tool/Sources/Persist/ConfigPathUtils.swift:80-86 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) Core/Sources/ConversationTab/ModeAndModelPicker/ModePicker/AgentModeMenu.swift:157— Core/Sources/ConversationTab/ModeAndModelPicker/ModePicker/AgentModeMenu.swift:157-164 | Core/Sources/ConversationTab/ModeAndModelPicker/ModelPicker/ModelPickerMenu.swift:169-175 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (23 lines × 2) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:359— Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:359-381 | Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:454-476 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:359` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (23 lines × 2) Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:47— Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:47-69 | Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:93-115 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:47` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (19 lines × 2) Core/Sources/HostApp/AdvancedSettings/ChatSection.swift:430— Core/Sources/HostApp/AdvancedSettings/ChatSection.swift:430-448 | Core/Sources/HostApp/AdvancedSettings/ChatSection.swift:494-512 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/HostApp/AdvancedSettings/ChatSection.swift:430` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift:80— Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift:80-98 | Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift:103-121 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift:80` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) Core/Sources/HostApp/AdvancedSettings/ChatSection.swift:451— Core/Sources/HostApp/AdvancedSettings/ChatSection.swift:451-468 | Core/Sources/HostApp/AdvancedSettings/ChatSection.swift:515-532 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/HostApp/AdvancedSettings/ChatSection.swift:451` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:338— Core/Sources/SuggestionWidget/WidgetWindowsController.swift:338-355 | Core/Sources/SuggestionWidget/WidgetWindowsController.swift:362-379 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/SuggestionWidget/WidgetWindowsController.swift:338` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) Core/Sources/HostApp/ToolsSettings/AutoApprove/AutoApprovalDisableView.swift:9— Core/Sources/HostApp/ToolsSettings/AutoApprove/AutoApprovalDisableView.swift:9-24 | Core/Sources/HostApp/ToolsSettings/MCPIntroView.swift:17-32 — before extracting anything, compare `Core/Sources/HostApp/ToolsSettings/AutoApprove/AutoApprovalDisableView.swift` and `Core/Sources/HostApp/ToolsSettings/MCPIntroView.swift` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/HostApp/ToolsSettings/MCPIntroView.swift:17` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) Tool/Sources/SuggestionProvider/SuggestionServiceMiddleware.swift:42— Tool/Sources/SuggestionProvider/SuggestionServiceMiddleware.swift:42-57 | Tool/Sources/SuggestionProvider/SuggestionServiceMiddleware.swift:60-75 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/SuggestionProvider/SuggestionServiceMiddleware.swift:42` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) Core/Sources/ConversationTab/Chat.swift:840— Core/Sources/ConversationTab/Chat.swift:840-850 | Core/Sources/ConversationTab/Chat.swift:1345-1355 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/ConversationTab/Chat.swift:840` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) Core/Sources/ConversationTab/Views/ChatPanelInputArea/InputAreaTextEditor.swift:456— Core/Sources/ConversationTab/Views/ChatPanelInputArea/InputAreaTextEditor.swift:456-466 | Core/Sources/ConversationTab/VisionViews/VisionMenuView.swift:108-118 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/ConversationTab/Views/ChatPanelInputArea/InputAreaTextEditor.swift:456` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8–9 lines × 2) Core/Sources/SuggestionWidget/ChatWindow/ChatHistoryView.swift:259— Core/Sources/SuggestionWidget/ChatWindow/ChatHistoryView.swift:259-266 | Core/Sources/SuggestionWidget/ChatWindowView.swift:689-697 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/SuggestionWidget/ChatWindow/ChatHistoryView.swift:259` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Core/Sources/SuggestionWidget/ChatWindow/ChatHistoryView.swift:256` calls `EmptyChatTab` and `Core/Sources/SuggestionWidget/ChatWindowView.swift:686` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8–9 lines × 2) Tool/Sources/XPCShared/XPCExtensionService.swift:308— Tool/Sources/XPCShared/XPCExtensionService.swift:308-315 | Tool/Sources/XPCShared/XPCExtensionService.swift:335-343 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/XPCShared/XPCExtensionService.swift:308` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) Tool/Sources/ConversationServiceProvider/LSPTypes+AgentRound.swift:118— Tool/Sources/ConversationServiceProvider/LSPTypes+AgentRound.swift:118-124 | Tool/Sources/ConversationServiceProvider/LSPTypes+AgentRound.swift:168-174 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/ConversationServiceProvider/LSPTypes+AgentRound.swift:118` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) Core/Sources/ChatService/ToolCalls/AutoApproval/MCPApprovalStorage.swift:90— Core/Sources/ChatService/ToolCalls/AutoApproval/MCPApprovalStorage.swift:90-96 | Core/Sources/ChatService/ToolCalls/AutoApproval/SensitiveFileApprovalStorage.swift:85-91 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark Server/src/diffView/diffView.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Low contrast colour pair in CSS (3.8:1) Server/src/diffView/css/style.css:94— `.action-button.secondary` sets color: #DFDEDF on background-color: #6E6D70 — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Chat.body (cyclomatic 151) Core/Sources/ConversationTab/Chat.swift:689— Chat.body has cyclomatic complexity 151 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ChatPanelFeature.body (cyclomatic 72) Core/Sources/SuggestionWidget/FeatureReducers/ChatPanelFeature.swift:210— ChatPanelFeature.body has cyclomatic complexity 72 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WidgetFeature.body (cyclomatic 52) Core/Sources/SuggestionWidget/FeatureReducers/WidgetFeature.swift:145— WidgetFeature.body has cyclomatic complexity 52 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PanelFeature.body (cyclomatic 42) Core/Sources/SuggestionWidget/FeatureReducers/PanelFeature.swift:80— PanelFeature.body has cyclomatic complexity 42 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
GUI.body (cyclomatic 38) Core/Sources/Service/GUI/GraphicalUserInterfaceController.swift:65— GUI.body has cyclomatic complexity 38 (threshold 15). Of this number, 37 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ChatMessage.mergeEditAgentRounds (cyclomatic 38) Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:167— ChatMessage.mergeEditAgentRounds has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CodeReviewPanelFeature.body (cyclomatic 34) Core/Sources/SuggestionWidget/FeatureReducers/CodeReviewFeature.swift:107— CodeReviewPanelFeature.body has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
WidgetWindowsController.updateWindowOpacity (cyclomatic 33) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:453— WidgetWindowsController.updateWindowOpacity has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FixErrorPanelFeature.body (cyclomatic 31) Core/Sources/SuggestionWidget/FeatureReducers/FixErrorPanelFeature.swift:87— FixErrorPanelFeature.body has cyclomatic complexity 31 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
ChatService.handleProgressReport (cyclomatic 28) Core/Sources/ChatService/ChatService.swift:789— ChatService.handleProgressReport has cyclomatic complexity 28 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ChatMemory.appendMessage (cyclomatic 27) Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:12— ChatMemory.appendMessage has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HTMLToMarkdownConverter.convertSpecificElement (cyclomatic 27) Tool/Sources/WebContentExtractor/HTMLToMarkdownConverter.swift:103— HTMLToMarkdownConverter.convertSpecificElement has cyclomatic complexity 27 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ToolAutoApprovalManager.splitTerminalCommandLineIntoSubCommands (cyclomatic 26) Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalParsingHelpers.swift:115— ToolAutoApprovalManager.splitTerminalCommandLineIntoSubCommands has cyclomatic complexity 26 (threshold 15). Of this number, 25 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ServerNotificationHandlerImpl.handleNotification (cyclomatic 25) Tool/Sources/GitHubCopilotService/LanguageServer/ServerNotificationHandler.swift:25— ServerNotificationHandlerImpl.handleNotification has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ChatService.resetOngoingRequest (cyclomatic 24) Core/Sources/ChatService/ChatService.swift:1123— ChatService.resetOngoingRequest has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NSError.from (cyclomatic 24) Core/Sources/Service/Helpers.swift:6— NSError.from has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PromptToCode.body (cyclomatic 23) Core/Sources/SuggestionWidget/FeatureReducers/PromptToCode.swift:150— PromptToCode.body has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
XcodeInspector.restart (cyclomatic 23) Tool/Sources/XcodeInspector/XcodeInspector.swift:123— XcodeInspector.restart has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ToolStatusItemView.parsedFileListResult (cyclomatic 22) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:361— ToolStatusItemView.parsedFileListResult has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WidgetWindowsController.generateWidgetLocation (cyclomatic 22) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:310— WidgetWindowsController.generateWidgetLocation has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HighlightrThemeManager.theme (cyclomatic 21) Core/Sources/XcodeThemeController/HighlightrThemeManager.swift:15— HighlightrThemeManager.theme has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ChatService.handleProgressEnd (cyclomatic 20) Core/Sources/ChatService/ChatService.swift:1019— ChatService.handleProgressEnd has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
InputAreaTextEditor.body (cyclomatic 20) Core/Sources/ConversationTab/Views/ChatPanelInputArea/InputAreaTextEditor.swift:90— InputAreaTextEditor.body has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SuggestionInjector.acceptSuggestion (cyclomatic 20) Core/Sources/SuggestionInjector/SuggestionInjector.swift:18— SuggestionInjector.acceptSuggestion has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WidgetWindowsController.updateAttachedChatWindowLocation (cyclomatic 20) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:555— WidgetWindowsController.updateAttachedChatWindowLocation has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ToolAutoApprovalManager.extractTerminalCommandName (cyclomatic 19) Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalParsingHelpers.swift:239— ToolAutoApprovalManager.extractTerminalCommandName has cyclomatic complexity 19 (threshold 15). Of this number, 12 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
ModelPickerDetailPanel.show (cyclomatic 19) Core/Sources/ConversationTab/ModeAndModelPicker/ModelPicker/ModelPickerDetailPanel.swift:398— ModelPickerDetailPanel.show has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PseudoCommandHandler.acceptSuggestion (cyclomatic 19) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:401— PseudoCommandHandler.acceptSuggestion has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GitHubCopilotRequest.swift.editorConfiguration (cyclomatic 19) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:55— GitHubCopilotRequest.swift.editorConfiguration has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BatchingFileChangeWatcher.processEvent (cyclomatic 19) Tool/Sources/Workspace/FileChangeWatcher/BatchingFileChangeWatcher.swift:257— BatchingFileChangeWatcher.processEvent has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WorkspaceXcodeWindowInspector.deriveWorkspaceFromDocumentURL (cyclomatic 19) Tool/Sources/XcodeInspector/XcodeWindowInspector.swift:126— WorkspaceXcodeWindowInspector.deriveWorkspaceFromDocumentURL has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ChatService.send (cyclomatic 18) Core/Sources/ChatService/ChatService.swift:358— ChatService.send has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SuggestionInjector.recoverSuffixIfNeeded (cyclomatic 18) Core/Sources/SuggestionInjector/SuggestionInjector.swift:133— SuggestionInjector.recoverSuffixIfNeeded has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PromptToCodeGroup.body (cyclomatic 18) Core/Sources/SuggestionWidget/FeatureReducers/PromptToCodeGroup.swift:94— PromptToCodeGroup.body has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
XcodeThemeController.syncXcodeThemeIfNeeded (cyclomatic 18) Core/Sources/XcodeThemeController/XcodeThemeController.swift:91— XcodeThemeController.syncXcodeThemeIfNeeded has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AXNotificationStream.init (cyclomatic 18) Tool/Sources/AXNotificationStream/AXNotificationStream.swift:47— AXNotificationStream.init has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
AppDelegate.menuWillOpen (cyclomatic 18) ExtensionService/AppDelegate+Menu.swift:179— AppDelegate.menuWillOpen has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ToolAutoApprovalManager.approve (cyclomatic 17) Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalManager.swift:26— ToolAutoApprovalManager.approve has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
CopilotLocalProcessServer.handleNotification (cyclomatic 17) Tool/Sources/GitHubCopilotService/LanguageServer/CopilotLocalProcessServer.swift:181— CopilotLocalProcessServer.handleNotification has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
CodeHighlighting.convertToCodeLines (cyclomatic 17) Tool/Sources/SharedUIComponents/SyntaxHighlighting.swift:76— CodeHighlighting.convertToCodeLines has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ToolStatusItemView.body (cyclomatic 16) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:452— ToolStatusItemView.body has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
RealtimeSuggestionController.handleFocusElementChange (cyclomatic 16) Core/Sources/Service/RealtimeSuggestionController.swift:46— RealtimeSuggestionController.handleFocusElementChange has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AgentMCPServerSection.body (cyclomatic 16) Core/Sources/SuggestionWidget/AgentConfigurationWidgetView.swift:671— AgentMCPServerSection.body has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WidgetWindowsController._updateCodeReviewWindowLocation (cyclomatic 16) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:839— WidgetWindowsController._updateCodeReviewWindowLocation has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
QuotaView.createUpsellView (cyclomatic 16) Tool/Sources/StatusBarItemView/QuotaView.swift:406— QuotaView.createUpsellView has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
QuotaView.buildFooterConstraints (cyclomatic 16) Tool/Sources/StatusBarItemView/QuotaView.swift:580— QuotaView.buildFooterConstraints has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Chat.body (cognitive 186) Core/Sources/ConversationTab/Chat.swift:689— Chat.body has cognitive complexity 186 (threshold 15). Drivers by points: if/else 51 (110 pts), loops 14 (30 pts), boolean chains 15, match/switch 5 (15 pts), error handling 4 (14 pts), ternaries 1 (2 pts) (nesting depth added 96). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ChatMessage.mergeEditAgentRounds (cognitive 158) Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:167— ChatMessage.mergeEditAgentRounds has cognitive complexity 158 (threshold 15). Drivers by points: if/else 24 (129 pts), loops 4 (16 pts), boolean chains 13 (nesting depth added 117). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ChatMemory.appendMessage (cognitive 130) Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:12— ChatMemory.appendMessage has cognitive complexity 130 (threshold 15). Drivers by points: if/else 20 (112 pts), loops 2 (11 pts), boolean chains 7 (nesting depth added 101). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ChatPanelFeature.body (cognitive 77) Core/Sources/SuggestionWidget/FeatureReducers/ChatPanelFeature.swift:210— ChatPanelFeature.body has cognitive complexity 77 (threshold 15). Drivers by points: if/else 29 (62 pts), boolean chains 10, loops 1 (2 pts), ternaries 1 (2 pts), match/switch 1 (nesting depth added 35). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
WidgetFeature.body (cognitive 62) Core/Sources/SuggestionWidget/FeatureReducers/WidgetFeature.swift:145— WidgetFeature.body has cognitive complexity 62 (threshold 15). Drivers by points: if/else 23 (45 pts), match/switch 5 (7 pts), loops 3 (6 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 28). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
WidgetWindowsController.updateWindowOpacity (cognitive 57) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:453— WidgetWindowsController.updateWindowOpacity has cognitive complexity 57 (threshold 15). Drivers by points: ternaries 15 (30 pts), if/else 14 (20 pts), boolean chains 7 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToolAutoApprovalManager.splitTerminalCommandLineIntoSubCommands (cognitive 52) Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalParsingHelpers.swift:115— ToolAutoApprovalManager.splitTerminalCommandLineIntoSubCommands has cognitive complexity 52 (threshold 15). Drivers by points: if/else 16 (43 pts), boolean chains 8, loops 1 (nesting depth added 27). Of this number, 51 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GUI.body (cognitive 47) Core/Sources/Service/GUI/GraphicalUserInterfaceController.swift:65— GUI.body has cognitive complexity 47 (threshold 15). Drivers by points: if/else 21 (41 pts), boolean chains 4, match/switch 2 (nesting depth added 20). Of this number, 45 points are the body's own statements and 2 belong to one function item inside it that branches. The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
AppDelegate.menuWillOpen (cognitive 45) ExtensionService/AppDelegate+Menu.swift:179— AppDelegate.menuWillOpen has cognitive complexity 45 (threshold 15). Drivers by points: if/else 13 (22 pts), ternaries 4 (13 pts), loops 3 (9 pts), match/switch 1 (nesting depth added 24). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ChatService.resetOngoingRequest (cognitive 44) Core/Sources/ChatService/ChatService.swift:1123— ChatService.resetOngoingRequest has cognitive complexity 44 (threshold 15). Drivers by points: if/else 10 (24 pts), loops 7 (14 pts), boolean chains 6 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToolStatusItemView.parsedFileListResult (cognitive 43) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:361— ToolStatusItemView.parsedFileListResult has cognitive complexity 43 (threshold 15). Drivers by points: if/else 13 (27 pts), boolean chains 7, ternaries 1 (6 pts), loops 1 (3 pts) (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
XcodeInspector.restart (cognitive 42) Tool/Sources/XcodeInspector/XcodeInspector.swift:123— XcodeInspector.restart has cognitive complexity 42 (threshold 15). Drivers by points: if/else 18 (35 pts), loops 4 (5 pts), boolean chains 2 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PseudoCommandHandler.acceptSuggestion (cognitive 41) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:401— PseudoCommandHandler.acceptSuggestion has cognitive complexity 41 (threshold 15). Drivers by points: if/else 10 (29 pts), match/switch 2 (6 pts), error handling 3 (5 pts), boolean chains 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WidgetWindowsController.generateWidgetLocation (cognitive 39) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:310— WidgetWindowsController.generateWidgetLocation has cognitive complexity 39 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 11, match/switch 3 (11 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ServerNotificationHandlerImpl.handleNotification (cognitive 38) Tool/Sources/GitHubCopilotService/LanguageServer/ServerNotificationHandler.swift:25— ServerNotificationHandlerImpl.handleNotification has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (28 pts), boolean chains 6, match/switch 2 (4 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChatService.handleProgressEnd (cognitive 37) Core/Sources/ChatService/ChatService.swift:1019— ChatService.handleProgressEnd has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 9, error handling 1 (4 pts), ternaries 1 (4 pts) (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
CodeReviewPanelFeature.body (cognitive 36) Core/Sources/SuggestionWidget/FeatureReducers/CodeReviewFeature.swift:107— CodeReviewPanelFeature.body has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 10, loops 2 (4 pts), match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
BatchingFileChangeWatcher.processEvent (cognitive 36) Tool/Sources/Workspace/FileChangeWatcher/BatchingFileChangeWatcher.swift:257— BatchingFileChangeWatcher.processEvent has cognitive complexity 36 (threshold 15). Drivers by points: if/else 14 (30 pts), boolean chains 5, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NSMutableArray.apply (cognitive 34) Tool/Sources/SuggestionBasic/Modification.swift:61— NSMutableArray.apply has cognitive complexity 34 (threshold 15). Drivers by points: if/else 8 (26 pts), loops 2 (4 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CodeHighlighting.convertToCodeLines (cognitive 32) Tool/Sources/SharedUIComponents/SyntaxHighlighting.swift:76— CodeHighlighting.convertToCodeLines has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 4 (8 pts), error handling 1 (3 pts) (nesting depth added 16). Of this number, 29 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkspaceXcodeWindowInspector.deriveWorkspaceFromDocumentURL (cognitive 31) Tool/Sources/XcodeInspector/XcodeWindowInspector.swift:126— WorkspaceXcodeWindowInspector.deriveWorkspaceFromDocumentURL has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 6, loops 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
QuotaView.createUpsellView (cognitive 30) Tool/Sources/StatusBarItemView/QuotaView.swift:406— QuotaView.createUpsellView has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 4 (11 pts), boolean chains 4, match/switch 1 (2 pts) (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ChatService.handleProgressReport (cognitive 29) Core/Sources/ChatService/ChatService.swift:789— ChatService.handleProgressReport has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 16, if/else 12 (13 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
WidgetWindowsController.updateAttachedChatWindowLocation (cognitive 29) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:555— WidgetWindowsController.updateAttachedChatWindowLocation has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 8, ternaries 2 (8 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FixErrorPanelFeature.body (cognitive 29) Core/Sources/SuggestionWidget/FeatureReducers/FixErrorPanelFeature.swift:87— FixErrorPanelFeature.body has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 5, loops 2 (4 pts), match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
QuotaPopoverView.quotaContent (cognitive 29) Tool/Sources/SharedUIComponents/QuotaPopoverView.swift:55— QuotaPopoverView.quotaContent has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 6 (18 pts), if/else 5 (9 pts), boolean chains 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XcodeAppInstanceInspector.observeAXNotifications (cognitive 29) Tool/Sources/XcodeInspector/Apps/XcodeAppInstanceInspector.swift:200— XcodeAppInstanceInspector.observeAXNotifications has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (22 pts), boolean chains 3, match/switch 1 (3 pts), loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MCPAutoApproveView.body (cognitive 27) Core/Sources/HostApp/ToolsSettings/AutoApprove/MCPAutoApproveView.swift:15— MCPAutoApproveView.body has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (25 pts), boolean chains 1, ternaries 1 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PanelFeature.body (cognitive 27) Core/Sources/SuggestionWidget/FeatureReducers/PanelFeature.swift:80— PanelFeature.body has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (20 pts), match/switch 3 (5 pts), boolean chains 2 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
AppInstanceInspector.triggerMenuItem (cognitive 26) Tool/Sources/XcodeInspector/XcodeInspector+TriggerCommand.swift:57— AppInstanceInspector.triggerMenuItem has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (21 pts), error handling 1 (2 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ModelPickerDetailPanel.show (cognitive 25) Core/Sources/ConversationTab/ModeAndModelPicker/ModelPicker/ModelPickerDetailPanel.swift:398— ModelPickerDetailPanel.show has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 4, loops 1 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TabToAcceptSuggestion.handleEvent (cognitive 25) Core/Sources/KeyBindingManager/TabToAcceptSuggestion.swift:136— TabToAcceptSuggestion.handleEvent has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 2 (6 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RealtimeSuggestionController.handleFocusElementChange (cognitive 25) Core/Sources/Service/RealtimeSuggestionController.swift:46— RealtimeSuggestionController.handleFocusElementChange has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (21 pts), error handling 1 (2 pts), loops 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SuggestionInjector.acceptSuggestion (cognitive 25) Core/Sources/SuggestionInjector/SuggestionInjector.swift:18— SuggestionInjector.acceptSuggestion has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 10 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GitHubCopilotService.refreshClientTools (cognitive 25) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:1350— GitHubCopilotService.refreshClientTools has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (14 pts), error handling 2 (6 pts), boolean chains 5 (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ChatService.send (cognitive 24) Core/Sources/ChatService/ChatService.swift:358— ChatService.send has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 4, ternaries 2 (3 pts), error handling 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XPCService.updateToolsStatus (cognitive 24) Core/Sources/Service/XPCService.swift:480— XPCService.updateToolsStatus has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (17 pts), error handling 3 (4 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
QuotaPopoverView.buildQuotaItems (cognitive 24) Tool/Sources/SharedUIComponents/QuotaPopoverView.swift:227— QuotaPopoverView.buildQuotaItems has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 4 (8 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XPCService.updateMCPServerToolsStatus (cognitive 23) Core/Sources/Service/XPCService.swift:335— XPCService.updateMCPServerToolsStatus has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 3, error handling 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToolStatusItemView.fileOperationProgressView (cognitive 22) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:181— ToolStatusItemView.fileOperationProgressView has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentMCPServerSection.body (cognitive 22) Core/Sources/SuggestionWidget/AgentConfigurationWidgetView.swift:671— AgentMCPServerSection.body has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 6, match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GitHubCopilotService.updateServiceAuthStatus (cognitive 22) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:1075— GitHubCopilotService.updateServiceAuthStatus has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 4 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExtensionServiceLauncher.launch (cognitive 22) CommunicationBridge/ServiceDelegate.swift:134— ExtensionServiceLauncher.launch has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
String.apply (cognitive 21) Tool/Sources/SuggestionBasic/Modification.swift:10— String.apply has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (17 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XcodeThemeController.syncXcodeThemeIfNeeded (cognitive 21) Core/Sources/XcodeThemeController/XcodeThemeController.swift:91— XcodeThemeController.syncXcodeThemeIfNeeded has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 4, error handling 1 (2 pts), ternaries 1 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GitHunk.parseDiff (cognitive 21) Tool/Sources/GitHelper/GitHunk.swift:29— GitHunk.parseDiff has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (17 pts), ternaries 2, boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkspaceFile.processWorkspaceNodes (cognitive 21) Tool/Sources/Workspace/WorkspaceFile.swift:89— WorkspaceFile.processWorkspaceNodes has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InputAreaTextEditor.body (cognitive 20) Core/Sources/ConversationTab/Views/ChatPanelInputArea/InputAreaTextEditor.swift:90— InputAreaTextEditor.body has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10, ternaries 5 (6 pts), boolean chains 4 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PseudoCommandHandler.acceptPromptToCode (cognitive 20) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:339— PseudoCommandHandler.acceptPromptToCode has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (14 pts), error handling 3 (5 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HighlightrThemeManager.theme (cognitive 20) Core/Sources/XcodeThemeController/HighlightrThemeManager.swift:15— HighlightrThemeManager.theme has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 6, match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
GitDiff.parseDiff (cognitive 20) Tool/Sources/GitHelper/GitDiff.swift:43— GitDiff.parseDiff has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
QuotaView.buildFooterConstraints (cognitive 20) Tool/Sources/StatusBarItemView/QuotaView.swift:580— QuotaView.buildFooterConstraints has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 5 (9 pts), if/else 5 (6 pts), boolean chains 5 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkspaceFile.getFilesInActiveWorkspace (cognitive 20) Tool/Sources/Workspace/WorkspaceFile.swift:227— WorkspaceFile.getFilesInActiveWorkspace has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (5 pts), error handling 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToolAutoApprovalManager.extractTerminalCommandName (cognitive 19) Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalParsingHelpers.swift:239— ToolAutoApprovalManager.extractTerminalCommandName has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, if/else 8, loops 2 (3 pts) (nesting depth added 1). Of this number, 12 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConversationTab.handlePasteEvent (cognitive 19) Core/Sources/ConversationTab/ConversationTab.swift:248— ConversationTab.handlePasteEvent has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FunctionMessage.body (cognitive 19) Core/Sources/ConversationTab/Views/FunctionMessage.swift:107— FunctionMessage.body has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (19 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NSError.from (cognitive 19) Core/Sources/Service/Helpers.swift:6— NSError.from has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
HorizontalMovable.framesForWindows (cognitive 19) Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:197— HorizontalMovable.framesForWindows has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 2 (5 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GitHubCopilotRequest.swift.editorConfiguration (cognitive 19) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:55— GitHubCopilotRequest.swift.editorConfiguration has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 3, loops 3 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WorkspaceXcodeWindowInspector.extractProjectURL (cognitive 19) Tool/Sources/XcodeInspector/XcodeWindowInspector.swift:183— WorkspaceXcodeWindowInspector.extractProjectURL has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChatPanel.onFileDrop (cognitive 18) Core/Sources/ConversationTab/ChatPanel.swift:92— ChatPanel.onFileDrop has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ModelPickerMenu.rebuildMenuItems (cognitive 18) Core/Sources/ConversationTab/ModeAndModelPicker/ModelPicker/ModelPickerMenu.swift:224— ModelPickerMenu.rebuildMenuItems has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 7, loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
MCPConfigView.body (cognitive 18) Core/Sources/HostApp/ToolsConfigView.swift:33— MCPConfigView.body has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ModelRowView.body (cognitive 18) Core/Sources/HostApp/BYOKSettings/ModelRowView.swift:23— ModelRowView.body has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 4 (6 pts), boolean chains 3, error handling 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SuggestionInjector.recoverSuffixIfNeeded (cognitive 18) Core/Sources/SuggestionInjector/SuggestionInjector.swift:133— SuggestionInjector.recoverSuffixIfNeeded has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 8, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AgentConfigurationWidgetLocationStrategy.getAgentConfigurationWidgetLocation (cognitive 18) Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:558— AgentConfigurationWidgetLocationStrategy.getAgentConfigurationWidgetLocation has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 5 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
PromptToCode.body (cognitive 18) Core/Sources/SuggestionWidget/FeatureReducers/PromptToCode.swift:150— PromptToCode.body has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), error handling 2 (4 pts), loops 1 (3 pts), boolean chains 1, match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
AXNotificationStream.init (cognitive 18) Tool/Sources/AXNotificationStream/AXNotificationStream.swift:47— AXNotificationStream.init has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3 (4 pts), match/switch 1 (3 pts), boolean chains 1, ternaries 1 (nesting depth added 7). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GitHubCopilotService.init (cognitive 18) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:464— GitHubCopilotService.init has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 2 (4 pts), match/switch 1 (3 pts), boolean chains 2, error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppDelegate.updateStatusBarItem (cognitive 18) ExtensionService/AppDelegate.swift:415— AppDelegate.updateStatusBarItem has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 1 (4 pts), boolean chains 1, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TerminalAddon.handleSingleLine (cognitive 18) Server/src/terminal/terminalAddon.ts:125— TerminalAddon.handleSingleLine has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToolCallStatusUpdater.findAndUpdateToolCall (cognitive 17) Core/Sources/ChatService/ToolCalls/ToolCallStatusUpdater.swift:26— ToolCallStatusUpdater.findAndUpdateToolCall has cognitive complexity 17 (threshold 15). Drivers by points: loops 5 (10 pts), if/else 3 (7 pts) (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ToolAutoApprovalManager.approve (cognitive 17) Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalManager.swift:26— ToolAutoApprovalManager.approve has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 5 (9 pts), if/else 3 (7 pts), boolean chains 1 (nesting depth added 8). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ModelPickerDetailPanel.layoutAndShow (cognitive 17) Core/Sources/ConversationTab/ModeAndModelPicker/ModelPicker/ModelPickerDetailPanel.swift:567— ModelPickerDetailPanel.layoutAndShow has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
General.body (cognitive 17) Core/Sources/HostApp/General.swift:42— General.body has cognitive complexity 17 (threshold 15). Drivers by points: error handling 4 (8 pts), if/else 3 (6 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ScheduledCleaner.cleanUp (cognitive 17) Core/Sources/Service/ScheduledCleaner.swift:33— ScheduledCleaner.cleanUp has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WidgetWindowsController._updateCodeReviewWindowLocation (cognitive 17) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:839— WidgetWindowsController._updateCodeReviewWindowLocation has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (7 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CodeBlockSuggestionPanel.body (cognitive 17) Core/Sources/SuggestionWidget/SuggestionPanelContent/CodeBlockSuggestionPanel.swift:42— CodeBlockSuggestionPanel.body has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 3, ternaries 2 (3 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
DiffBuilder.diff (cognitive 17) Core/Sources/SuggestionWidget/NES/NESDiffView/NESDiffBuilder.swift:62— DiffBuilder.diff has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 5 (6 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CurrentChangeService.getPRChanges (cognitive 17) Tool/Sources/GitHelper/CurrentChange.swift:14— CurrentChangeService.getPRChanges has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (3 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConversationStorage.operate (cognitive 17) Tool/Sources/Persist/Storage/ConversationStorage/ConversationStorage.swift:78— ConversationStorage.operate has cognitive complexity 17 (threshold 15). Drivers by points: loops 4 (10 pts), match/switch 2 (6 pts), if/else 1 (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Terminal.streamCommand (cognitive 17) Tool/Sources/Terminal/Terminal.swift:44— Terminal.streamCommand has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 4, error handling 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SourceEditor.observeAXNotifications (cognitive 17) Tool/Sources/XcodeInspector/SourceEditor.swift:105— SourceEditor.observeAXNotifications has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 2 (3 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XcodeInspector.setActiveXcode (cognitive 17) Tool/Sources/XcodeInspector/XcodeInspector.swift:270— XcodeInspector.setActiveXcode has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 4 (5 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChatService.requestThinkingTitle (cognitive 16) Core/Sources/ChatService/ChatService.swift:920— ChatService.requestThinkingTitle has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 3 (4 pts), boolean chains 3, error handling 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InputAreaTextEditor.subscribeToActiveDocumentChangeEvent (cognitive 16) Core/Sources/ConversationTab/Views/ChatPanelInputArea/InputAreaTextEditor.swift:600— InputAreaTextEditor.subscribeToActiveDocumentChangeEvent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExpandableFileListView.fileRow (cognitive 16) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ExpandableFileListView.swift:118— ExpandableFileListView.fileRow has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), error handling 1 (3 pts), ternaries 3, boolean chains 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ToolStatusItemView.body (cognitive 16) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:452— ToolStatusItemView.body has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 8. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
GitHubCopilotViewModel.waitForSignIn (cognitive 16) Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift:148— GitHubCopilotViewModel.waitForSignIn has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), error handling 2, match/switch 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BuiltInToolsListView.reloadModesAndUpdateStates (cognitive 16) Core/Sources/HostApp/ToolsSettings/BuiltInToolsListView.swift:178— BuiltInToolsListView.reloadModesAndUpdateStates has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 1 (4 pts), error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MCPServerToolsSection.reloadModesAndUpdateStates (cognitive 16) Core/Sources/HostApp/ToolsSettings/MCPServerToolsSection.swift:419— MCPServerToolsSection.reloadModesAndUpdateStates has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 1 (4 pts), error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PseudoCommandHandler.generateRealtimeSuggestions (cognitive 16) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:54— PseudoCommandHandler.generateRealtimeSuggestions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 5, error handling 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
CopilotLanguageModelToolManager.updateToolsStatus (cognitive 16) Tool/Sources/GitHubCopilotService/LanguageServer/CopilotLanguageModelToolManager.swift:15— CopilotLanguageModelToolManager.updateToolsStatus has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 2, boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
QuotaView.addSubviewsToHierarchy (cognitive 16) Tool/Sources/StatusBarItemView/QuotaView.swift:73— QuotaView.addSubviewsToHierarchy has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Members sharing a duplicated core (22 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (22 members, 50+ identical tokens) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:367— Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:367-371 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:439-443 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:453-457 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:465-469 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:479-483 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:493-497 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:507-511 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:531-535 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:545-549 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:557-561 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:589-593 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:601-605 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:613-617 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:627-631 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:641-645 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:655-659 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:667-671 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:679-683 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:691-695 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:703-707 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:715-719 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:728-732 — These 22 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 22 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 22 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) Tool/Sources/HostAppActivator/HostAppActivator.swift:42— Tool/Sources/HostAppActivator/HostAppActivator.swift:42-60 | Tool/Sources/HostAppActivator/HostAppActivator.swift:62-89 | Tool/Sources/HostAppActivator/HostAppActivator.swift:91-110 | Tool/Sources/HostAppActivator/HostAppActivator.swift:112-130 | Tool/Sources/HostAppActivator/HostAppActivator.swift:132-150 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:269— Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:269-275 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:285-291 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:337-341 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:351-357 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (57 corresponding lines) · ×1
Edited copy of a member (57 corresponding lines) Core/Sources/Service/XPCService.swift:335— Core/Sources/Service/XPCService.swift:335-391 | Core/Sources/Service/XPCService.swift:480-551 — These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (45 corresponding lines) · ×1
Edited copy of a member (45 corresponding lines) Core/Sources/ConversationTab/Chat.swift:46— Core/Sources/ConversationTab/Chat.swift:46-90 | Tool/Sources/ChatAPIService/Models.swift:191-247 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:44— Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:44-88 | Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:90-130 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) Core/Sources/Service/SuggestionCommandHandler/WindowBaseCommandHandler.swift:176— Core/Sources/Service/SuggestionCommandHandler/WindowBaseCommandHandler.swift:176-211 | Core/Sources/Service/SuggestionCommandHandler/WindowBaseCommandHandler.swift:213-246 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) Tool/Sources/ConversationServiceProvider/ConversationServiceProvider.swift:356— Tool/Sources/ConversationServiceProvider/ConversationServiceProvider.swift:356-390 | Tool/Sources/ConversationServiceProvider/LSPTypes.swift:800-836 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:139— Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:139-187 | Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:189-228 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (39 corresponding lines) · ×1
Edited copy of a member (39 corresponding lines) Core/Sources/HostApp/AdvancedSettings/ChatSection.swift:430— Core/Sources/HostApp/AdvancedSettings/ChatSection.swift:430-468 | Core/Sources/HostApp/AdvancedSettings/ChatSection.swift:494-532 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) Core/Sources/HostApp/CopilotPolicyManager.swift:57— Core/Sources/HostApp/CopilotPolicyManager.swift:57-84 | Core/Sources/HostApp/FeatureFlagManager.swift:59-88 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:1290— Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:1290-1316 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:1318-1346 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) Core/Sources/SuggestionWidget/AgentConfigurationWidgetView.swift:360— Core/Sources/SuggestionWidget/AgentConfigurationWidgetView.swift:360-389 | Core/Sources/SuggestionWidget/AgentConfigurationWidgetView.swift:391-420 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 20+ corresponding lines) · ×1
Edited copies of one member (6 members, 20+ corresponding lines) Core/Sources/Service/XPCService.swift:395— Core/Sources/Service/XPCService.swift:395-416 | Core/Sources/Service/XPCService.swift:418-439 | Core/Sources/Service/XPCService.swift:626-645 | Core/Sources/Service/XPCService.swift:671-690 | Core/Sources/Service/XPCService.swift:692-711 | Core/Sources/Service/XPCService.swift:746-765 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 22+ corresponding lines) · ×1
Edited copies of one member (3 members, 22+ corresponding lines) EditorExtension/AcceptNESSuggestionCommand.swift:10— EditorExtension/AcceptNESSuggestionCommand.swift:10-31 | EditorExtension/AcceptPromptToCodeCommand.swift:9-30 | EditorExtension/AcceptSuggestionCommand.swift:10-31 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 19+ corresponding lines) · ×1
Edited copies of one member (3 members, 19+ corresponding lines) Tool/Sources/GitHubCopilotService/Conversation/ShowMessageRequestHandler.swift:44— Tool/Sources/GitHubCopilotService/Conversation/ShowMessageRequestHandler.swift:44-62 | Tool/Sources/GitHubCopilotService/Services/QuotaNotifier.swift:224-243 | Tool/Sources/GitHubCopilotService/Services/RateLimitNotifier.swift:80-99 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) Tool/Sources/SharedUIComponents/CustomTextEditor.swift:24— Tool/Sources/SharedUIComponents/CustomTextEditor.swift:24-42 | Tool/Sources/SharedUIComponents/CustomTextEditor.swift:75-93 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×1
Edited copies of one member (3 members, 7+ corresponding lines) Tool/Sources/Persist/AppState.swift:61— Tool/Sources/Persist/AppState.swift:61-67 | Tool/Sources/Persist/ConfigPathUtils.swift:12-18 | Tool/Sources/Persist/ConfigPathUtils.swift:80-86 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 19+ corresponding lines) · ×1
Edited copies of one member (6 members, 19+ corresponding lines) Tool/Sources/XPCShared/XPCExtensionService.swift:403— Tool/Sources/XPCShared/XPCExtensionService.swift:403-421 | Tool/Sources/XPCShared/XPCExtensionService.swift:537-555 | Tool/Sources/XPCShared/XPCExtensionService.swift:557-575 | Tool/Sources/XPCShared/XPCExtensionService.swift:615-633 | Tool/Sources/XPCShared/XPCExtensionService.swift:635-653 | Tool/Sources/XPCShared/XPCExtensionService.swift:688-706 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift:239— Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift:239-248 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift:356-367 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift:389-404 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 14+ corresponding lines) · ×1
Edited copies of one member (4 members, 14+ corresponding lines) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:24— Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:24-37 | Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:39-52 | Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:266-279 | Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:281-294 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 11+ corresponding lines) · ×1
Edited copies of one member (5 members, 11+ corresponding lines) Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift:11— Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift:11-23 | Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift:94-105 | Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift:107-118 | Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift:120-130 | Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift:132-142 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 9+ corresponding lines) · ×1
Edited copies of one member (4 members, 9+ corresponding lines) Core/Sources/ConversationTab/ChatPanel.swift:740— Core/Sources/ConversationTab/ChatPanel.swift:740-748 | Core/Sources/ConversationTab/ChatPanel.swift:752-760 | Core/Sources/ConversationTab/ChatPanel.swift:764-779 | Core/Sources/ConversationTab/ChatPanel.swift:783-791 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 10+ corresponding lines) · ×1
Edited copies of one member (4 members, 10+ corresponding lines) Core/Sources/Service/SuggestionCommandHandler/WindowBaseCommandHandler.swift:89— Core/Sources/Service/SuggestionCommandHandler/WindowBaseCommandHandler.swift:89-103 | Core/Sources/Service/SuggestionCommandHandler/WindowBaseCommandHandler.swift:116-130 | Core/Sources/Service/SuggestionCommandHandler/WindowBaseCommandHandler.swift:143-152 | Core/Sources/Service/SuggestionCommandHandler/WindowBaseCommandHandler.swift:165-174 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (8 members, 11+ corresponding lines) · ×1
Edited copies of one member (8 members, 11+ corresponding lines) Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift:59— Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift:59-72 | Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift:74-92 | Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift:144-155 | Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift:157-168 | Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift:170-181 | Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift:192-203 | Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift:205-216 | Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift:218-228 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) Tool/Sources/Preferences/UserDefaults.swift:161— Tool/Sources/Preferences/UserDefaults.swift:161-168 | Tool/Sources/Preferences/UserDefaults.swift:170-178 | Tool/Sources/Preferences/UserDefaults.swift:236-244 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (36 lines × 2) Core/Sources/HostApp/ToolsSettings/AutoApprove/EditsAutoApproveView.swift:97— Core/Sources/HostApp/ToolsSettings/AutoApprove/EditsAutoApproveView.swift:97-132 | Core/Sources/HostApp/ToolsSettings/AutoApprove/TerminalAutoApproveView.swift:77-112 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (28–32 lines × 2) Core/Sources/HostApp/ToolsSettings/AutoApprove/EditsAutoApproveView.swift:25— Core/Sources/HostApp/ToolsSettings/AutoApprove/EditsAutoApproveView.swift:25-52 | Core/Sources/HostApp/ToolsSettings/AutoApprove/TerminalAutoApproveView.swift:22-53 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (30 lines × 2) Tool/Sources/AppActivator/AppActivator.swift:77— Tool/Sources/AppActivator/AppActivator.swift:77-106 | Tool/Sources/XcodeInspector/XcodeInspector+TriggerCommand.swift:177-206 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (27 lines × 2) Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift:366— Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift:366-392 | Core/Sources/HostApp/ToolsSettings/MCPRegistry/ServerInstallationOptionView.swift:136-162 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (20–22 lines × 3) Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanel.swift:485— Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanel.swift:485-504 | Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanel.swift:514-535 | Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanel.swift:545-564 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanel.swift:485` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20–21 lines × 2) Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:248— Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:248-268 | Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:300-319 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:248` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (21 lines × 2) Tool/Sources/SuggestionProvider/SuggestionServiceMiddleware.swift:82— Tool/Sources/SuggestionProvider/SuggestionServiceMiddleware.swift:82-102 | Tool/Sources/SuggestionProvider/SuggestionServiceMiddleware.swift:105-125 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/SuggestionProvider/SuggestionServiceMiddleware.swift:82` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (20 lines × 2) Core/Sources/HostApp/AdvancedSettings/DisabledLanguageList.swift:29— Core/Sources/HostApp/AdvancedSettings/DisabledLanguageList.swift:29-48 | Core/Sources/HostApp/AdvancedSettings/GlobalInstructionsView.swift:16-35 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/HostApp/AdvancedSettings/DisabledLanguageList.swift:29` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17–18 lines × 2) Core/Sources/HostApp/AdvancedSettings/GlobalInstructionsView.swift:65— Core/Sources/HostApp/AdvancedSettings/GlobalInstructionsView.swift:65-82 | Core/Sources/HostApp/AdvancedSettings/ProxySection.swift:42-58 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13–14 lines × 2) Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:44— Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:44-57 | Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:187-199 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14 lines × 2) Tool/Sources/Terminal/Terminal.swift:54— Tool/Sources/Terminal/Terminal.swift:54-67 | Tool/Sources/Terminal/Terminal.swift:135-148 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11–12 lines × 2) Core/Sources/ChatService/ChatService.swift:335— Core/Sources/ChatService/ChatService.swift:335-345 | Core/Sources/ChatService/ChatService.swift:1140-1151 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/ChatService/ChatService.swift:335` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–11 lines × 2) Core/Sources/KeyBindingManager/KeyBindingManager.swift:6— Core/Sources/KeyBindingManager/KeyBindingManager.swift:6-15 | Core/Sources/KeyBindingManager/TabToAcceptSuggestion.swift:52-62 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/KeyBindingManager/KeyBindingManager.swift:6` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–11 lines × 2) Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift:61— Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift:61-69 | Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift:76-86 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift:61` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7–8 lines × 3) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift:116— Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift:116-123 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift:174-180 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift:223-229 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 5) Tool/Sources/HostAppActivator/HostAppActivator.swift:44— Tool/Sources/HostAppActivator/HostAppActivator.swift:44-50 | Tool/Sources/HostAppActivator/HostAppActivator.swift:64-70 | Tool/Sources/HostAppActivator/HostAppActivator.swift:93-99 | Tool/Sources/HostAppActivator/HostAppActivator.swift:114-120 | Tool/Sources/HostAppActivator/HostAppActivator.swift:134-140 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/HostAppActivator/HostAppActivator.swift:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6–7 lines × 2) Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:36— Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:36-42 | Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:179-184 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:36` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (3–5 lines × 4) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:271— Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:271-275 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:287-291 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:337-339 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:353-357 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:271` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:339` calls `JSONDecoder`, `decode`, `hash` and `Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:275` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 3) Tool/Sources/Persist/AppState.swift:63— Tool/Sources/Persist/AppState.swift:63-67 | Tool/Sources/Persist/ConfigPathUtils.swift:14-18 | Tool/Sources/Persist/ConfigPathUtils.swift:82-86 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/Persist/AppState.swift:63` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (10 lines × 7) EditorExtension/GetSuggestionsCommand.swift:9— EditorExtension/GetSuggestionsCommand.swift:9-18 | EditorExtension/NextSuggestionCommand.swift:9-18 | EditorExtension/PreviousSuggestionCommand.swift:9-18 | EditorExtension/PromptToCodeCommand.swift:9-18 | EditorExtension/RejectNESSuggestionCommand.swift:9-18 | EditorExtension/RejectSuggestionCommand.swift:9-18 | EditorExtension/SyncTextSettingsCommand.swift:9-18 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 7 call sites, so a change lands once.
Duplicated block (7 lines × 3) ExtensionService/AppDelegate+Menu.swift:365— ExtensionService/AppDelegate+Menu.swift:365-371 | ExtensionService/AppDelegate+Menu.swift:386-392 | ExtensionService/AppDelegate.swift:491-497 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (5 lines × 22) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:367— Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:367-371 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:439-443 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:453-457 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:465-469 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:479-483 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:493-497 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:507-511 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:531-535 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:545-549 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:557-561 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:589-593 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:601-605 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:613-617 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:627-631 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:641-645 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:655-659 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:667-671 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:679-683 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:691-695 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:703-707 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:715-719 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:728-732 — all 22 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
No structured logging — No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
Duplicated block (20 lines × 2 locations) Server/src/diffView/js/ui-controller.ts:84— Server/src/diffView/js/ui-controller.ts:84 · Server/src/diffView/js/ui-controller.ts:108 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication· Duplicated block with local edits (17 matched lines × 2 locations) · ×1
Duplicated block with local edits (17 matched lines × 2 locations) Server/src/diffView/js/api.ts:82— Server/src/diffView/js/api.ts:82 · Server/src/diffView/js/monaco-diff-editor.ts:243 — the two spans are one implementation copied and then locally edited — 106 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (9 lines × 2 locations) Server/src/terminal/terminalAddon.ts:93— Server/src/terminal/terminalAddon.ts:93 · Server/src/terminal/terminalAddon.ts:132 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (8 matched lines × 2 locations) · ×1
Duplicated block with local edits (8 matched lines × 2 locations) Server/src/diffView/js/monaco-diff-editor.ts:61— Server/src/diffView/js/monaco-diff-editor.ts:61 · Server/src/diffView/js/monaco-diff-editor.ts:243 — the two spans are one implementation copied and then locally edited — 56 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (7 lines × 2 locations) Server/src/terminal/terminalAddon.ts:132— Server/src/terminal/terminalAddon.ts:132 · Server/src/terminal/terminalAddon.ts:142 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Complex function handleSingleLine (cyclomatic 12, cognitive 18) Server/src/terminal/terminalAddon.ts:125— handleSingleLine has cyclomatic complexity 12 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
No test or lint script — test ✗ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
Unused dependency '@github/copilot-language-server' — Declared in Server/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@github/copilot-language-server-darwin-arm64' — Declared in Server/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@github/copilot-language-server-darwin-x64' — Declared in Server/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Silent fallback default in catch Core/Sources/ChatService/ChatService.swift:1359— `copilotModels` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift:399— `formatConfigAsJSON` turns every thrown error into `"{}"` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Core/Sources/HostApp/ToolsSettings/MCPRegistry/ServerInstallationOptionView.swift:168— `formatConfigAsJSON` turns every thrown error into `"{}"` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:18— `identifier` turns every thrown error into `""` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:22— `value` turns every thrown error into `""` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:30— `title` turns every thrown error into `""` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:34— `role` turns every thrown error into `""` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:38— `doubleValue` turns every thrown error into `0.0` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:47— `description` turns every thrown error into `""` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:52— `roleDescription` turns every thrown error into `""` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:56— `label` turns every thrown error into `""` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:119— `sharedFocusElements` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:127— `windows` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:143— `rows` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:151— `children` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:159— `visibleChildren` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
No direct assertions: test_should_accept Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:10— No conventional assertion call was detected, and 10 of 10 tests in `KeyBindingManagerTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_should_not_accept_without_suggestion Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:29— No conventional assertion call was detected, and 10 of 10 tests in `KeyBindingManagerTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_should_not_accept_without_filespace Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:48— No conventional assertion call was detected, and 10 of 10 tests in `KeyBindingManagerTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_should_not_accept_without_editor_focused Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:66— No conventional assertion call was detected, and 10 of 10 tests in `KeyBindingManagerTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_should_not_accept_without_active_xcode Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:85— No conventional assertion call was detected, and 10 of 10 tests in `KeyBindingManagerTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_should_not_accept_without_active_document Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:104— No conventional assertion call was detected, and 10 of 10 tests in `KeyBindingManagerTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_should_not_accept_with_shift Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:123— No conventional assertion call was detected, and 10 of 10 tests in `KeyBindingManagerTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_should_not_accept_with_command Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:142— No conventional assertion call was detected, and 10 of 10 tests in `KeyBindingManagerTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_should_not_accept_with_control Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:161— No conventional assertion call was detected, and 10 of 10 tests in `KeyBindingManagerTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_should_not_accept_with_help Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:180— No conventional assertion call was detected, and 10 of 10 tests in `KeyBindingManagerTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
Duplicated predicate Server/src/diffView/js/api.ts:109— `window.matchMedia && window.matchMedia('(prefers-color-scheme: dark)').matches` appears character-identically in 2 files — Server/src/diffView/js/api.ts, Server/src/diffView/js/monaco-diff-editor.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Core/Sources/ConversationTab/TerminalViews/RunInTerminalToolView.swift:164— `FeatureFlagNotifierImpl.shared.featureFlags.agentModeAutoApproval && CopilotPolicyNotifierImpl.shared.copilotPolicy.agentModeAutoApprovalEna…` appears character-identically in 2 files — Core/Sources/ConversationTab/TerminalViews/RunInTerminalToolView.swift, Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ConversationAgentProgressView.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift:381— `accountStatus == .ok || accountStatus == .maybeOk` appears character-identically in 2 files — Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift, ExtensionService/AppDelegate.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Core/Sources/HostApp/GeneralSettings/CopilotConnectionView.swift:41— `viewModel.isRunningAction || viewModel.waitingForSignIn` appears character-identically in 3 files — Core/Sources/HostApp/GeneralSettings/CopilotConnectionView.swift, Core/Sources/SuggestionWidget/ChatWindow/ChatLoginView.swift, Core/Sources/SuggestionWidget/ChatWindow/ChatNoSubscriptionView.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
redundant comment Server/src/diffView/js/api.ts:73— "Update diff stats" repeats the code it sits on: 3 of its 3 words (update, diff, stats) are already in `updateDiffStats();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment Server/src/terminal/terminalAddon.ts:212— "Write prompt and input" repeats the code it sits on: 3 of its 3 words (write, prompt, input) are already in `this.term.write(this.promptInLastLine + this.inputBuffer);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D10 · Test Quality· Test project verifies nothing · ×1
Test project verifies nothing: KeyBindingManagerTests Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:10— No conventional assertion call was detected in 10 of 10 tests in `KeyBindingManagerTests` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
No ADRs found Copilot for Xcode.xcodeproj/project.pbxproj:1— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `Copilot for Xcode.xcodeproj/project.pbxproj` makes this repository a deployable product (line 1).
D21 · Naming Consistency· `originalMcpRegistryBaseURL` spells `Mcp` where 34 names in the project spell it `MCP` · ×1
`originalMcpRegistryBaseURL` spells `Mcp` where 34 names in the project spell it `MCP` Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPRegistryURLSheet.swift:9— 34 of 35 names in project Core~ChatService spell the token `MCP` (34 of 35; unit: names in project Core~ChatService containing `MCP`). Peers: ToolAutoApprovalManager.allowMCPTool (Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalManager.swift:86); ToolAutoApprovalManager.allowMCPServer (Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalManager.swift:90); ToolAutoApprovalManager.isMCPAllowed (Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalManager.swift:94); ToolAutoApprovalManager.allowMCPToolGlobally (Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalManager.swift:104); ToolAutoApprovalManager.allowMCPServerGlobally (Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalManager.swift:108). Rename to `originalMCPRegistryBaseURL`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 4 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `Core` (39665 LoC, 556 module-visible types across 52 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P10 · Library API & versioning· Implementation type on the public API · ×1
Implementation type on the public API Tool/Sources/GitHubCopilotService/Conversation/ClientToolHandler.swift:13— 11 public types in `Tool~GitHubCopilotService` are marked as implementation by their own namespace, folder or name: `ClientToolHandlerImpl` (Tool/Sources/GitHubCopilotService/Conversation/ClientToolHandler.swift:13, name ends in `Impl`), `CompressionHandlerImpl` (Tool/Sources/GitHubCopilotService/Conversation/CompressionHandler.swift:9, name ends in `Impl`), `ConversationContextHandlerImpl` (Tool/Sources/GitHubCopilotService/Conversation/ConversationContextHandler.swift:9, name ends in `Impl`), `ConversationProgressHandlerImpl` (Tool/Sources/GitHubCopilotService/Conversation/ConversationProgressHandler.swift:18, name ends in `Impl`), `DynamicOAuthRequestHandlerImpl` (Tool/Sources/GitHubCopilotService/Conversation/DynamicOAuthRequestHandler.swift:15, name ends in `Impl`), `ShowMessageRequestHandlerImpl` (Tool/Sources/GitHubCopilotService/Conversation/ShowMessageRequestHandler.swift:17, name ends in `Impl`), `WatchedFilesHandlerImpl` (Tool/Sources/GitHubCopilotService/Conversation/WatchedFilesHandler.swift:13, name ends in `Impl`), `CopilotPolicyNotifierImpl` (Tool/Sources/GitHubCopilotService/Services/CopilotPolicyNotifier.swift:32, name ends in `Impl`), and 3 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
P3 · Security & performance tooling· Dependabot does not watch npm · ×1
Dependabot does not watch npm .github/dependabot.yml:2— `.github/dependabot.yml` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
Outdated: combine-schedulers — `combine-schedulers` is resolved at 1.0.0, but 1.2.2 is the newest release tagged on https://github.com/pointfreeco/combine-schedulers within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update combine-schedulers` reaches this one with no change to Package.swift.
Outdated: jsonrpc — `jsonrpc` is resolved at 0.9.0, but 0.9.2 is the newest release tagged on https://github.com/ChimeHQ/JSONRPC within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update jsonrpc` reaches this one with no change to Package.swift.
Outdated: languageserverprotocol — `languageserverprotocol` is resolved at 0.13.3, but 0.14.2 is the newest release tagged on https://github.com/ChimeHQ/LanguageServerProtocol within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update languageserverprotocol` reaches this one with no change to Package.swift.
Outdated: networkimage — `networkimage` is resolved at 6.0.0, but 6.0.1 is the newest release tagged on https://github.com/gonzalezreal/NetworkImage within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update networkimage` reaches this one with no change to Package.swift.
Outdated: queue — `queue` is resolved at 0.2.1, but 0.2.2 is the newest release tagged on https://github.com/mattmassicotte/Queue within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update queue` reaches this one with no change to Package.swift.
Outdated: sparkle — `sparkle` is resolved at 2.6.4, but 2.10.1 is the newest release tagged on https://github.com/sparkle-project/Sparkle within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update sparkle` reaches this one with no change to Package.swift.
Outdated: sqlite.swift — `sqlite.swift` is resolved at 0.15.3, but 0.17.0 is the newest release tagged on https://github.com/stephencelis/SQLite.swift.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update sqlite.swift` reaches this one with no change to Package.swift.
Outdated: swift-argument-parser — `swift-argument-parser` is resolved at 1.2.2, but 1.8.2 is the newest release tagged on https://github.com/apple/swift-argument-parser.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-argument-parser` reaches this one with no change to Package.swift.
Outdated: swift-async-algorithms — `swift-async-algorithms` is resolved at 1.0.0, but 1.1.7 is the newest release tagged on https://github.com/apple/swift-async-algorithms within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-async-algorithms` reaches this one with no change to Package.swift.
Outdated: swift-case-paths — `swift-case-paths` is resolved at 1.3.3, but 1.10.0 is the newest release tagged on https://github.com/pointfreeco/swift-case-paths within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-case-paths` reaches this one with no change to Package.swift.
Outdated: swift-clocks — `swift-clocks` is resolved at 1.0.2, but 1.1.1 is the newest release tagged on https://github.com/pointfreeco/swift-clocks within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-clocks` reaches this one with no change to Package.swift.
Outdated: swift-collections — `swift-collections` is resolved at 1.1.0, but 1.7.6 is the newest release tagged on https://github.com/apple/swift-collections within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-collections` reaches this one with no change to Package.swift.
Outdated: swift-composable-architecture — `swift-composable-architecture` is resolved at 1.10.4, but 1.26.2 is the newest release tagged on https://github.com/pointfreeco/swift-composable-architecture within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-composable-architecture` reaches this one with no change to Package.swift.
Outdated: swift-concurrency-extras — `swift-concurrency-extras` is resolved at 1.1.0, but 1.4.3 is the newest release tagged on https://github.com/pointfreeco/swift-concurrency-extras within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-concurrency-extras` reaches this one with no change to Package.swift.
Outdated: swift-custom-dump — `swift-custom-dump` is resolved at 1.3.0, but 1.7.3 is the newest release tagged on https://github.com/pointfreeco/swift-custom-dump within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-custom-dump` reaches this one with no change to Package.swift.
Outdated: swift-dependencies — `swift-dependencies` is resolved at 1.3.0, but 1.17.2 is the newest release tagged on https://github.com/pointfreeco/swift-dependencies within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-dependencies` reaches this one with no change to Package.swift.
Outdated: swift-identified-collections — `swift-identified-collections` is resolved at 1.0.2, but 1.1.1 is the newest release tagged on https://github.com/pointfreeco/swift-identified-collections within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-identified-collections` reaches this one with no change to Package.swift.
Outdated: swift-markdown-ui — `swift-markdown-ui` is resolved at 2.4.0, but 2.4.1 is the newest release tagged on https://github.com/gonzalezreal/swift-markdown-ui within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-markdown-ui` reaches this one with no change to Package.swift.
Outdated: swift-parsing — `swift-parsing` is resolved at 0.13.0, but 0.15.2 is the newest release tagged on https://github.com/pointfreeco/swift-parsing within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-parsing` reaches this one with no change to Package.swift.
Outdated: swift-perception — `swift-perception` is resolved at 1.2.2, but 1.6.0 is the newest release tagged on https://github.com/pointfreeco/swift-perception within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-perception` reaches this one with no change to Package.swift.
Outdated: swiftsoup — `swiftsoup` is resolved at 2.9.6, but 2.14.4 is the newest release tagged on https://github.com/scinfu/SwiftSoup.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swiftsoup` reaches this one with no change to Package.swift.
Outdated: swiftui-navigation — `swiftui-navigation` is resolved at 1.4.0, but 1.5.5 is the newest release tagged on https://github.com/pointfreeco/swiftui-navigation within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swiftui-navigation` reaches this one with no change to Package.swift.
Outdated: tree-sitter — `tree-sitter` is resolved at 0.25.10, but 0.27.2 is the newest release tagged on https://github.com/tree-sitter/tree-sitter within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update tree-sitter` reaches this one with no change to Package.swift.
Outdated: xctest-dynamic-overlay — `xctest-dynamic-overlay` is resolved at 1.1.2, but 1.13.1 is the newest release tagged on https://github.com/pointfreeco/xctest-dynamic-overlay within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update xctest-dynamic-overlay` reaches this one with no change to Package.swift.
doc comments repeat the names Server/src/diffView/js/api.ts:105— 0 of 24 documented parameters and 9 of 39 summaries in `@github/copilot-xcode` only repeat the member or parameter name (e.g. "Follow the system theme" for `followSystemTheme`). Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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 61 file(s) — `CommunicationBridge/ServiceDelegate.swift`, `Core/Sources/ChatService/ChatService.swift`, `Core/Sources/ChatService/CodeReview/CodeReviewProvider.swift`, `Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalParsingHelpers.swift`, `Core/Sources/ChatService/ToolCalls/InsertEditIntoFileTool.swift`, … (+56 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
provenance: not applicable — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files).
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1dc00-71c3-7154-b520-5a19ca6e792d · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 9 · Warnings: 487 · Recommendations: 42 · Info: 25 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 21:39 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.