Public report of intitni/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, 08:45 UTC · Survey ID cd_3bc5caec6f7144c29bbc497a3c7adb8e
intitni/CopilotForXcode
Measured 14 November 2026, 08:44 UTC, at code version b59c57a
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Down 12 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: 56,856 lines of product code in 75 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Event Sourcing, 10
Findings by how serious they are
9 critical438 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, 08:44 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 ▸
39of 39 dimensions measured by tools.
423of 514 findings point to an exact file and line, so you can open each one in the code. The other 91 concern the repository as a whole, such as missing documentation.
39dimensions across 7 lenses, read from 56,856 lines of product code in 75 projects.
intitni/CopilotForXcode falls short of our standard for a preview release, held back most by its Event Sourcing lens, the way the code stores and replays its history of events. It scores 33 out of 100 and is rated Weak, and two of its nine critical findings are security problems.
Event Sourcing, at 10, is the weakest lens and counts most in the score. The best first step is making the events unchangeable, worth about 20 points. Making the tests check their results comes next, worth about 5 points. Raising Event Sourcing to 65 would lift the score to about 50.
One password or key is open to anyone who can read the repository. One pipeline tool is referenced by a changeable name, so the build pipeline can be tampered with. Replacing the exposed password or key and pinning the tool to an exact version would close both risks. The five tests that check nothing need to check the result they produce.
The product code is 56,856 lines, about €57,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 Event Sourcing rose from 10 to 65, the lowest score rated Strong, the score would rise from 33 to about 50.
Code composition: what the lines of code are
Product code 85%Tests 15%
New since the last survey: 97 findings
These 97 critical or serious findings weren't in the previous survey, on 26 October 2026.
Code Duplication · Near-duplicate member pair (32 shared lines) Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift
Code Duplication · Edited copy of a member (77 corresponding lines) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift
Code Duplication · Edited copy of a member (78 corresponding lines) Core/Sources/HostApp/AccountSettings/APIKeyManagement/APIKeyManagementView.swift
Code Duplication · Edited copy of a member (40 corresponding lines) Tool/Sources/OpenAIService/APIs/OpenAIEmbeddingService.swift
Code Duplication · Edited copy of a member (61 corresponding lines) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift
Code Duplication · Edited copy of a member (46 corresponding lines) Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift
Code Duplication · Edited copy of a member (36 corresponding lines) Tool/Sources/CodeiumService/Services/CodeiumService.swift
Code Duplication · Edited copy of a member (35 corresponding lines) Core/Sources/SuggestionWidget/ChatWindowView.swift
Code Duplication · Edited copy of a member (31 corresponding lines) Tool/Sources/WebSearchService/SearchServices/HeadlessBrowserSearchService.swift
Code Duplication · Edited copy of a member (40 corresponding lines) Tool/Sources/SharedUIComponents/SyntaxHighlighting.swift
Code Duplication · Edited copies of one member (3 members, 39+ corresponding lines) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift
Code Duplication · Edited copy of a member (25 corresponding lines) Tool/Sources/WebSearchService/SearchServices/AppleDocumentationSearchService.swift
Code Duplication · Edited copy of a member (37 corresponding lines) Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift
Code Duplication · Edited copy of a member (29 corresponding lines) Tool/Sources/SharedUIComponents/AsyncDiffCodeBlock.swift
Code Duplication · Edited copy of a member (49 corresponding lines) Tool/Sources/OpenAIService/APIs/ChatCompletionsAPIBuilder.swift
Code Duplication · Edited copy of a member (35 corresponding lines) Core/Sources/PromptToCodeService/OpenAIPromptToCodeService.swift
Code Duplication · Edited copy of a member (38 corresponding lines) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift
Code Duplication · Edited copy of a member (37 corresponding lines) Core/Sources/HostApp/CustomCommandSettings/CustomCommandView.swift
Code Duplication · Edited copy of a member (35 corresponding lines) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift
Code Duplication · Edited copy of a member (29 corresponding lines) Tool/Sources/CodeiumService/CodeiumExtension.swift
Code Duplication · Edited copy of a member (23 corresponding lines) Tool/Sources/FocusedCodeFinder/ObjectiveC/ObjectiveCCodeFinder.swift
Code Duplication · Edited copy of a member (28 corresponding lines) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift
Code Duplication · Edited copy of a member (17 corresponding lines) Tool/Sources/LangChain/VectorStore/TemporaryUSearch.swift
Code Duplication · Edited copy of a member (17 corresponding lines) Tool/Sources/CodeiumService/Services/CodeiumSuggestionService.swift
Code Duplication · Edited copy of a member (13 corresponding lines) Core/Sources/SuggestionWidget/ChatWindowView.swift
Code Duplication · Edited copy of a member (13 corresponding lines) Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift
Code Duplication · Edited copy of a member (21 corresponding lines) Tool/Sources/OpenAIService/APIs/ChatCompletionsAPIDefinition.swift
Code Duplication · Edited copy of a member (22 corresponding lines) Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift
Code Duplication · Edited copy of a member (15 corresponding lines) Tool/Sources/XcodeInspector/SourceEditor.swift
Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) EditorExtension/AcceptPromptToCodeCommand.swift
Code Duplication · Edited copy of a member (14 corresponding lines) Tool/Sources/SharedUIComponents/CustomTextEditor.swift
Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) Tool/Sources/OpenAIService/APIs/ChatCompletionsAPIDefinition.swift
Code Duplication · Edited copy of a member (21 corresponding lines) ChatPlugins/Sources/ShortcutChatPlugin/ShortcutChatPlugin.swift
Code Duplication · Edited copy of a member (20 corresponding lines) Tool/Sources/FocusedCodeFinder/ObjectiveC/ObjectiveCCodeFinder.swift
Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) Core/Sources/HostApp/CustomCommandSettings/EditCustomCommandView.swift
Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) Tool/Sources/SharedUIComponents/SyntaxHighlighting.swift
Code Duplication · Edited copy of a member (9 corresponding lines) Tool/Sources/Workspace/OpenedFileRocoverableStorage.swift
Code Duplication · Edited copy of a member (14 corresponding lines) Tool/Sources/ChatContextCollectors/ActiveDocumentChatContextCollector/ActiveDocumentChatContextCollector.swift
Code Duplication · Edited copy of a member (8 corresponding lines) Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift
Code Duplication · Edited copy of a member (14 corresponding lines) Tool/Sources/USearchIndex/UsearchIndex.swift
Code Duplication · Edited copy of a member (18 corresponding lines) Core/Sources/HostApp/AccountSettings/WebSearchView.swift
Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift
Code Duplication · Edited copy of a member (14 corresponding lines) Tool/Sources/CodeiumService/CodeiumWorkspacePlugin.swift
Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift
Code Duplication · Edited copy of a member (12 corresponding lines) Core/Sources/ChatGPTChatTab/Chat.swift
Code Duplication · Edited copy of a member (14 corresponding lines) Core/Sources/ChatService/ChatService.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 (15 corresponding lines) Tool/Sources/SharedUIComponents/TabContainer.swift
Code Duplication · Edited copy of a member (14 corresponding lines) Tool/Sources/DebounceFunction/ThrottleFunction.swift
Code Duplication · Edited copy of a member (10 corresponding lines) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift
Code Duplication · Edited copy of a member (13 corresponding lines) Tool/Sources/LangChain/Chains/QAInformationRetrievalChain.swift
Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) Core/Sources/Service/SuggestionCommandHandler/WindowBaseCommandHandler.swift
Code Duplication · Edited copy of a member (17 corresponding lines) Tool/Sources/FocusedCodeFinder/ActiveDocumentContext.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/ChatGPTChatTab/ChatContextMenu.swift
Code Duplication · Edited copy of a member (8 corresponding lines) Tool/Sources/AXExtension/AXUIElement.swift
Code Duplication · Edited copy of a member (15 corresponding lines) Core/Sources/HostApp/FeatureSettings/Chat/ChatSettingsGeneralSectionView.swift
Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) Tool/Sources/BuiltinExtension/BuiltinExtensionWorkspacePlugin.swift
Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) Core/Sources/ChatGPTChatTab/ChatPanel.swift
Code Duplication · Edited copy of a member (12 corresponding lines) Tool/Sources/LangChain/DocumentTransformer/RecursiveCharacterTextSplitter.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 (10 corresponding lines) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift
Code Duplication · Edited copy of a member (13 corresponding lines) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift
Code Duplication · Edited copy of a member (8 corresponding lines) Tool/Sources/LangChain/Chain.swift
Code Duplication · Edited copy of a member (12 corresponding lines) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagementView.swift
Code Duplication · Edited copies of one member (5 members, 11+ corresponding lines) Tool/Sources/CodeiumService/CodeiumExtension.swift
Code Duplication · Edited copy of a member (14 corresponding lines) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift
Code Duplication · Edited copy of a member (13 corresponding lines) Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift
Code Duplication · Edited copy of a member (6 corresponding lines) Tool/Sources/Preferences/UserDefaults.swift
Code Duplication · Edited copy of a member (13 corresponding lines) Core/Sources/PromptToCodeService/PromptToCodeServiceType.swift
Code Duplication · Edited copy of a member (9 corresponding lines) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift
Code Duplication · Edited copy of a member (13 corresponding lines) CommunicationBridge/ServiceDelegate.swift
Code Duplication · Edited copy of a member (7 corresponding lines) Tool/Sources/LangChain/Chains/CombineAnswersChain.swift
Code Duplication · Edited copy of a member (11 corresponding lines) Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift
Code Duplication · Edited copy of a member (4 corresponding lines) Tool/Sources/OpenAIService/Configuration/EmbeddingConfiguration.swift
Code Duplication · Edited copy of a member (10 corresponding lines) Tool/Sources/LangChain/DocumentLoader/WebLoader.swift
Code Duplication · Edited copy of a member (4 corresponding lines) Tool/Sources/CodeiumService/Services/CodeiumSuggestionService.swift
Code Duplication · Edited copy of a member (4 corresponding lines) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.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: 27 findings
These 27 critical or serious findings were in the previous survey, on 26 October 2026, and are gone from this one.
Code Duplication · Near-duplicate member pair (32 shared lines) Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift
€19,000 to €95,000, for 316 to 1,004 hours of work, about 0.4 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 33. 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: 56,856 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 finding(s) in Immutable events.
Raises the score by about 20 points · Medium effort · Immutable events
2
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
3
Resolve the 2 Assertions commented out finding(s) in Test Quality — start with ChatPluginsTests.swift, WindowTests.swift.
Raises the score by about 5 points · Low effort · Test 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 €57,000 to build again, about 0.4 person-years of work. Its weakest lens is Event Sourcing, at 10 (Critical). Event Sourcing is about whether the stored history the system is built on can be trusted. Because the weakest lens counts most in the score, work on Event Sourcing also moves the score most.
Based on: the rebuild estimate · the Event Sourcing grade · how much each lens counts
What to do: Start with the Event Sourcing actions in Top priorities.
If you do one thing first · First action
Resolve the 1 finding(s) in Immutable events. Of all the actions in this report, it raises the score most for the work it takes: about 20 points for medium effort, because it clears the 1 Immutable events 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.7 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 3% to 7% on every change.
How this is estimated: It rests on an assumption 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. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4)
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.
69 modules, with 319 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; 29 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.
Tool~Preferences uses Tool~LangChain, so a change to Tool~LangChain can break Tool~Preferences, while a change to Tool~Preferences can't break Tool~LangChain.
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→21 Tool~Preferences uses Tool~FileSystempart of a loop✕
Connections
1 pair of types, where a type in Tool~Preferences uses a type in Tool~FileSystem.
The types involved
Tool~Preferences.Digest → Tool~FileSystem.UInt8
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→23 Tool~Preferences uses Tool~ChatBasicpart of a loop✕
Connections
18 pairs of types, where a type in Tool~Preferences uses a type in Tool~ChatBasic.
Tool~Preferences uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~Preferences, while a change to Tool~Preferences can't break Tool~ChatBasic.
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→37 Tool~Preferences uses Core~ChatGPTChatTabpart of a loop✕
Connections
1 pair of types, where a type in Tool~Preferences uses a type in Core~ChatGPTChatTab.
Tool~Preferences uses Core~ChatGPTChatTab, so a change to Core~ChatGPTChatTab can break Tool~Preferences, while a change to Tool~Preferences can't break Core~ChatGPTChatTab.
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~AIModel uses Tool~Preferences, so a change to Tool~Preferences can break Tool~AIModel, while a change to Tool~AIModel can't break Tool~Preferences.
Position
Below the diagonal: Tool~AIModel uses a module listed above it, which is the healthy direction.
2→20 Tool~AIModel uses Tool~LangChainpart of a loop✕
Connections
1 pair of types, where a type in Tool~AIModel uses a type in Tool~LangChain.
The types involved
Tool~AIModel.Info → Tool~LangChain.Int
Direction
Tool~AIModel uses Tool~LangChain, so a change to Tool~LangChain can break Tool~AIModel, while a change to Tool~AIModel can't break Tool~LangChain.
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→23 Tool~AIModel uses Tool~ChatBasicpart of a loop✕
Connections
9 pairs of types, where a type in Tool~AIModel uses a type in Tool~ChatBasic.
Tool~AIModel uses Core~ChatGPTChatTab, so a change to Core~ChatGPTChatTab can break Tool~AIModel, while a change to Tool~AIModel can't break Core~ChatGPTChatTab.
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.
3→15 Tool~AXExtension uses Core~SuggestionWidgetpart of a loop✕
Connections
1 pair of types, where a type in Tool~AXExtension uses a type in Core~SuggestionWidget.
Tool~AXExtension uses Core~SuggestionWidget, so a change to Core~SuggestionWidget can break Tool~AXExtension, while a change to Tool~AXExtension 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.
3→20 Tool~AXExtension uses Tool~LangChainpart of a loop✕
Connections
2 pairs of types, where a type in Tool~AXExtension uses a type in Tool~LangChain.
Tool~AXExtension uses Tool~LangChain, so a change to Tool~LangChain can break Tool~AXExtension, while a change to Tool~AXExtension can't break Tool~LangChain.
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→21 Tool~AXExtension uses Tool~FileSystempart of a loop✕
Connections
1 pair of types, where a type in Tool~AXExtension uses a type in Tool~FileSystem.
Tool~AXExtension uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~AXExtension, while a change to Tool~AXExtension 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→23 Tool~AXExtension uses Tool~ChatBasicpart of a loop✕
Connections
1 pair of types, where a type in Tool~AXExtension uses a type in Tool~ChatBasic.
Tool~AXExtension uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~AXExtension, while a change to Tool~AXExtension can't break Tool~ChatBasic.
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.
4→10 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.
4→20 Tool~ActiveApplicationMonitor uses Tool~LangChainpart of a loop✕
Connections
1 pair of types, where a type in Tool~ActiveApplicationMonitor uses a type in Tool~LangChain.
Tool~ActiveApplicationMonitor uses Tool~LangChain, so a change to Tool~LangChain can break Tool~ActiveApplicationMonitor, while a change to Tool~ActiveApplicationMonitor can't break Tool~LangChain.
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.
4→21 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.
4→23 Tool~ActiveApplicationMonitor uses Tool~ChatBasicpart of a loop✕
Connections
1 pair of types, where a type in Tool~ActiveApplicationMonitor uses a type in Tool~ChatBasic.
Tool~ActiveApplicationMonitor uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~ActiveApplicationMonitor, while a change to Tool~ActiveApplicationMonitor can't break Tool~ChatBasic.
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.
5→20 Tool~SuggestionBasic uses Tool~LangChainpart of a loop✕
Connections
4 pairs of types, where a type in Tool~SuggestionBasic uses a type in Tool~LangChain.
Tool~SuggestionBasic uses Tool~LangChain, so a change to Tool~LangChain can break Tool~SuggestionBasic, while a change to Tool~SuggestionBasic can't break Tool~LangChain.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→23 Tool~SuggestionBasic uses Tool~ChatBasicpart of a loop✕
Connections
9 pairs of types, where a type in Tool~SuggestionBasic uses a type in Tool~ChatBasic.
Tool~SuggestionBasic uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~SuggestionBasic, while a change to Tool~SuggestionBasic can't break Tool~ChatBasic.
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~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.
7→20 Tool~SuggestionProvider uses Tool~LangChainpart of a loop✕
Connections
2 pairs of types, where a type in Tool~SuggestionProvider uses a type in Tool~LangChain.
Tool~SuggestionProvider uses Tool~LangChain, so a change to Tool~LangChain can break Tool~SuggestionProvider, while a change to Tool~SuggestionProvider can't break Tool~LangChain.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→21 Tool~SuggestionProvider uses Tool~FileSystempart of a loop✕
Connections
1 pair of types, where a type in Tool~SuggestionProvider uses a type in Tool~FileSystem.
Tool~SuggestionProvider uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~SuggestionProvider, while a change to Tool~SuggestionProvider 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.
7→23 Tool~SuggestionProvider uses Tool~ChatBasicpart of a loop✕
Connections
4 pairs of types, where a type in Tool~SuggestionProvider uses a type in Tool~ChatBasic.
Tool~SuggestionProvider uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~SuggestionProvider, while a change to Tool~SuggestionProvider can't break Tool~ChatBasic.
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
Below the diagonal: Tool~XPCShared uses a module listed above it, which is the healthy direction.
8→10 Tool~XPCShared uses repositorypart of a loop✕
Connections
1 pair of types, where a type in Tool~XPCShared uses a type in repository.
Tool~XPCShared uses repository, so a change to repository can break Tool~XPCShared, while a change to Tool~XPCShared 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.
8→20 Tool~XPCShared uses Tool~LangChainpart of a loop✕
Connections
1 pair of types, where a type in Tool~XPCShared uses a type in Tool~LangChain.
The types involved
Tool~XPCShared.EditorContent → Tool~LangChain.Int
Direction
Tool~XPCShared uses Tool~LangChain, so a change to Tool~LangChain can break Tool~XPCShared, while a change to Tool~XPCShared can't break Tool~LangChain.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→23 Tool~XPCShared uses Tool~ChatBasicpart of a loop✕
Connections
17 pairs of types, where a type in Tool~XPCShared uses a type in Tool~ChatBasic.
Tool~XPCShared uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~XPCShared, while a change to Tool~XPCShared can't break Tool~ChatBasic.
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~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~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.
9→12 Tool~WorkspaceSuggestionService uses Tool~Workspacepart of a loop✕
Connections
3 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.
9→23 Tool~WorkspaceSuggestionService uses Tool~ChatBasicpart of a loop✕
Connections
1 pair of types, where a type in Tool~WorkspaceSuggestionService uses a type in Tool~ChatBasic.
Tool~WorkspaceSuggestionService uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~WorkspaceSuggestionService, while a change to Tool~WorkspaceSuggestionService can't break Tool~ChatBasic.
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.
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
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
repository uses Tool~ChatBasic, so a change to Tool~ChatBasic can break repository, while a change to repository can't break Tool~ChatBasic.
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→37 repository uses Core~ChatGPTChatTabpart of a loop✕
Connections
1 pair of types, where a type in repository uses a type in Core~ChatGPTChatTab.
The types involved
repository.ContentView → Core~ChatGPTChatTab.View
Direction
repository uses Core~ChatGPTChatTab, so a change to Core~ChatGPTChatTab can break repository, while a change to repository can't break Core~ChatGPTChatTab.
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~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.
Core~SuggestionService uses repository, so a change to repository can break Core~SuggestionService, while a change to Core~SuggestionService can't break repository.
Position
Below the diagonal: Core~SuggestionService uses a module listed above it, which is the healthy direction.
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~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~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.
12→20 Tool~Workspace uses Tool~LangChainpart of a loop✕
Connections
2 pairs of types, where a type in Tool~Workspace uses a type in Tool~LangChain.
Tool~Workspace uses Tool~LangChain, so a change to Tool~LangChain can break Tool~Workspace, while a change to Tool~Workspace can't break Tool~LangChain.
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→21 Tool~Workspace uses Tool~FileSystempart of a loop✕
Connections
2 pairs of types, where a type in Tool~Workspace uses a type in Tool~FileSystem.
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.
12→23 Tool~Workspace uses Tool~ChatBasicpart of a loop✕
Connections
9 pairs of types, where a type in Tool~Workspace uses a type in Tool~ChatBasic.
Tool~Workspace uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~Workspace, while a change to Tool~Workspace can't break Tool~ChatBasic.
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~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~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.
13→21 Tool~XcodeInspector uses Tool~FileSystempart of a loop✕
Connections
1 pair of types, where a type in Tool~XcodeInspector uses a type in Tool~FileSystem.
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
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→23 Tool~XcodeInspector uses Tool~ChatBasicpart of a loop✕
Connections
6 pairs of types, where a type in Tool~XcodeInspector uses a type in Tool~ChatBasic.
Tool~XcodeInspector uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~XcodeInspector, while a change to Tool~XcodeInspector can't break Tool~ChatBasic.
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.
OverlayWindow~OverlayWindow uses Tool~Preferences, so a change to Tool~Preferences can break OverlayWindow~OverlayWindow, while a change to OverlayWindow~OverlayWindow can't break Tool~Preferences.
Position
Below the diagonal: OverlayWindow~OverlayWindow uses a module listed above it, which is the healthy direction.
OverlayWindow~OverlayWindow uses Tool~AXExtension, so a change to Tool~AXExtension can break OverlayWindow~OverlayWindow, while a change to OverlayWindow~OverlayWindow can't break Tool~AXExtension.
Position
Below the diagonal: OverlayWindow~OverlayWindow uses a module listed above it, which is the healthy direction.
OverlayWindow~OverlayWindow uses repository, so a change to repository can break OverlayWindow~OverlayWindow, while a change to OverlayWindow~OverlayWindow can't break repository.
Position
Below the diagonal: OverlayWindow~OverlayWindow uses a module listed above it, which is the healthy direction.
OverlayWindow~OverlayWindow uses Tool~XcodeInspector, so a change to Tool~XcodeInspector can break OverlayWindow~OverlayWindow, while a change to OverlayWindow~OverlayWindow can't break Tool~XcodeInspector.
Position
Below the diagonal: OverlayWindow~OverlayWindow uses a module listed above it, which is the healthy direction.
14→15 OverlayWindow~OverlayWindow uses Core~SuggestionWidgetpart of a loop✕
Connections
3 pairs of types, where a type in OverlayWindow~OverlayWindow uses a type in Core~SuggestionWidget.
OverlayWindow~OverlayWindow uses Core~SuggestionWidget, so a change to Core~SuggestionWidget can break OverlayWindow~OverlayWindow, while a change to OverlayWindow~OverlayWindow 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.
14→20 OverlayWindow~OverlayWindow uses Tool~LangChainpart of a loop✕
Connections
1 pair of types, where a type in OverlayWindow~OverlayWindow uses a type in Tool~LangChain.
OverlayWindow~OverlayWindow uses Tool~LangChain, so a change to Tool~LangChain can break OverlayWindow~OverlayWindow, while a change to OverlayWindow~OverlayWindow can't break Tool~LangChain.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→21 OverlayWindow~OverlayWindow uses Tool~FileSystempart of a loop✕
Connections
1 pair of types, where a type in OverlayWindow~OverlayWindow uses a type in Tool~FileSystem.
OverlayWindow~OverlayWindow uses Tool~FileSystem, so a change to Tool~FileSystem can break OverlayWindow~OverlayWindow, while a change to OverlayWindow~OverlayWindow 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.
14→37 OverlayWindow~OverlayWindow uses Core~ChatGPTChatTabpart of a loop✕
Connections
1 pair of types, where a type in OverlayWindow~OverlayWindow uses a type in Core~ChatGPTChatTab.
OverlayWindow~OverlayWindow uses Core~ChatGPTChatTab, so a change to Core~ChatGPTChatTab can break OverlayWindow~OverlayWindow, while a change to OverlayWindow~OverlayWindow can't break Core~ChatGPTChatTab.
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.
26 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~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 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~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.
Core~SuggestionWidget uses OverlayWindow~OverlayWindow, so a change to OverlayWindow~OverlayWindow can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break OverlayWindow~OverlayWindow.
Position
Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
15→16 Core~SuggestionWidget uses Tool~ChatTabpart of a loop✕
Connections
8 pairs of types, where a type in Core~SuggestionWidget uses a type in Tool~ChatTab.
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
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→20 Core~SuggestionWidget uses Tool~LangChainpart of a loop✕
Connections
10 pairs of types, where a type in Core~SuggestionWidget uses a type in Tool~LangChain.
Core~SuggestionWidget uses Tool~LangChain, so a change to Tool~LangChain can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~LangChain.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→21 Core~SuggestionWidget uses Tool~FileSystempart of a loop✕
Connections
2 pairs of types, where a type in Core~SuggestionWidget uses a type in Tool~FileSystem.
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
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→23 Core~SuggestionWidget uses Tool~ChatBasicpart of a loop✕
Connections
11 pairs of types, where a type in Core~SuggestionWidget uses a type in Tool~ChatBasic.
Core~SuggestionWidget uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~ChatBasic.
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→37 Core~SuggestionWidget uses Core~ChatGPTChatTabpart of a loop✕
Connections
34 pairs of types, where a type in Core~SuggestionWidget uses a type in Core~ChatGPTChatTab. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Core~SuggestionWidget uses Core~ChatGPTChatTab, so a change to Core~ChatGPTChatTab can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Core~ChatGPTChatTab.
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
Below the diagonal: Tool~ChatTab uses a module listed above it, which is the healthy direction.
16→20 Tool~ChatTab uses Tool~LangChainpart of a loop✕
Connections
1 pair of types, where a type in Tool~ChatTab uses a type in Tool~LangChain.
The types involved
Tool~ChatTab.ChatTabInfo → Tool~LangChain.Int
Direction
Tool~ChatTab uses Tool~LangChain, so a change to Tool~LangChain can break Tool~ChatTab, while a change to Tool~ChatTab can't break Tool~LangChain.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→23 Tool~ChatTab uses Tool~ChatBasicpart of a loop✕
Connections
8 pairs of types, where a type in Tool~ChatTab uses a type in Tool~ChatBasic.
Tool~ChatTab uses Core~ChatGPTChatTab, so a change to Core~ChatGPTChatTab can break Tool~ChatTab, while a change to Tool~ChatTab can't break Core~ChatGPTChatTab.
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~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 Core~SuggestionService, so a change to Core~SuggestionService can break Tool~BuiltinExtension, while a change to Tool~BuiltinExtension can't break Core~SuggestionService.
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.
Tool~BuiltinExtension uses Tool~ChatTab, so a change to Tool~ChatTab can break Tool~BuiltinExtension, while a change to Tool~BuiltinExtension can't break Tool~ChatTab.
Position
Below the diagonal: Tool~BuiltinExtension uses a module listed above it, which is the healthy direction.
17→20 Tool~BuiltinExtension uses Tool~LangChainpart of a loop✕
Connections
1 pair of types, where a type in Tool~BuiltinExtension uses a type in Tool~LangChain.
Tool~BuiltinExtension uses Tool~LangChain, so a change to Tool~LangChain can break Tool~BuiltinExtension, while a change to Tool~BuiltinExtension can't break Tool~LangChain.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→23 Tool~BuiltinExtension uses Tool~ChatBasicpart of a loop✕
Connections
7 pairs of types, where a type in Tool~BuiltinExtension uses a type in Tool~ChatBasic.
Tool~BuiltinExtension uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~BuiltinExtension, while a change to Tool~BuiltinExtension can't break Tool~ChatBasic.
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~OpenAIService uses Tool~Preferences, so a change to Tool~Preferences can break Tool~OpenAIService, while a change to Tool~OpenAIService can't break Tool~Preferences.
Position
Below the diagonal: Tool~OpenAIService uses a module listed above it, which is the healthy direction.
Tool~OpenAIService uses Tool~AIModel, so a change to Tool~AIModel can break Tool~OpenAIService, while a change to Tool~OpenAIService can't break Tool~AIModel.
Position
Below the diagonal: Tool~OpenAIService uses a module listed above it, which is the healthy direction.
Tool~OpenAIService uses repository, so a change to repository can break Tool~OpenAIService, while a change to Tool~OpenAIService can't break repository.
Position
Below the diagonal: Tool~OpenAIService uses a module listed above it, which is the healthy direction.
Tool~OpenAIService uses Tool~BuiltinExtension, so a change to Tool~BuiltinExtension can break Tool~OpenAIService, while a change to Tool~OpenAIService can't break Tool~BuiltinExtension.
Position
Below the diagonal: Tool~OpenAIService uses a module listed above it, which is the healthy direction.
18→20 Tool~OpenAIService uses Tool~LangChainpart of a loop✕
Connections
35 pairs of types, where a type in Tool~OpenAIService uses a type in Tool~LangChain. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Tool~OpenAIService uses Tool~LangChain, so a change to Tool~LangChain can break Tool~OpenAIService, while a change to Tool~OpenAIService can't break Tool~LangChain.
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→23 Tool~OpenAIService uses Tool~ChatBasicpart of a loop✕
Connections
103 pairs of types, where a type in Tool~OpenAIService uses a type in Tool~ChatBasic. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Tool~OpenAIService uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~OpenAIService, while a change to Tool~OpenAIService can't break Tool~ChatBasic.
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 Tool~CodeiumService uses a type in Tool~Preferences. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Tool~CodeiumService uses Tool~Preferences, so a change to Tool~Preferences can break Tool~CodeiumService, while a change to Tool~CodeiumService can't break Tool~Preferences.
Position
Below the diagonal: Tool~CodeiumService uses a module listed above it, which is the healthy direction.
Tool~CodeiumService uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Tool~CodeiumService, while a change to Tool~CodeiumService can't break Tool~SuggestionBasic.
Position
Below the diagonal: Tool~CodeiumService uses a module listed above it, which is the healthy direction.
Tool~CodeiumService uses Tool~SuggestionProvider, so a change to Tool~SuggestionProvider can break Tool~CodeiumService, while a change to Tool~CodeiumService can't break Tool~SuggestionProvider.
Position
Below the diagonal: Tool~CodeiumService uses a module listed above it, which is the healthy direction.
Tool~CodeiumService uses repository, so a change to repository can break Tool~CodeiumService, while a change to Tool~CodeiumService can't break repository.
Position
Below the diagonal: Tool~CodeiumService uses a module listed above it, which is the healthy direction.
Tool~CodeiumService uses Core~SuggestionService, so a change to Core~SuggestionService can break Tool~CodeiumService, while a change to Tool~CodeiumService can't break Core~SuggestionService.
Position
Below the diagonal: Tool~CodeiumService uses a module listed above it, which is the healthy direction.
Tool~CodeiumService uses Tool~Workspace, so a change to Tool~Workspace can break Tool~CodeiumService, while a change to Tool~CodeiumService can't break Tool~Workspace.
Position
Below the diagonal: Tool~CodeiumService uses a module listed above it, which is the healthy direction.
Tool~CodeiumService uses Tool~ChatTab, so a change to Tool~ChatTab can break Tool~CodeiumService, while a change to Tool~CodeiumService can't break Tool~ChatTab.
Position
Below the diagonal: Tool~CodeiumService uses a module listed above it, which is the healthy direction.
Tool~CodeiumService uses Tool~BuiltinExtension, so a change to Tool~BuiltinExtension can break Tool~CodeiumService, while a change to Tool~CodeiumService can't break Tool~BuiltinExtension.
Position
Below the diagonal: Tool~CodeiumService uses a module listed above it, which is the healthy direction.
Tool~CodeiumService uses Tool~OpenAIService, so a change to Tool~OpenAIService can break Tool~CodeiumService, while a change to Tool~CodeiumService can't break Tool~OpenAIService.
Position
Below the diagonal: Tool~CodeiumService uses a module listed above it, which is the healthy direction.
19→20 Tool~CodeiumService uses Tool~LangChainpart of a loop✕
Connections
7 pairs of types, where a type in Tool~CodeiumService uses a type in Tool~LangChain.
Tool~CodeiumService uses Tool~LangChain, so a change to Tool~LangChain can break Tool~CodeiumService, while a change to Tool~CodeiumService can't break Tool~LangChain.
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→21 Tool~CodeiumService uses Tool~FileSystempart of a loop✕
Connections
1 pair of types, where a type in Tool~CodeiumService uses a type in Tool~FileSystem.
Tool~CodeiumService uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~CodeiumService, while a change to Tool~CodeiumService 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→23 Tool~CodeiumService uses Tool~ChatBasicpart of a loop✕
Connections
43 pairs of types, where a type in Tool~CodeiumService uses a type in Tool~ChatBasic. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Tool~CodeiumService uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~CodeiumService, while a change to Tool~CodeiumService can't break Tool~ChatBasic.
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→37 Tool~CodeiumService uses Core~ChatGPTChatTabpart of a loop✕
Connections
4 pairs of types, where a type in Tool~CodeiumService uses a type in Core~ChatGPTChatTab.
Tool~CodeiumService uses Core~ChatGPTChatTab, so a change to Core~ChatGPTChatTab can break Tool~CodeiumService, while a change to Tool~CodeiumService can't break Core~ChatGPTChatTab.
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~LangChain uses Tool~Preferences, so a change to Tool~Preferences can break Tool~LangChain, while a change to Tool~LangChain can't break Tool~Preferences.
Position
Below the diagonal: Tool~LangChain uses a module listed above it, which is the healthy direction.
Tool~LangChain uses Tool~OpenAIService, so a change to Tool~OpenAIService can break Tool~LangChain, while a change to Tool~LangChain can't break Tool~OpenAIService.
Position
Below the diagonal: Tool~LangChain uses a module listed above it, which is the healthy direction.
Tool~LangChain uses Tool~CodeiumService, so a change to Tool~CodeiumService can break Tool~LangChain, while a change to Tool~LangChain can't break Tool~CodeiumService.
Position
Below the diagonal: Tool~LangChain uses a module listed above it, which is the healthy direction.
20→23 Tool~LangChain uses Tool~ChatBasicpart of a loop✕
Connections
62 pairs of types, where a type in Tool~LangChain uses a type in Tool~ChatBasic. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Tool~LangChain uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~LangChain, while a change to Tool~LangChain can't break Tool~ChatBasic.
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~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~LangChain, so a change to Tool~LangChain can break Tool~FileSystem, while a change to Tool~FileSystem can't break Tool~LangChain.
Position
Below the diagonal: Tool~FileSystem uses a module listed above it, which is the healthy direction.
21→23 Tool~FileSystem uses Tool~ChatBasicpart of a loop✕
Connections
22 pairs of types, where a type in Tool~FileSystem uses a type in Tool~ChatBasic.
Tool~FileSystem uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~FileSystem, while a change to Tool~FileSystem can't break Tool~ChatBasic.
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~CodeDiff uses a type in Tool~Preferences.
The types involved
Tool~CodeDiff.Section → Tool~Preferences.Bool
Direction
Tool~CodeDiff uses Tool~Preferences, so a change to Tool~Preferences can break Tool~CodeDiff, while a change to Tool~CodeDiff can't break Tool~Preferences.
Position
Below the diagonal: Tool~CodeDiff uses a module listed above it, which is the healthy direction.
Tool~CodeDiff uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~CodeDiff, while a change to Tool~CodeDiff can't break Tool~FileSystem.
Position
Below the diagonal: Tool~CodeDiff uses a module listed above it, which is the healthy direction.
22→23 Tool~CodeDiff uses Tool~ChatBasicpart of a loop✕
Connections
8 pairs of types, where a type in Tool~CodeDiff uses a type in Tool~ChatBasic.
Tool~CodeDiff uses Core~ChatGPTChatTab, so a change to Core~ChatGPTChatTab can break Tool~CodeDiff, while a change to Tool~CodeDiff can't break Core~ChatGPTChatTab.
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~ChatBasic uses Tool~Preferences, so a change to Tool~Preferences can break Tool~ChatBasic, while a change to Tool~ChatBasic can't break Tool~Preferences.
Position
Below the diagonal: Tool~ChatBasic uses a module listed above it, which is the healthy direction.
Tool~ChatBasic uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Tool~ChatBasic, while a change to Tool~ChatBasic can't break Tool~SuggestionBasic.
Position
Below the diagonal: Tool~ChatBasic uses a module listed above it, which is the healthy direction.
Tool~ChatBasic uses Tool~SuggestionProvider, so a change to Tool~SuggestionProvider can break Tool~ChatBasic, while a change to Tool~ChatBasic can't break Tool~SuggestionProvider.
Position
Below the diagonal: Tool~ChatBasic uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in Tool~ChatBasic uses a type in Tool~LangChain.
The types involved
Tool~ChatBasic.ChatMessage → Tool~LangChain.Int
Direction
Tool~ChatBasic uses Tool~LangChain, so a change to Tool~LangChain can break Tool~ChatBasic, while a change to Tool~ChatBasic can't break Tool~LangChain.
Position
Below the diagonal: Tool~ChatBasic uses a module listed above it, which is the healthy direction.
Tool~ChatBasic uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~ChatBasic, while a change to Tool~ChatBasic can't break Tool~FileSystem.
Position
Below the diagonal: Tool~ChatBasic 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~SuggestionBasic, so a change to Tool~SuggestionBasic can break Core~KeyBindingManager, while a change to Core~KeyBindingManager can't break Tool~SuggestionBasic.
Position
Below the diagonal: Core~KeyBindingManager uses a module listed above it, which is the healthy direction.
Core~KeyBindingManager uses repository, so a change to repository can break Core~KeyBindingManager, while a change to Core~KeyBindingManager can't break repository.
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 Tool~XcodeInspector, so a change to Tool~XcodeInspector can break Core~KeyBindingManager, while a change to Core~KeyBindingManager can't break Tool~XcodeInspector.
Position
Below the diagonal: Core~KeyBindingManager uses a module listed above it, which is the healthy direction.
Core~KeyBindingManager uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Core~KeyBindingManager, while a change to Core~KeyBindingManager can't break Tool~ChatBasic.
Position
Below the diagonal: Core~KeyBindingManager uses a module listed above it, which is the healthy direction.
Core~LegacyChatPlugin uses Tool~Preferences, so a change to Tool~Preferences can break Core~LegacyChatPlugin, while a change to Core~LegacyChatPlugin can't break Tool~Preferences.
Position
Below the diagonal: Core~LegacyChatPlugin uses a module listed above it, which is the healthy direction.
Core~LegacyChatPlugin uses Tool~OpenAIService, so a change to Tool~OpenAIService can break Core~LegacyChatPlugin, while a change to Core~LegacyChatPlugin can't break Tool~OpenAIService.
Position
Below the diagonal: Core~LegacyChatPlugin uses a module listed above it, which is the healthy direction.
Core~LegacyChatPlugin uses Tool~LangChain, so a change to Tool~LangChain can break Core~LegacyChatPlugin, while a change to Core~LegacyChatPlugin can't break Tool~LangChain.
Position
Below the diagonal: Core~LegacyChatPlugin uses a module listed above it, which is the healthy direction.
Core~LegacyChatPlugin uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Core~LegacyChatPlugin, while a change to Core~LegacyChatPlugin can't break Tool~ChatBasic.
Position
Below the diagonal: Core~LegacyChatPlugin 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 Tool~LangChain, so a change to Tool~LangChain can break Core~XcodeThemeController, while a change to Core~XcodeThemeController can't break Tool~LangChain.
Position
Below the diagonal: Core~XcodeThemeController uses a module listed above it, which is the healthy direction.
Core~XcodeThemeController uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Core~XcodeThemeController, while a change to Core~XcodeThemeController can't break Tool~ChatBasic.
Position
Below the diagonal: Core~XcodeThemeController uses a module listed above it, which is the healthy direction.
Tool~ASTParser uses Tool~Preferences, so a change to Tool~Preferences can break Tool~ASTParser, while a change to Tool~ASTParser can't break Tool~Preferences.
Position
Below the diagonal: Tool~ASTParser uses a module listed above it, which is the healthy direction.
Tool~ASTParser uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Tool~ASTParser, while a change to Tool~ASTParser can't break Tool~SuggestionBasic.
Position
Below the diagonal: Tool~ASTParser uses a module listed above it, which is the healthy direction.
Tool~ASTParser uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~ASTParser, while a change to Tool~ASTParser can't break Tool~FileSystem.
Position
Below the diagonal: Tool~ASTParser uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in Tool~ASTParser uses a type in Tool~ChatBasic.
The types involved
Tool~ASTParser.ASTNode → Tool~ChatBasic.String
Tool~ASTParser.ASTParser → Tool~ChatBasic.String
Direction
Tool~ASTParser uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~ASTParser, while a change to Tool~ASTParser can't break Tool~ChatBasic.
Position
Below the diagonal: Tool~ASTParser 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 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~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~ChatBasic, so a change to Tool~ChatBasic can break Tool~AXNotificationStream, while a change to Tool~AXNotificationStream can't break Tool~ChatBasic.
Position
Below the diagonal: Tool~AXNotificationStream uses a module listed above it, which is the healthy direction.
Tool~ChatContextCollector uses Tool~LangChain, so a change to Tool~LangChain can break Tool~ChatContextCollector, while a change to Tool~ChatContextCollector can't break Tool~LangChain.
Position
Below the diagonal: Tool~ChatContextCollector uses a module listed above it, which is the healthy direction.
Tool~ChatContextCollector uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~ChatContextCollector, while a change to Tool~ChatContextCollector can't break Tool~ChatBasic.
Position
Below the diagonal: Tool~ChatContextCollector uses a module listed above it, which is the healthy direction.
Tool~CommandHandler uses Tool~Preferences, so a change to Tool~Preferences can break Tool~CommandHandler, while a change to Tool~CommandHandler can't break Tool~Preferences.
Position
Below the diagonal: Tool~CommandHandler uses a module listed above it, which is the healthy direction.
Tool~CommandHandler uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Tool~CommandHandler, while a change to Tool~CommandHandler can't break Tool~SuggestionBasic.
Position
Below the diagonal: Tool~CommandHandler uses a module listed above it, which is the healthy direction.
Tool~CommandHandler uses Tool~Toast, so a change to Tool~Toast can break Tool~CommandHandler, while a change to Tool~CommandHandler can't break Tool~Toast.
Position
Below the diagonal: Tool~CommandHandler uses a module listed above it, which is the healthy direction.
Tool~CommandHandler uses Tool~XcodeInspector, so a change to Tool~XcodeInspector can break Tool~CommandHandler, while a change to Tool~CommandHandler can't break Tool~XcodeInspector.
Position
Below the diagonal: Tool~CommandHandler uses a module listed above it, which is the healthy direction.
Tool~CommandHandler uses Tool~LangChain, so a change to Tool~LangChain can break Tool~CommandHandler, while a change to Tool~CommandHandler can't break Tool~LangChain.
Position
Below the diagonal: Tool~CommandHandler uses a module listed above it, which is the healthy direction.
Tool~CommandHandler uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~CommandHandler, while a change to Tool~CommandHandler can't break Tool~ChatBasic.
Position
Below the diagonal: Tool~CommandHandler uses a module listed above it, which is the healthy direction.
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 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.
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 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.
Tool~GitHubCopilotService uses Tool~LangChain, so a change to Tool~LangChain can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Tool~LangChain.
Position
Below the diagonal: Tool~GitHubCopilotService uses a module listed above it, which is the healthy direction.
33 pairs of types, where a type in Tool~GitHubCopilotService uses a type in Tool~ChatBasic. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Tool~GitHubCopilotService uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Tool~ChatBasic.
Position
Below the diagonal: Tool~GitHubCopilotService uses a module listed above it, which is the healthy direction.
Tool~ModificationBasic uses Tool~Preferences, so a change to Tool~Preferences can break Tool~ModificationBasic, while a change to Tool~ModificationBasic can't break Tool~Preferences.
Position
Below the diagonal: Tool~ModificationBasic uses a module listed above it, which is the healthy direction.
Tool~ModificationBasic uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Tool~ModificationBasic, while a change to Tool~ModificationBasic can't break Tool~SuggestionBasic.
Position
Below the diagonal: Tool~ModificationBasic uses a module listed above it, which is the healthy direction.
Tool~ModificationBasic uses Tool~LangChain, so a change to Tool~LangChain can break Tool~ModificationBasic, while a change to Tool~ModificationBasic can't break Tool~LangChain.
Position
Below the diagonal: Tool~ModificationBasic uses a module listed above it, which is the healthy direction.
Tool~ModificationBasic uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~ModificationBasic, while a change to Tool~ModificationBasic can't break Tool~FileSystem.
Position
Below the diagonal: Tool~ModificationBasic uses a module listed above it, which is the healthy direction.
Tool~ModificationBasic uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~ModificationBasic, while a change to Tool~ModificationBasic can't break Tool~ChatBasic.
Position
Below the diagonal: Tool~ModificationBasic uses a module listed above it, which is the healthy direction.
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~OpenAIService, so a change to Tool~OpenAIService can break Core~ChatService, while a change to Core~ChatService can't break Tool~OpenAIService.
Position
Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
Core~ChatService uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Core~ChatService, while a change to Core~ChatService can't break Tool~ChatBasic.
Position
Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
Core~ChatService uses Tool~ChatContextCollector, so a change to Tool~ChatContextCollector can break Core~ChatService, while a change to Core~ChatService can't break Tool~ChatContextCollector.
Position
Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
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.
Core~PromptToCodeService uses Tool~LangChain, so a change to Tool~LangChain can break Core~PromptToCodeService, while a change to Core~PromptToCodeService can't break Tool~LangChain.
Position
Below the diagonal: Core~PromptToCodeService uses a module listed above it, which is the healthy direction.
Core~PromptToCodeService uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Core~PromptToCodeService, while a change to Core~PromptToCodeService can't break Tool~ChatBasic.
Position
Below the diagonal: Core~PromptToCodeService uses a module listed above it, which is the healthy direction.
Core~PromptToCodeService uses Tool~ModificationBasic, so a change to Tool~ModificationBasic can break Core~PromptToCodeService, while a change to Core~PromptToCodeService can't break Tool~ModificationBasic.
Position
Below the diagonal: Core~PromptToCodeService 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~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 OverlayWindow~OverlayWindow, so a change to OverlayWindow~OverlayWindow can break Core~Service, while a change to Core~Service can't break OverlayWindow~OverlayWindow.
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~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.
Core~Service uses Tool~CommandHandler, so a change to Tool~CommandHandler can break Core~Service, while a change to Core~Service can't break Tool~CommandHandler.
Position
Below the diagonal: Core~Service uses a module listed above it, which is the healthy direction.
Tool~FocusedCodeFinder uses Tool~Preferences, so a change to Tool~Preferences can break Tool~FocusedCodeFinder, while a change to Tool~FocusedCodeFinder can't break Tool~Preferences.
Position
Below the diagonal: Tool~FocusedCodeFinder uses a module listed above it, which is the healthy direction.
Tool~FocusedCodeFinder uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Tool~FocusedCodeFinder, while a change to Tool~FocusedCodeFinder can't break Tool~SuggestionBasic.
Position
Below the diagonal: Tool~FocusedCodeFinder uses a module listed above it, which is the healthy direction.
Tool~FocusedCodeFinder uses Tool~LangChain, so a change to Tool~LangChain can break Tool~FocusedCodeFinder, while a change to Tool~FocusedCodeFinder can't break Tool~LangChain.
Position
Below the diagonal: Tool~FocusedCodeFinder uses a module listed above it, which is the healthy direction.
Tool~FocusedCodeFinder uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~FocusedCodeFinder, while a change to Tool~FocusedCodeFinder can't break Tool~FileSystem.
Position
Below the diagonal: Tool~FocusedCodeFinder uses a module listed above it, which is the healthy direction.
Tool~FocusedCodeFinder uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~FocusedCodeFinder, while a change to Tool~FocusedCodeFinder can't break Tool~ChatBasic.
Position
Below the diagonal: Tool~FocusedCodeFinder uses a module listed above it, which is the healthy direction.
Tool~FocusedCodeFinder uses Tool~ASTParser, so a change to Tool~ASTParser can break Tool~FocusedCodeFinder, while a change to Tool~FocusedCodeFinder can't break Tool~ASTParser.
Position
Below the diagonal: Tool~FocusedCodeFinder uses a module listed above it, which is the healthy direction.
Core~ChatGPTChatTab uses Tool~Preferences, so a change to Tool~Preferences can break Core~ChatGPTChatTab, while a change to Core~ChatGPTChatTab can't break Tool~Preferences.
Position
Below the diagonal: Core~ChatGPTChatTab uses a module listed above it, which is the healthy direction.
Core~ChatGPTChatTab uses repository, so a change to repository can break Core~ChatGPTChatTab, while a change to Core~ChatGPTChatTab can't break repository.
Position
Below the diagonal: Core~ChatGPTChatTab uses a module listed above it, which is the healthy direction.
Core~ChatGPTChatTab uses Core~SuggestionWidget, so a change to Core~SuggestionWidget can break Core~ChatGPTChatTab, while a change to Core~ChatGPTChatTab can't break Core~SuggestionWidget.
Position
Below the diagonal: Core~ChatGPTChatTab uses a module listed above it, which is the healthy direction.
Core~ChatGPTChatTab uses Tool~ChatTab, so a change to Tool~ChatTab can break Core~ChatGPTChatTab, while a change to Core~ChatGPTChatTab can't break Tool~ChatTab.
Position
Below the diagonal: Core~ChatGPTChatTab uses a module listed above it, which is the healthy direction.
Core~ChatGPTChatTab uses Tool~LangChain, so a change to Tool~LangChain can break Core~ChatGPTChatTab, while a change to Core~ChatGPTChatTab can't break Tool~LangChain.
Position
Below the diagonal: Core~ChatGPTChatTab uses a module listed above it, which is the healthy direction.
Core~ChatGPTChatTab uses Tool~FileSystem, so a change to Tool~FileSystem can break Core~ChatGPTChatTab, while a change to Core~ChatGPTChatTab can't break Tool~FileSystem.
Position
Below the diagonal: Core~ChatGPTChatTab uses a module listed above it, which is the healthy direction.
Core~ChatGPTChatTab uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Core~ChatGPTChatTab, while a change to Core~ChatGPTChatTab can't break Tool~ChatBasic.
Position
Below the diagonal: Core~ChatGPTChatTab uses a module listed above it, which is the healthy direction.
Core~ChatGPTChatTab uses Core~ChatService, so a change to Core~ChatService can break Core~ChatGPTChatTab, while a change to Core~ChatGPTChatTab can't break Core~ChatService.
Position
Below the diagonal: Core~ChatGPTChatTab uses a module listed above it, which is the healthy direction.
Core~ChatGPTChatTab uses Tool~FocusedCodeFinder, so a change to Tool~FocusedCodeFinder can break Core~ChatGPTChatTab, while a change to Core~ChatGPTChatTab can't break Tool~FocusedCodeFinder.
Position
Below the diagonal: Core~ChatGPTChatTab uses a module listed above it, which is the healthy direction.
Tool~ChatContextCollectors uses Tool~Preferences, so a change to Tool~Preferences can break Tool~ChatContextCollectors, while a change to Tool~ChatContextCollectors can't break Tool~Preferences.
Position
Below the diagonal: Tool~ChatContextCollectors uses a module listed above it, which is the healthy direction.
Tool~ChatContextCollectors uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Tool~ChatContextCollectors, while a change to Tool~ChatContextCollectors can't break Tool~SuggestionBasic.
Position
Below the diagonal: Tool~ChatContextCollectors uses a module listed above it, which is the healthy direction.
Tool~ChatContextCollectors uses Tool~LangChain, so a change to Tool~LangChain can break Tool~ChatContextCollectors, while a change to Tool~ChatContextCollectors can't break Tool~LangChain.
Position
Below the diagonal: Tool~ChatContextCollectors uses a module listed above it, which is the healthy direction.
Tool~ChatContextCollectors uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~ChatContextCollectors, while a change to Tool~ChatContextCollectors can't break Tool~ChatBasic.
Position
Below the diagonal: Tool~ChatContextCollectors uses a module listed above it, which is the healthy direction.
Tool~ChatContextCollectors uses Tool~ChatContextCollector, so a change to Tool~ChatContextCollector can break Tool~ChatContextCollectors, while a change to Tool~ChatContextCollectors can't break Tool~ChatContextCollector.
Position
Below the diagonal: Tool~ChatContextCollectors uses a module listed above it, which is the healthy direction.
Tool~ChatContextCollectors uses Tool~FocusedCodeFinder, so a change to Tool~FocusedCodeFinder can break Tool~ChatContextCollectors, while a change to Tool~ChatContextCollectors can't break Tool~FocusedCodeFinder.
Position
Below the diagonal: Tool~ChatContextCollectors uses a module listed above it, which is the healthy direction.
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~LangChain, so a change to Tool~LangChain can break Tool~SharedUIComponents, while a change to Tool~SharedUIComponents can't break Tool~LangChain.
Position
Below the diagonal: Tool~SharedUIComponents uses a module listed above it, which is the healthy direction.
Tool~SharedUIComponents uses Tool~CodeDiff, so a change to Tool~CodeDiff can break Tool~SharedUIComponents, while a change to Tool~SharedUIComponents can't break Tool~CodeDiff.
Position
Below the diagonal: Tool~SharedUIComponents uses a module listed above it, which is the healthy direction.
Tool~SharedUIComponents uses Tool~ChatBasic, so a change to Tool~ChatBasic can break Tool~SharedUIComponents, while a change to Tool~SharedUIComponents can't break Tool~ChatBasic.
Position
Below the diagonal: Tool~SharedUIComponents uses a module listed above it, which is the healthy direction.
Tool~SharedUIComponents uses Tool~FocusedCodeFinder, so a change to Tool~FocusedCodeFinder can break Tool~SharedUIComponents, while a change to Tool~SharedUIComponents can't break Tool~FocusedCodeFinder.
Position
Below the diagonal: Tool~SharedUIComponents uses a module listed above it, which is the healthy direction.
Tool~SharedUIComponents uses Core~ChatGPTChatTab, so a change to Core~ChatGPTChatTab can break Tool~SharedUIComponents, while a change to Tool~SharedUIComponents can't break Core~ChatGPTChatTab.
Position
Below the diagonal: Tool~SharedUIComponents uses a module listed above it, which is the healthy direction.
37 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~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.
Core~HostApp uses Tool~OpenAIService, so a change to Tool~OpenAIService can break Core~HostApp, while a change to Core~HostApp can't break Tool~OpenAIService.
Position
Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
Core~HostApp uses Tool~CodeiumService, so a change to Tool~CodeiumService can break Core~HostApp, while a change to Core~HostApp can't break Tool~CodeiumService.
Position
Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
Core~HostApp uses Tool~CommandHandler, so a change to Tool~CommandHandler can break Core~HostApp, while a change to Core~HostApp can't break Tool~CommandHandler.
Position
Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
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.
105 pairs of types, where a type in Core~HostApp uses a type in Core~ChatGPTChatTab. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Core~HostApp uses Core~ChatGPTChatTab, so a change to Core~ChatGPTChatTab can break Core~HostApp, while a change to Core~HostApp can't break Core~ChatGPTChatTab.
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.
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
A07:2025 — Authentication Failures
2
High / Critical
A05:2025 — Injection
1
High / Critical
Roadmap
Top priorities: Resolve the 1 finding(s) in Immutable events; Resolve the 18 Floating branch dependency finding(s) in Dependency Hygiene; Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with SwiftFocusedCodeFinderTests.swift.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
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.
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 — 438
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 39 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 39 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, 423 of 514 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 ChatPlugins 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 (4 packages), but it was not re-run: the analyzer environment could not run it. 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. 4 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, generative-ai-swift, keyboardshortcuts.
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 (13 contributor(s) across 3499 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 12 hold 0.1% 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.
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 — 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. 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/ChatGPTChatTab/ChatPanel.swift`, `Core/Sources/ChatGPTChatTab/Views/BotMessage.swift`, `Core/Sources/ChatGPTChatTab/Views/FunctionMessage.swift`, `Core/Sources/ChatGPTChatTab/Views/UserMessage.swift`, … (+53 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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: a native UI project (ExtensionService/Main.storyboard). 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 Swift, c, objectivec 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 Swift, c, objectivec 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.
P5 DR & Backup — 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. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Objective-C, Swift (Foundation mutable collections) 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.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's C, Objectivec, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
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 REDACTED Scanning: REDACTED 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.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
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.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
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.
41 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was RequestBody.init at 54. A further 7 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 CodeiumSupportedLanguage.init at 66 — they are counted neither in the figure above nor in this dimension's score. 6 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/CodeiumService/LanguageServer/CodeiumSupportedLanguage.swift (CodeiumSupportedLanguage.init at 66), Tool/Sources/SuggestionBasic/LanguageIdentifierFromFilePath.swift (LanguageIdentifier.fileExtensions at 58), Core/Sources/ChatGPTChatTab/Views/BotMessage.swift (ReferenceIcon.body at 35), Tool/Sources/Preferences/Types/ChatGPTModel.swift (ChatGPTModel.maxToken at 21), Tool/Sources/FocusedCodeFinder/Swift/SwiftFocusedCodeFinder.swift (SwiftFocusedCodeFinder.contextContainingNode at 18), and 1 more not listed here. 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.
+ 36 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 41 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with RequestBody.init (cyclomatic 54), Chat.body (cyclomatic 50), ChatPanel.body (cyclomatic 47). — 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 41 together lifts Cyclomatic Complexity from 6.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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.
+ 70 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with RequestBody.init (cognitive 145), ExplanationThenCodeStreamParser.yield (cognitive 100), ChatGPTService.send (cognitive 75). — 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 3 together lifts Cognitive Complexity from 5.3 to about 6.3/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.4 / 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 17 MethodTooLong finding(s) in God Classes — start with Chat.swift, OpenAIChatCompletionsService.swift, SwiftFocusedCodeFinder.swift. — One of this dimension's main actionable groups (17 warning-level).
Resolve the 3 FileTooLong finding(s) in God Classes — start with PromptToCodePanelView.swift, OpenAIChatCompletionsService.swift, PseudoCommandHandler.swift. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 FunctionTooLong finding(s) in God Classes — start with PromptToCodePanelView.swift. — One of this dimension's main actionable groups (1 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.
121 duplicated block group(s) detected. 10.5 % of the production lines (5,958 of 56,856) are in a reported copy. A further 99 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 (13 corresponding lines) · ×7Core/Sources/SuggestionWidget/ChatWindowView.swift:148
Edited copy of a member (14 corresponding lines) · ×7Tool/Sources/SharedUIComponents/CustomTextEditor.swift:11
+ 106 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with ChatWindowView.swift, CodeiumInstallationManager.swift, QAInformationRetrievalChain.swift. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 7 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with CustomTextEditor.swift, ActiveDocumentChatContextCollector.swift, UsearchIndex.swift. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with SuggestionFeatureDisabledLanguageListView.swift, OpenAIPromptToCodeService.swift, SharedPanelView.swift. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling7.5 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
75 production modules (SwiftPM+Xcode), 0 dependency cycle(s), 2 unstable depended-on module(s). Read from the build's own module declarations; a workspace's implicit (product-name) dependency is not visible there; 21 module(s) off the main sequence, with abstractness counted on 72 of the 75 (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: AIModel · ×21
Unstable project ChatGPTChatTab
Unstable project CodeiumService
What to do
Resolve the 21 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (21 warning-level).
Resolve the 1 Unstable project ChatGPTChatTab finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project CodeiumService 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 9 Low cohesion finding(s) in Cohesion (LCOM4) — start with ChatGPTFunction.swift, Styles.swift, GitHubCopilotService.swift. — One of this dimension's main actionable groups (9 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.3 / 10Adequategated by 5 critical findings✓ 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, 7 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 214 tests.
Assertions commented out: example · ×2ChatPlugins/Tests/ChatPluginsTests/ChatPluginsTests.swift:4
Test project verifies nothing: ChatPluginsTests · ×2ChatPlugins/Tests/ChatPluginsTests/ChatPluginsTests.swift:4
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 · ×4Tool/Tests/SuggestionBasicTests/BreakLinePerformanceTests.swift:6
What to do
Resolve the 2 Assertions commented out finding(s) in Test Quality — start with ChatPluginsTests.swift, WindowTests.swift. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 2 Test project verifies nothing finding(s) in Test Quality — start with ChatPluginsTests.swift, WindowTests.swift. — One of this dimension's main actionable groups (2 issue-level).
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).
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.
51 outdated direct SwiftPM dependencies, 22 pinning defect(s). 83 of 104 direct dependencies had their releases listed (0 naming no readable repository, 21 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.
Dependency not covered by the committed resolution: keyboardshortcuts · ×4
Outdated: aexml · ×37
What to do
Resolve the 18 Floating branch dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (18 warning-level).
Resolve the 4 Dependency not covered by the committed resolution finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 49 SwiftPM package(s) use a banned license. SwiftPM has no package registry, so each package's licence is the one its repository declares: 45 of them read from the licence file the repository carries at the revision Package.resolved pins, and 4 — unpinned, or whose licence file could not be read or named — from api.deps.dev, which reports the licence the repository declares today. Graded: every package a committed Package.resolved pins, direct and transitive, and every declared dependency none pins. 6 of them are declared by a manifest that commits no Package.resolved (a library, whose resolution is its consumer's), so their own dependencies are resolved by whoever builds it and are not in this verdict. 2 of them declare no licence that matches a known SPDX licence; that is missing data, not a violation, and none of them is charged. ★ 4 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`, `generative-ai-swift`, `keyboardshortcuts`.
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.
7 deducted task-comment markers across 56856 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 6 TodoComment finding(s) in Explicit Debt — start with AXUIElement.swift (2), Package.swift, SwiftFocusedCodeFinderTests.swift. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with EditableText.swift. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
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.
6 naming inconsistencies among 226 declarations measured against a convention their peers follow.
`codeiumPortalUrl` spells `Url` where 42 names in the project spell it `URL`Core/Sources/HostApp/AccountSettings/CodeiumView.swift:15
`codeiumApiUrl` spells `Url` where 42 names in the project spell it `URL`Core/Sources/HostApp/AccountSettings/CodeiumView.swift:16
`codeiumPortalUrl` spells `Url` where 151 names in the project spell it `URL`Tool/Sources/Preferences/Keys.swift:224
`codeiumApiUrl` spells `Url` where 151 names in the project spell it `URL`Tool/Sources/Preferences/Keys.swift:228
`webSearchUrl` spells `Url` where 151 names in the project spell it `URL`Tool/Sources/WebSearchService/SearchServices/BingSearchService.swift:7
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 `codeiumPortalUrl` spells `Url` where 42 names in the project spell it… finding(s) in Naming Consistency — start with CodeiumView.swift. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `codeiumApiUrl` spells `Url` where 42 names in the project spell it… finding(s) in Naming Consistency — start with CodeiumView.swift. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `codeiumPortalUrl` spells `Url` where 151 names in the project spell it… finding(s) in Naming Consistency — start with Keys.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.
2 of 5 build units (SwiftPM, Xcode) 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: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED 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.
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. 1 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `Core/Sources/LaunchAgentManager/LaunchAgentManager.swift` (line 69) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
What to do
No action in Static Analysis (SAST) — all 1 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (1 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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 237 of the 396 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.
Resolve the 7 Change coupling finding(s) in Change Coupling — start with DebugView.swift, ChatPanel.swift, AskChatGPT.swift. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with SuggestionCommandHandler.swift. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with ChatGPTService.swift. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
`ActiveDocumentChatContextCollector.getActiveDocumentContext` is a read-named query yet it performs a durable write on the read path (a persist to a store/client). A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the write into a command. — Tool/Sources/ChatContextCollectors/ActiveDocumentChatContextCollector/ActiveDocumentChatContextCollector.swift:102
What to do
Keep query handlers read-only — move the writes/event-publishes into a command handler so reads stay safe to retry, cache, and route to a read replica.
Other · Event Sourcing — Whether domain events stay immutable (a `struct` with `let` fields) rather than carrying mutable state.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
`UnTypedEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten. — Tool/Sources/LangChain/Callback.swift:9
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Do you agree with this assessment?
P1 · CI/CD gates1.5 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
A workflow is configured, but the repository's only workflow is `REDACTED`, which neither runs on a code change (no `push` or `pull_request` trigger) nor checks the code out — so nothing here builds or tests a change before it merges. This is automation for the repository's ISSUES AND HOUSEKEEPING, not a gate on its code: a pull request can land without anything having compiled or run it. The rows about missing build and test steps are deliberately not reported beside this one, because there is no pipeline for them to be missing from — adding the gate is one action, not three.
What to do
Add a CI workflow that triggers on push and pull_request, checks the code out, and runs the build and the test suite — so a change cannot merge without having been compiled and exercised.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language'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.
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.
No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×18) — Tool/Sources/XPCShared/XPCService.swift:160, Tool/Sources/WebSearchService/SearchServices/HeadlessBrowserSearchService.swift:120, Tool/Sources/LangChain/VectorStore/TemporaryUSearch.swift:37, …
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. (×2) — Tool/Sources/SharedUIComponents/SyntaxHighlighting.swift:303, Core/Sources/ChatService/ChatService.swift:112
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 1 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.
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 — 74 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No 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 — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
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.
D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
D22 Internal API Consistency — 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"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .swift source were not judged.
D25 ADR Conformance — no ADRs to check
D27 Navigability — symbol resolution incomplete — navigability not assessed
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) — 58 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). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — Swift suite
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Fold determinism — not applicable — the code was read and holds no event-replay fold, so there is nothing for this check to judge
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, Swift source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X12 Unreachable branch — X12 reached only 0% of this repository's production lines — swift (53,158 lines), objectivec (15 lines), c (5 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — 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
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
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Assertions commented out: example ChatPlugins/Tests/ChatPluginsTests/ChatPluginsTests.swift:4— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
Assertions commented out: example OverlayWindow/Tests/OverlayWindowTests/WindowTests.swift:3— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
D10 · Test Quality· Test project verifies nothing · ×2
Test project verifies nothing: ChatPluginsTests ChatPlugins/Tests/ChatPluginsTests/ChatPluginsTests.swift:4— No conventional assertion call was detected in 1 of 1 tests in `ChatPluginsTests` — the project as a whole, not one method. 1 of them has its assertions commented out, so this suite did verify conventionally and was switched off — it is not an approval/verifier harness.
Test project verifies nothing: OverlayWindowTests OverlayWindow/Tests/OverlayWindowTests/WindowTests.swift:3— No conventional assertion call was detected in 1 of 1 tests in `OverlayWindowTests` — the project as a whole, not one method. 1 of them has its assertions commented out, so this suite did verify conventionally and was switched off — it is not an approval/verifier harness.
AX9 · CQS / query purity· Query writes persistent state on the read path · ×1
Query writes persistent state on the read path: ActiveDocumentChatContextCollector.getActiveDocumentContext Tool/Sources/ChatContextCollectors/ActiveDocumentChatContextCollector/ActiveDocumentChatContextCollector.swift:102— `ActiveDocumentChatContextCollector.getActiveDocumentContext` is a read-named query yet it performs a durable write on the read path (a persist to a store/client). A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the write into a command.
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.
Mutable domain event: UnTypedEvent Tool/Sources/LangChain/Callback.swift:9— `UnTypedEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten.
Off the main sequence: AIModel — AIModel: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: ActiveApplicationMonitor — ActiveApplicationMonitor: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 7 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: Client — Client: 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 2 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: JoinJSON — JoinJSON: 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: LaunchAgentManager — LaunchAgentManager: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: Logger — Logger: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 13 project(s), so it's rigid to change.
Off the main sequence: PromptToCodeService — PromptToCodeService: 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: SuggestionBasic — SuggestionBasic: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 16 project(s), so it's rigid to change.
Off the main sequence: Toast — Toast: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 4 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 4 project(s), so it's rigid to change.
Off the main sequence: WebScrapper — WebScrapper: 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: HostApp — HostApp: abstractness 0.02, instability 0.00, distance 0.98 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: Service — Service: abstractness 0.06, instability 0.00, distance 0.94 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: AXExtension — AXExtension: abstractness 0.00, instability 0.11, distance 0.89 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
Off the main sequence: AppActivator — AppActivator: abstractness 0.00, instability 0.13, distance 0.88 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: AXNotificationStream — AXNotificationStream: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
Off the main sequence: ChatService — ChatService: abstractness 0.25, instability 0.00, distance 0.75 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
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: 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: tiktoken — Dependency `tiktoken` 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: 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: generative-ai-swift — Dependency `generative-ai-swift` is declared in Tool/Package.swift against branch `support-setting-base-url` — 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 `feature/custom-chat-tab` — 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: swifttreesitter — Dependency `swifttreesitter` 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: tree-sitter-objc — Dependency `tree-sitter-objc` is declared in Tool/Package.swift against branch `feature/spm` — 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: splash — Dependency `splash` is resolved in Copilot for Xcode.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved 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: tiktoken — Dependency `tiktoken` is resolved in Copilot for Xcode.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved 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: copilotforxcodekit — Dependency `copilotforxcodekit` is resolved in Copilot for Xcode.xcworkspace/xcshareddata/swiftpm/Package.resolved against branch `feature/custom-chat-tab` 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: generative-ai-swift — Dependency `generative-ai-swift` is resolved in Copilot for Xcode.xcworkspace/xcshareddata/swiftpm/Package.resolved against branch `support-setting-base-url` 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 Copilot for Xcode.xcworkspace/xcshareddata/swiftpm/Package.resolved 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: indexstore-db — Dependency `indexstore-db` is resolved in Copilot for Xcode.xcworkspace/xcshareddata/swiftpm/Package.resolved against branch `release/6.1` 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 Copilot for Xcode.xcworkspace/xcshareddata/swiftpm/Package.resolved 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: swifttreesitter — Dependency `swifttreesitter` is resolved in Copilot for Xcode.xcworkspace/xcshareddata/swiftpm/Package.resolved 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: tiktoken — Dependency `tiktoken` is resolved in Copilot for Xcode.xcworkspace/xcshareddata/swiftpm/Package.resolved 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: tree-sitter-objc — Dependency `tree-sitter-objc` is resolved in Copilot for Xcode.xcworkspace/xcshareddata/swiftpm/Package.resolved against branch `feature/spm` 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.
Swallowed exception (caught, then discarded) Tool/Sources/XPCShared/XPCService.swift:160— `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/WebSearchService/SearchServices/HeadlessBrowserSearchService.swift:120— `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/LangChain/VectorStore/TemporaryUSearch.swift:37— `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/LangChain/VectorStore/TemporaryUSearch.swift:48— `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/LangChain/Chains/RelevantInformationExtractionChain.swift:124— `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/LangChain/Chains/RelevantInformationExtractionChain.swift:136— `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/LangChain/Chains/StructuredOutputChatModelChain.swift:119— `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/GitIgnoreCheck/GitIgnoreCheck.swift:63— `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/GitIgnoreCheck/GitIgnoreCheck.swift:87— `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/GitHubCopilotService/Services/GitHubCopilotChatService.swift:116— `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/GitHubCopilotService/Services/GitHubCopilotChatService.swift:126— `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/ChatContextCollector/ChatContextCollector.swift:93— `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/XcodeThemeController/XcodeThemeController.swift:242— `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/Service/RealtimeSuggestionController.swift:129— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
MethodTooLong: Chat.body Core/Sources/ChatGPTChatTab/Chat.swift:128— MethodTooLong — body runs 194 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 94 over it, 1.94× 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: RequestBody.init Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:1049— MethodTooLong — init runs 179 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 79 over it, 1.79× 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: SwiftFocusedCodeFinder.contextContainingNode Tool/Sources/FocusedCodeFinder/Swift/SwiftFocusedCodeFinder.swift:63— MethodTooLong — contextContainingNode runs 178 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 78 over it, 1.78× 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: General.body Core/Sources/HostApp/General.swift:56— MethodTooLong — body runs 167 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× 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: SimpleModificationAgent.modifyCode Core/Sources/PromptToCodeService/OpenAIPromptToCodeService.swift:47— MethodTooLong — modifyCode runs 167 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× 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: Widget.body Core/Sources/SuggestionWidget/FeatureReducers/Widget.swift:129— MethodTooLong — body runs 163 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× 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:106— MethodTooLong — parseXCColorTheme runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× 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: ChatPanel.body Core/Sources/SuggestionWidget/FeatureReducers/ChatPanel.swift:96— MethodTooLong — body runs 145 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× 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: PromptToCodePanel.body Core/Sources/SuggestionWidget/FeatureReducers/PromptToCodePanel.swift:110— MethodTooLong — body runs 145 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× 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:104— MethodTooLong — framesForWindows runs 142 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× 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: GitHubCopilotView.body Core/Sources/HostApp/AccountSettings/GitHubCopilotView.swift:145— MethodTooLong — body runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× 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: CodeiumSupportedLanguage.init Tool/Sources/CodeiumService/LanguageServer/CodeiumSupportedLanguage.swift:72— MethodTooLong — init runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× 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: GitHubCopilotBaseService.init Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:129— MethodTooLong — init runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× 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: ChatModelEdit.body Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift:98— MethodTooLong — body runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× 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: GUI.body Core/Sources/Service/GUI/GraphicalUserInterfaceController.swift:82— MethodTooLong — body runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× 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: EmbeddingModelEdit.body Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEdit.swift:83— MethodTooLong — body runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Low cohesion: String (LCOM4 13) Tool/Sources/ChatBasic/ChatGPTFunction.swift:38— String's methods fall into 13 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 13 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: View (LCOM4 12) Core/Sources/ChatGPTChatTab/Styles.swift:36— View'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: GitHubCopilotService (LCOM4 8) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:436— GitHubCopilotService's methods fall into 8 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 8 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 7) Tool/Sources/AXExtension/AXUIElement.swift:7— AXUIElement'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: AppDelegate (LCOM4 7) CommunicationBridge/main.swift:4— AppDelegate'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: UpdaterDelegate (LCOM4 5) Core/Sources/UpdateChecker/UpdateChecker.swift:58— UpdaterDelegate'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: BuiltinExtensionSuggestionServiceProvider (LCOM4 4) Tool/Sources/BuiltinExtension/BuiltinExtensionSuggestionServiceProvider.swift:8— BuiltinExtensionSuggestionServiceProvider'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: ChatAgent (LCOM4 4) Tool/Sources/LangChain/Agents/ChatAgent.swift:36— ChatAgent'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: AppDelegate (LCOM4 4) ExtensionService/AppDelegate.swift:20— AppDelegate'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.
Change coupling: DebugView.swift ↔ Keys.swift Core/Sources/HostApp/DebugView.swift:1— `Core/Sources/HostApp/DebugView.swift` and `Tool/Sources/Preferences/Keys.swift` change together 70% of the time (14 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `4543fb2b` Add toggle to prevent automatic launch agent installation; `300f1c01` Add toggle to use Cloudflare domain name for license check; `1ba39c71` Remove a feature flag — run `git show` on any of them.
Change coupling: ChatPanel.swift ↔ Styles.swift Core/Sources/ChatGPTChatTab/ChatPanel.swift:1— `Core/Sources/ChatGPTChatTab/ChatPanel.swift` and `Core/Sources/ChatGPTChatTab/Styles.swift` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `cf9181ca` Improve code highlighting performance in chat; `2effc397` Improve performance of code highlighting in chat; `b8433c19` Support changing code font of suggestion, chat and prompt to code — run `git show` on any of them.
Change coupling: AskChatGPT.swift ↔ OpenAIPromptToCodeService.swift Core/Sources/LegacyChatPlugin/AskChatGPT.swift:1— `Core/Sources/LegacyChatPlugin/AskChatGPT.swift` and `Core/Sources/PromptToCodeService/OpenAIPromptToCodeService.swift` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `b29d1aa3` Fix message count (at that commit the file was still `Core/Sources/ChatPlugin/AskChatGPT.swift`); `d4c9c242` WIP (at that commit the file was still `Core/Sources/ChatPlugin/AskChatGPT.swift`); `2e88f832` Count functions tokens (at that commit the files were still `Core/Sources/ChatPlugin/AskChatGPT.swift` and `Core/Sources/PromptToCodeService/OpenAIPromptToCodeAPI.swift`) — run `git show` on any of them.
Change coupling: DynamicContextController.swift ↔ LegacyActiveDocumentChatContextCollector.swift Core/Sources/ChatService/DynamicContextController.swift:1— `Core/Sources/ChatService/DynamicContextController.swift` and `Tool/Sources/ChatContextCollectors/ActiveDocumentChatContextCollector/LegacyActiveDocumentChatContextCollector.swift` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `956f7129` Add Scope enum to represent scopes; `60f4ff59` Adjust ChatContext (at that commit the file was still `Core/Sources/ChatContextCollectors/ActiveDocumentChatContextCollector/LegacyActiveDocumentChatContextCollector.swift`); `68575c2f` ChatContextCollector (at that commit the file was still `Core/Sources/ChatContextCollectors/ActiveDocumentChatContextCollector/LegacyActiveDocumentChatContextCollector.swift`) — run `git show` on any of them.
Change coupling: PresentInWindowSuggestionPresenter.swift ↔ SuggestionWidgetController.swift Core/Sources/Service/SuggestionPresenter/PresentInWindowSuggestionPresenter.swift:1— `Core/Sources/Service/SuggestionPresenter/PresentInWindowSuggestionPresenter.swift` and `Core/Sources/SuggestionWidget/SuggestionWidgetController.swift` change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `2a36d2e3` Tweak the behavior of activating the app on chat; `11a47625` Support prompt to code in widget; `2166af45` Isolate chat box and suggestion panel — run `git show` on any of them.
Change coupling: ChatGPTMemory.swift ↔ Models.swift Tool/Sources/OpenAIService/Memory/ChatGPTMemory.swift:1— `Tool/Sources/OpenAIService/Memory/ChatGPTMemory.swift` and `Tool/Sources/OpenAIService/Models.swift` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `21d7ae4c` Put tool call responses into the tool call struct; `a412c23f` Move tool call responses into its source assistant message; `42a8efb1` Support tool call — run `git show` on any of them.
Change coupling: Widget.swift ↔ AppActivator.swift Core/Sources/SuggestionWidget/FeatureReducers/Widget.swift:1— `Core/Sources/SuggestionWidget/FeatureReducers/Widget.swift` and `Tool/Sources/AppActivator/AppActivator.swift` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `de89a060` Use new form of XcodeInspector; `9bee878a` Access XcodeInspector thru actor (at that commit the file was still `Core/Sources/SuggestionWidget/FeatureReducers/WidgetFeature.swift`); `84fc894d` Make runningApplication private (at that commit the file was still `Core/Sources/SuggestionWidget/FeatureReducers/WidgetFeature.swift`) — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×7
Edited copy of a member (13 corresponding lines) Core/Sources/SuggestionWidget/ChatWindowView.swift:148— Core/Sources/SuggestionWidget/ChatWindowView.swift:148-162 | Core/Sources/SuggestionWidget/PromptToCodePanelGroupView.swift:38-50 — 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/CodeiumService/LanguageServer/CodeiumInstallationManager.swift:201— Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift:201-213 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotInstallationManager.swift:198-210 — 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/LangChain/Chains/QAInformationRetrievalChain.swift:17— Tool/Sources/LangChain/Chains/QAInformationRetrievalChain.swift:17-29 | Tool/Sources/LangChain/Chains/QAInformationRetrievalChain.swift:31-43 — 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/AccountSettings/ChatModelManagement/ChatModelEditView.swift:382— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:382-398 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:292-304 — 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/OpenAIService/APIs/OpenAIChatCompletionsService.swift:238— Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:238-250 | Tool/Sources/Workspace/Filespace.swift:37-49 — 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/PromptToCodeService/PromptToCodeServiceType.swift:13— Core/Sources/PromptToCodeService/PromptToCodeServiceType.swift:13-27 | Tool/Sources/ModificationBasic/ModificationAgent.swift:28-40 — 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 (14 corresponding lines) · ×7
Edited copy of a member (14 corresponding lines) Tool/Sources/SharedUIComponents/CustomTextEditor.swift:11— Tool/Sources/SharedUIComponents/CustomTextEditor.swift:11-26 | Tool/Sources/SharedUIComponents/CustomTextEditor.swift:61-74 — 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/ChatContextCollectors/ActiveDocumentChatContextCollector/ActiveDocumentChatContextCollector.swift:88— Tool/Sources/ChatContextCollectors/ActiveDocumentChatContextCollector/ActiveDocumentChatContextCollector.swift:88-104 | Tool/Sources/FocusedCodeFinder/ActiveDocumentContext.swift:84-97 — 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/USearchIndex/UsearchIndex.swift:59— Tool/Sources/USearchIndex/UsearchIndex.swift:59-72 | Tool/Sources/USearchIndex/UsearchIndex.swift:74-87 — 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/CodeiumService/CodeiumWorkspacePlugin.swift:39— Tool/Sources/CodeiumService/CodeiumWorkspacePlugin.swift:39-54 | Tool/Sources/GitHubCopilotService/GitHubCopilotWorkspacePlugin.swift:67-80 — 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/ChatService/ChatService.swift:252— Core/Sources/ChatService/ChatService.swift:252-266 | Core/Sources/ChatService/ChatService.swift:268-281 — 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/DebounceFunction/ThrottleFunction.swift:22— Tool/Sources/DebounceFunction/ThrottleFunction.swift:22-35 | Tool/Sources/DebounceFunction/ThrottleFunction.swift:59-72 — 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/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift:69— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift:69-86 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEdit.swift:58-71 — 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.
TodoComment Tool/Package.swift:65— // 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/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/AXExtension/AXUIElement.swift:337— /// - 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 Tool/Sources/AXExtension/AXUIElement.swift:399— /// - 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 Core/Tests/ServiceTests/FilespaceSuggestionInvalidationTests.swift:44— // TODO: What — 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:165— // 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.
Duplicated block (13 lines × 2) Core/Sources/HostApp/FeatureSettings/Suggestion/SuggestionFeatureDisabledLanguageListView.swift:21— Core/Sources/HostApp/FeatureSettings/Suggestion/SuggestionFeatureDisabledLanguageListView.swift:21-33 | Core/Sources/HostApp/FeatureSettings/Suggestion/SuggestionFeatureEnabledProjectListView.swift:20-32 — before extracting anything, compare `Core/Sources/HostApp/FeatureSettings/Suggestion/SuggestionFeatureDisabledLanguageListView.swift` and `Core/Sources/HostApp/FeatureSettings/Suggestion/SuggestionFeatureEnabledProjectListView.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — 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/FeatureSettings/Suggestion/SuggestionFeatureDisabledLanguageListView.swift:21` 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/PromptToCodeService/OpenAIPromptToCodeService.swift:15— Core/Sources/PromptToCodeService/OpenAIPromptToCodeService.swift:15-27 | Core/Sources/PromptToCodeService/PreviewPromptToCodeService.swift:12-24 — 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/PromptToCodeService/OpenAIPromptToCodeService.swift:15` 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 (13 lines × 2) Core/Sources/SuggestionWidget/SharedPanelView.swift:47— Core/Sources/SuggestionWidget/SharedPanelView.swift:47-59 | Core/Sources/SuggestionWidget/SuggestionPanelView.swift:31-43 — 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/SharedPanelView.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 (13 lines × 2) Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift:187— Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift:187-199 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotInstallationManager.swift:184-196 — before extracting anything, compare `Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift` and `Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotInstallationManager.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift:187` 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 (13 lines × 2) Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:79— Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:79-91 | Tool/Sources/SharedUIComponents/CodeBlock.swift:75-87 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:79` 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 (13 lines × 2) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:158— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:158-170 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:126-138 — before extracting anything, compare `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift` and `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 180 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (12 lines × 2) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift:117— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift:117-128 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelManagement.swift:109-120 — `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift` and `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelManagement.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 68 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift:117` 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 (12 lines × 2) Core/Sources/HostApp/CustomCommandSettings/EditCustomCommandView.swift:283— Core/Sources/HostApp/CustomCommandSettings/EditCustomCommandView.swift:283-294 | Core/Sources/HostApp/CustomCommandSettings/EditCustomCommandView.swift:329-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. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/HostApp/CustomCommandSettings/EditCustomCommandView.swift:283` 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/SuggestionWidget/WidgetPositionStrategy.swift:406— Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:406-417 | Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:424-435 — 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.
Duplicated block (12 lines × 2) Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift:264— Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift:264-275 | Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:677-688 — 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 `Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift:264` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift:260` calls `hasPrefix`, `init` and `Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:676` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:37— Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:37-48 | Tool/Sources/OpenAIService/APIs/OpenAIResponsesRawService.swift:38-49 — before extracting anything, compare `Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift` and `Tool/Sources/OpenAIService/APIs/OpenAIResponsesRawService.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift:277— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift:277-285 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEdit.swift:234-242 — before extracting anything, compare `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift` and `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEdit.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/AccountSettings/ChatModelManagement/ChatModelEdit.swift:277` 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 first that the copies are not typed on the same thing: the declarations holding them bind `state` to `ChatModelEdit.State` in one and `EmbeddingModelEdit.State` 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 (9 lines × 2) Tool/Sources/LangChain/DocumentLoader/WebLoader.swift:150— Tool/Sources/LangChain/DocumentLoader/WebLoader.swift:150-158 | Tool/Sources/WebScrapper/WebScrapper.swift:143-151 — 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 (9 lines × 2) Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift:225— Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift:225-233 | Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:636-644 — 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 `Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift:225` 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 (9 lines × 2) Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:68— Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:68-76 | Tool/Sources/SharedUIComponents/AsyncDiffCodeBlock.swift:131-139 — before extracting anything, compare `Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift` and `Tool/Sources/SharedUIComponents/AsyncDiffCodeBlock.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:68` 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/SuggestionWidget/ChatWindowView.swift:154— Core/Sources/SuggestionWidget/ChatWindowView.swift:154-162 | Core/Sources/SuggestionWidget/PromptToCodePanelGroupView.swift:42-50 — 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/ChatWindowView.swift:154` 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/SuggestionWidget/WidgetWindowsController.swift:927— Core/Sources/SuggestionWidget/WidgetWindowsController.swift:927-935 | OverlayWindow/Sources/OverlayWindow/OverlayPanel.swift:143-151 — 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 (8 lines × 2) Core/Sources/ChatGPTChatTab/Styles.swift:7— Core/Sources/ChatGPTChatTab/Styles.swift:7-14 | Core/Sources/ChatGPTChatTab/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/SuggestionWidget/SuggestionPanelContent/CodeBlockSuggestionPanelView.swift:190— Core/Sources/SuggestionWidget/SuggestionPanelContent/CodeBlockSuggestionPanelView.swift:190-197 | Core/Sources/SuggestionWidget/SuggestionPanelContent/CodeBlockSuggestionPanelView.swift:202-209 — 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/CodeiumService/Services/CodeiumSuggestionService.swift:21— Tool/Sources/CodeiumService/Services/CodeiumSuggestionService.swift:21-28 | Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift:21-28 — before extracting anything, compare `Tool/Sources/CodeiumService/Services/CodeiumSuggestionService.swift` and `Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `Tool/Sources/CodeiumService/Services/CodeiumSuggestionService.swift:21` 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 first that the copies are not typed on the same thing: the declarations holding them bind `serviceLocator` to `ServiceLocator` in one and `ServiceLocatorType` 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 (8 lines × 2) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:242— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:242-249 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:236-243 — before extracting anything, compare `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift` and `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 180 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (8 lines × 2) Core/Sources/HostApp/AccountSettings/CodeiumView.swift:131— Core/Sources/HostApp/AccountSettings/CodeiumView.swift:131-138 | Core/Sources/HostApp/AccountSettings/GitHubCopilotView.swift:136-143 — 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 (11 lines × 2) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:359— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:359-369 | Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:512-522 — 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/AccountSettings/ChatModelManagement/ChatModelEditView.swift:359` 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, `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:371` calls `Text`, `Image` and `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:523` 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 (11 lines × 2) Core/Sources/HostApp/AccountSettings/CodeiumView.swift:195— Core/Sources/HostApp/AccountSettings/CodeiumView.swift:195-205 | Core/Sources/HostApp/AccountSettings/GitHubCopilotView.swift:329-339 — 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/AccountSettings/CodeiumView.swift:195` 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/HostApp/AccountSettings/GitHubCopilotView.swift:340` calls `checkStatus` and `Core/Sources/HostApp/AccountSettings/CodeiumView.swift:206` 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 (11 lines × 2) Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift:203— Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift:203-213 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotInstallationManager.swift:200-210 — before extracting anything, compare `Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift` and `Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotInstallationManager.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift:203` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) Tool/Sources/LangChain/VectorStore/TemporaryUSearch.swift:118— Tool/Sources/LangChain/VectorStore/TemporaryUSearch.swift:118-128 | Tool/Sources/LangChain/VectorStore/TemporaryUSearch.swift:136-146 — 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/LangChain/VectorStore/TemporaryUSearch.swift:118` 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) Tool/Sources/OpenAIService/APIs/OpenAIEmbeddingService.swift:26— Tool/Sources/OpenAIService/APIs/OpenAIEmbeddingService.swift:26-36 | Tool/Sources/OpenAIService/APIs/OpenAIEmbeddingService.swift:67-77 — 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 (7 lines × 2) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:189— Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:189-195 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:203-209 — 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/LanguageServer/GitHubCopilotService.swift:189` 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) Tool/Sources/SharedUIComponents/CustomTextEditor.swift:16— Tool/Sources/SharedUIComponents/CustomTextEditor.swift:16-22 | Tool/Sources/SharedUIComponents/CustomTextEditor.swift:65-71 — 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/SharedUIComponents/CustomTextEditor.swift:16` 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/CodeiumService/Services/CodeiumSuggestionService.swift:39— Tool/Sources/CodeiumService/Services/CodeiumSuggestionService.swift:39-45 | Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift:40-46 — before extracting anything, compare `Tool/Sources/CodeiumService/Services/CodeiumSuggestionService.swift` and `Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `serviceLocator` to `ServiceLocator` in one and `ServiceLocatorType` 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 (7 lines × 2) Tool/Sources/CodeiumService/CodeiumExtension.swift:145— Tool/Sources/CodeiumService/CodeiumExtension.swift:145-151 | Tool/Sources/GitHubCopilotService/GitHubCopilotExtension.swift:140-146 — 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 (7 lines × 2) Tool/Sources/OpenAIService/Configuration/ChatGPTConfiguration.swift:33— Tool/Sources/OpenAIService/Configuration/ChatGPTConfiguration.swift:33-39 | Tool/Sources/OpenAIService/Configuration/EmbeddingConfiguration.swift:29-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.
Duplicated block (5 lines × 2) Core/Sources/ChatService/AllPlugins.swift:47— Core/Sources/ChatService/AllPlugins.swift:47-51 | Core/Sources/LegacyChatPlugin/TerminalChatPlugin.swift:21-25 — 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 first that the copies are not typed on the same thing: the declarations holding them bind `delegate` to `any LegacyChatPluginDelegate` in one and `LegacyChatPluginDelegate` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 2) Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:799— Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:799-803 | Tool/Sources/OpenAIService/APIs/OpenAIResponsesRawService.swift:214-218 — before extracting anything, compare `Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift` and `Tool/Sources/OpenAIService/APIs/OpenAIResponsesRawService.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:451— Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:451-455 | Tool/Sources/SharedUIComponents/AsyncDiffCodeBlock.swift:384-388 — before extracting anything, compare `Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift` and `Tool/Sources/SharedUIComponents/AsyncDiffCodeBlock.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) Tool/Sources/WebSearchService/SearchServices/AppleDocumentationSearchService.swift:22— Tool/Sources/WebSearchService/SearchServices/AppleDocumentationSearchService.swift:22-26 | Tool/Sources/WebSearchService/SearchServices/HeadlessBrowserSearchService.swift:51-55 — 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) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:64— Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:64-68 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:92-96 — 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.
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.
No assertions: test_usearch Tool/Tests/LangChainTests/VectorStoreTests/TemporaryUSearchTests.swift:10— 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_setting_data Tool/Tests/LangChainTests/VectorStoreTests/TemporaryUSearchTests.swift:27— 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.
D12 · Dependency Hygiene· Dependency not covered by the committed resolution · ×4
Dependency not covered by the committed resolution: keyboardshortcuts — `keyboardshortcuts` is declared in Core/Package.swift but has no entry in the committed `Package.resolved` beside it, so its version is resolved rather than pinned. Resolve the package and commit the updated `Package.resolved`.
Dependency not covered by the committed resolution: cgeventoverride — `cgeventoverride` is declared in Core/Package.swift but has no entry in the committed `Package.resolved` beside it, so its version is resolved rather than pinned. Resolve the package and commit the updated `Package.resolved`.
Dependency not covered by the committed resolution: generative-ai-swift — `generative-ai-swift` is declared in Tool/Package.swift but has no entry in the committed `Package.resolved` beside it, so its version is resolved rather than pinned. Resolve the package and commit the updated `Package.resolved`.
Dependency not covered by the committed resolution: copilotforxcodekit — `copilotforxcodekit` is declared in Tool/Package.swift but has no entry in the committed `Package.resolved` beside it, so its version is resolved rather than pinned. Resolve the package and commit the updated `Package.resolved`.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (4 members, 50+ identical tokens) Tool/Sources/CodeiumService/Services/CodeiumSuggestionService.swift:59— Tool/Sources/CodeiumService/Services/CodeiumSuggestionService.swift:59-80 | Tool/Sources/CodeiumService/Services/CodeiumSuggestionService.swift:82-103 | Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift:61-82 | Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift:84-105 — 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.
Members sharing a duplicated core (4 members, 50+ identical tokens) Tool/Sources/GitHubCopilotService/GitHubCopilotExtension.swift:273— Tool/Sources/GitHubCopilotService/GitHubCopilotExtension.swift:273-330 | Tool/Sources/OpenAIService/APIs/GitHubCopilotChatCompletionsService.swift:69-110 | Tool/Sources/OpenAIService/APIs/GitHubCopilotEmbeddingService.swift:34-70 | Tool/Sources/OpenAIService/APIs/OpenAIResponsesRawService.swift:166-212 — 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.
Members sharing a duplicated core (4 members, 50+ identical tokens) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:232— Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:232-238 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:248-254 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:300-304 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:314-320 — 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.
Members sharing a duplicated core (4 members, 50+ identical tokens) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:400— Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:400-404 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:425-429 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:444-448 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:461-465 — 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.
Duplicated block (15 lines × 2) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:11— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:11-25 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:10-24 — before extracting anything, compare `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift` and `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 180 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/AccountSettings/ChatModelManagement/ChatModelEditView.swift:11` 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/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:27` calls `GoogleAIForm` and `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:26` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift:151— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift:151-165 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelManagement.swift:143-157 — `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift` and `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelManagement.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 68 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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 (15 lines × 2) Core/Sources/HostApp/FeatureSettings/Suggestion/SuggestionFeatureDisabledLanguageListView.swift:58— Core/Sources/HostApp/FeatureSettings/Suggestion/SuggestionFeatureDisabledLanguageListView.swift:58-72 | Core/Sources/HostApp/FeatureSettings/Suggestion/SuggestionFeatureEnabledProjectListView.swift:65-79 — before extracting anything, compare `Core/Sources/HostApp/FeatureSettings/Suggestion/SuggestionFeatureDisabledLanguageListView.swift` and `Core/Sources/HostApp/FeatureSettings/Suggestion/SuggestionFeatureEnabledProjectListView.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — 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/FeatureSettings/Suggestion/SuggestionFeatureDisabledLanguageListView.swift:58` 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 (15 lines × 2) Core/Sources/SuggestionWidget/WidgetView.swift:284— Core/Sources/SuggestionWidget/WidgetView.swift:284-298 | Core/Sources/SuggestionWidget/WidgetView.swift:314-328 — 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:284` 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) Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:102— Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:102-107 | Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:130-135 — 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/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift:89— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift:89-94 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEdit.swift:74-79 — before extracting anything, compare `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift` and `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEdit.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (6 lines × 2) Tool/Sources/AIModel/ChatModel.swift:12— Tool/Sources/AIModel/ChatModel.swift:12-17 | Tool/Sources/AIModel/EmbeddingModel.swift:12-17 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) Tool/Sources/CodeiumService/CodeiumExtension.swift:161— Tool/Sources/CodeiumService/CodeiumExtension.swift:161-166 | Tool/Sources/GitHubCopilotService/GitHubCopilotExtension.swift:160-165 — 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.
FileTooLong: SuggestionPanelContent/PromptToCodePanelView.swift Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift— FileTooLong — 907 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 407 over it, 1.81× 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: APIs/OpenAIChatCompletionsService.swift Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift— FileTooLong — 901 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 401 over it, 1.80× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: SuggestionCommandHandler/PseudoCommandHandler.swift Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift— FileTooLong — 566 significant lines (blank, comment-only and punctuation-only lines excluded), about 76% of them inside a single declaration: PseudoCommandHandler (30-588). The bar is 500 significant lines; this is 66 over it, 1.13× 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.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×3
Edited copy of a member (35 corresponding lines) Core/Sources/SuggestionWidget/ChatWindowView.swift:314— Core/Sources/SuggestionWidget/ChatWindowView.swift:314-348 | Core/Sources/SuggestionWidget/PromptToCodePanelGroupView.swift:100-139 — 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.
Edited copy of a member (35 corresponding lines) Core/Sources/PromptToCodeService/OpenAIPromptToCodeService.swift:9— Core/Sources/PromptToCodeService/OpenAIPromptToCodeService.swift:9-43 | Core/Sources/PromptToCodeService/PreviewPromptToCodeService.swift:6-40 — 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.
Edited copy of a member (35 corresponding lines) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:107— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:107-149 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:83-117 — 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 (17 corresponding lines) · ×3
Edited copy of a member (17 corresponding lines) Tool/Sources/LangChain/VectorStore/TemporaryUSearch.swift:112— Tool/Sources/LangChain/VectorStore/TemporaryUSearch.swift:112-128 | Tool/Sources/LangChain/VectorStore/TemporaryUSearch.swift:130-146 — 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) Tool/Sources/CodeiumService/Services/CodeiumSuggestionService.swift:21— Tool/Sources/CodeiumService/Services/CodeiumSuggestionService.swift:21-37 | Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift:21-38 — 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) Tool/Sources/FocusedCodeFinder/ActiveDocumentContext.swift:37— Tool/Sources/FocusedCodeFinder/ActiveDocumentContext.swift:37-53 | Tool/Sources/FocusedCodeFinder/FocusedCodeFinder.swift:44-60 — 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 (15 corresponding lines) · ×3
Edited copy of a member (15 corresponding lines) Tool/Sources/XcodeInspector/SourceEditor.swift:36— Tool/Sources/XcodeInspector/SourceEditor.swift:36-50 | Tool/Sources/XcodeInspector/SourceEditor.swift:56-74 — 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/SharedUIComponents/TabContainer.swift:49— Tool/Sources/SharedUIComponents/TabContainer.swift:49-63 | Tool/Sources/SharedUIComponents/TabContainer.swift:65-80 — 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) Core/Sources/HostApp/FeatureSettings/Chat/ChatSettingsGeneralSectionView.swift:45— Core/Sources/HostApp/FeatureSettings/Chat/ChatSettingsGeneralSectionView.swift:45-59 | Core/Sources/HostApp/FeatureSettings/Suggestion/SuggestionSettingsGeneralSectionView.swift:66-80 — 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 (9 corresponding lines) · ×3
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/ChatGPTChatTab/ChatContextMenu.swift:44— Core/Sources/ChatGPTChatTab/ChatContextMenu.swift:44-52 | Core/Sources/ChatGPTChatTab/ChatContextMenu.swift:55-63 — 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/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift:8— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift:8-18 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelManagement.swift:8-16 — 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.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×3
Edited copy of a member (8 corresponding lines) Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift:327— Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift:327-334 | Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:805-819 — 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:417— Tool/Sources/AXExtension/AXUIElement.swift:417-424 | Tool/Sources/AXExtension/AXUIElement.swift:426-442 — 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/LangChain/Chain.swift:71— Tool/Sources/LangChain/Chain.swift:71-78 | Tool/Sources/LangChain/Chain.swift:92-99 — 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.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×3
Edited copy of a member (12 corresponding lines) Core/Sources/ChatGPTChatTab/Chat.swift:488— Core/Sources/ChatGPTChatTab/Chat.swift:488-499 | 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/LangChain/DocumentTransformer/RecursiveCharacterTextSplitter.swift:21— Tool/Sources/LangChain/DocumentTransformer/RecursiveCharacterTextSplitter.swift:21-32 | Tool/Sources/LangChain/DocumentTransformer/RecursiveCharacterTextSplitter.swift:41-52 — 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/HostApp/AccountSettings/ChatModelManagement/ChatModelManagementView.swift:8— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagementView.swift:8-19 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelManagementView.swift:8-19 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×3
Edited copy of a member (10 corresponding lines) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:114— Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:114-127 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:129-138 — 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/GitHubCopilotService.swift:385— Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:385-394 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:396-408 — 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/LangChain/DocumentLoader/WebLoader.swift:139— Tool/Sources/LangChain/DocumentLoader/WebLoader.swift:139-148 | Tool/Sources/WebScrapper/WebScrapper.swift:18-27 — 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 (4 corresponding lines) · ×3
Edited copy of a member (4 corresponding lines) Tool/Sources/OpenAIService/Configuration/EmbeddingConfiguration.swift:18— Tool/Sources/OpenAIService/Configuration/EmbeddingConfiguration.swift:18-21 | Tool/Sources/RAGChatAgent/RAGChatAgentConfiguration.swift:113-116 — 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/CodeiumService/Services/CodeiumSuggestionService.swift:54— Tool/Sources/CodeiumService/Services/CodeiumSuggestionService.swift:54-57 | Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift:56-59 — 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) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift:145— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift:145-148 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelManagement.swift:137-140 — 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 (28 lines × 2) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift:98— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift:98-125 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEdit.swift:83-110 — before extracting anything, compare `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift` and `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEdit.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/AccountSettings/ChatModelManagement/ChatModelEdit.swift:98` 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 (28 lines × 2) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift:245— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift:245-272 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEdit.swift:202-229 — before extracting anything, compare `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift` and `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEdit.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/AccountSettings/ChatModelManagement/ChatModelEdit.swift:245` 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 (28 lines × 2) Core/Sources/HostApp/CustomCommandSettings/CustomCommandView.swift:269— Core/Sources/HostApp/CustomCommandSettings/CustomCommandView.swift:269-296 | Core/Sources/HostApp/CustomCommandSettings/CustomCommandView.swift:319-346 — 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/CustomCommandSettings/CustomCommandView.swift:269` 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 (16 lines × 2) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:359— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:359-374 | Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:597-612 — 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/AccountSettings/ChatModelManagement/ChatModelEditView.swift:359` 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, `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:613` calls `dynamicHeightTextInFormWorkaround` and `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:375` 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 (16 lines × 2) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:90— Core/Sources/SuggestionWidget/WidgetWindowsController.swift:90-105 | OverlayWindow/Sources/OverlayWindow/OverlayWindowController.swift:60-75 — 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 (16 lines × 2) Tool/Sources/ModificationBasic/ExplanationThenCodeStreamParser.swift:160— Tool/Sources/ModificationBasic/ExplanationThenCodeStreamParser.swift:160-175 | Tool/Sources/ModificationBasic/ExplanationThenCodeStreamParser.swift:204-219 — 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/ModificationBasic/ExplanationThenCodeStreamParser.swift:160` 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, `Tool/Sources/ModificationBasic/ExplanationThenCodeStreamParser.swift:156` calls `flushBuffer`, `appendBuffer` and `Tool/Sources/ModificationBasic/ExplanationThenCodeStreamParser.swift:203` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 2) Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:55— Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:55-68 | Tool/Sources/OpenAIService/APIs/OpenAIResponsesRawService.swift:56-69 — before extracting anything, compare `Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift` and `Tool/Sources/OpenAIService/APIs/OpenAIResponsesRawService.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:391— Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:391-404 | Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:443-456 — 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/OpenAIService/APIs/OpenAIChatCompletionsService.swift:391` 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 (14 lines × 2) Tool/Sources/Terminal/Terminal.swift:61— Tool/Sources/Terminal/Terminal.swift:61-74 | Tool/Sources/Terminal/Terminal.swift:190-203 — 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 lines × 3) Tool/Sources/OpenAIService/APIs/ChatCompletionsAPIDefinition.swift:178— Tool/Sources/OpenAIService/APIs/ChatCompletionsAPIDefinition.swift:178-188 | Tool/Sources/OpenAIService/APIs/EmbeddingAPIDefinitions.swift:16-26 | Tool/Sources/OpenAIService/APIs/OpenAIResponsesRawService.swift:223-233 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/OpenAIService/APIs/ChatCompletionsAPIDefinition.swift:178` 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 × 3) Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift:242— Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift:242-252 | Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:653-663 | Tool/Sources/OpenAIService/APIs/OpenAIResponsesRawService.swift:113-123 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift:242` 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, `Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:665` calls `unauthorized` and `Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift:253` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 3) Tool/Sources/SharedUIComponents/AsyncDiffCodeBlock.swift:395— Tool/Sources/SharedUIComponents/AsyncDiffCodeBlock.swift:395-405 | Tool/Sources/SharedUIComponents/AsyncDiffCodeBlock.swift:409-419 | Tool/Sources/SharedUIComponents/AsyncDiffCodeBlock.swift:423-433 — 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 `Tool/Sources/SharedUIComponents/AsyncDiffCodeBlock.swift:395` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×2
Edited copy of a member (40 corresponding lines) Tool/Sources/OpenAIService/APIs/OpenAIEmbeddingService.swift:25— Tool/Sources/OpenAIService/APIs/OpenAIEmbeddingService.swift:25-64 | Tool/Sources/OpenAIService/APIs/OpenAIEmbeddingService.swift:66-105 — 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.
Edited copy of a member (40 corresponding lines) Tool/Sources/SharedUIComponents/SyntaxHighlighting.swift:31— Tool/Sources/SharedUIComponents/SyntaxHighlighting.swift:31-70 | Tool/Sources/SharedUIComponents/SyntaxHighlighting.swift:72-118 — 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 (37 corresponding lines) · ×2
Edited copy of a member (37 corresponding lines) Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:360— Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:360-404 | Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:420-456 — These two members are one piece of code written twice and then edited apart: 37 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 (37 corresponding lines) Core/Sources/HostApp/CustomCommandSettings/CustomCommandView.swift:269— Core/Sources/HostApp/CustomCommandSettings/CustomCommandView.swift:269-315 | Core/Sources/HostApp/CustomCommandSettings/CustomCommandView.swift:319-355 — These two members are one piece of code written twice and then edited apart: 37 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 (29 corresponding lines) · ×2
Edited copy of a member (29 corresponding lines) Tool/Sources/SharedUIComponents/AsyncDiffCodeBlock.swift:126— Tool/Sources/SharedUIComponents/AsyncDiffCodeBlock.swift:126-154 | Tool/Sources/SharedUIComponents/CodeBlock.swift:59-90 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) Tool/Sources/CodeiumService/CodeiumExtension.swift:106— Tool/Sources/CodeiumService/CodeiumExtension.swift:106-134 | Tool/Sources/GitHubCopilotService/GitHubCopilotExtension.swift:96-131 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×2
Edited copy of a member (21 corresponding lines) Tool/Sources/OpenAIService/APIs/ChatCompletionsAPIDefinition.swift:107— Tool/Sources/OpenAIService/APIs/ChatCompletionsAPIDefinition.swift:107-130 | Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:564-584 — 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) ChatPlugins/Sources/ShortcutChatPlugin/ShortcutChatPlugin.swift:23— ChatPlugins/Sources/ShortcutChatPlugin/ShortcutChatPlugin.swift:23-48 | Tool/Sources/ChatBasic/ChatPlugin.swift:38-58 — 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 copies of one member (3 members, 14+ corresponding lines) · ×2
Edited copies of one member (3 members, 14+ corresponding lines) Tool/Sources/OpenAIService/APIs/ChatCompletionsAPIDefinition.swift:175— Tool/Sources/OpenAIService/APIs/ChatCompletionsAPIDefinition.swift:175-188 | Tool/Sources/OpenAIService/APIs/EmbeddingAPIDefinitions.swift:13-26 | Tool/Sources/OpenAIService/APIs/OpenAIResponsesRawService.swift:220-233 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 14+ corresponding lines) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:34— Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:34-47 | Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:49-62 | Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:150-163 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×2
Edited copy of a member (11 corresponding lines) Tool/Sources/WorkspaceSuggestionService/SuggestionWorkspacePlugin.swift:36— Tool/Sources/WorkspaceSuggestionService/SuggestionWorkspacePlugin.swift:36-53 | Tool/Sources/WorkspaceSuggestionService/SuggestionWorkspacePlugin.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) Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift:213— Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift:213-223 | Tool/Sources/OpenAIService/APIs/OlamaChatCompletionsService.swift:16-26 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (43 lines × 2) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:195— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:195-237 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:144-186 — before extracting anything, compare `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift` and `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 180 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (43 lines × 2) Tool/Sources/OpenAIService/APIs/ChatCompletionsAPIBuilder.swift:29— Tool/Sources/OpenAIService/APIs/ChatCompletionsAPIBuilder.swift:29-71 | Tool/Sources/OpenAIService/APIs/ChatCompletionsAPIBuilder.swift:79-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. 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 (34 lines × 2) Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1158— Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1158-1191 | Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1213-1246 — 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/SuggestionPanelContent/PromptToCodePanelView.swift:1158` 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 (34 lines × 2) Tool/Sources/OpenAIService/EmbeddingService.swift:13— Tool/Sources/OpenAIService/EmbeddingService.swift:13-46 | Tool/Sources/OpenAIService/EmbeddingService.swift:85-118 — 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 (29 lines × 2) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:404— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:404-432 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:311-339 — before extracting anything, compare `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift` and `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 180 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/AccountSettings/ChatModelManagement/ChatModelEditView.swift:404` 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 (29 lines × 2) Core/Sources/SuggestionWidget/ChatWindowView.swift:320— Core/Sources/SuggestionWidget/ChatWindowView.swift:320-348 | Core/Sources/SuggestionWidget/PromptToCodePanelGroupView.swift:111-139 — 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/ChatWindowView.swift:320` 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 (27 lines × 2) Tool/Sources/OpenAIService/APIs/OpenAIEmbeddingService.swift:38— Tool/Sources/OpenAIService/APIs/OpenAIEmbeddingService.swift:38-64 | Tool/Sources/OpenAIService/APIs/OpenAIEmbeddingService.swift:79-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 `Tool/Sources/OpenAIService/APIs/OpenAIEmbeddingService.swift:38` 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 (27 lines × 2) Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:97— Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:97-123 | Tool/Sources/SharedUIComponents/AsyncDiffCodeBlock.swift:70-96 — before extracting anything, compare `Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift` and `Tool/Sources/SharedUIComponents/AsyncDiffCodeBlock.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:97` 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 (25 lines × 2) Tool/Sources/OpenAIService/APIs/GitHubCopilotChatCompletionsService.swift:81— Tool/Sources/OpenAIService/APIs/GitHubCopilotChatCompletionsService.swift:81-105 | Tool/Sources/OpenAIService/APIs/GitHubCopilotEmbeddingService.swift:41-65 — 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 `Tool/Sources/OpenAIService/APIs/GitHubCopilotChatCompletionsService.swift:81` 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 (25 lines × 2) Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:649— Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:649-673 | Tool/Sources/OpenAIService/APIs/OpenAIResponsesRawService.swift:109-133 — before extracting anything, compare `Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift` and `Tool/Sources/OpenAIService/APIs/OpenAIResponsesRawService.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:32— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:32-51 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:27-46 — before extracting anything, compare `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift` and `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 180 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/AccountSettings/ChatModelManagement/ChatModelEditView.swift:32` 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 before the matched lines, `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:31` calls `ClaudeForm` and `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:26` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (20 lines × 2) Tool/Sources/CodeDiff/CodeDiff.swift:577— Tool/Sources/CodeDiff/CodeDiff.swift:577-596 | Tool/Sources/SharedUIComponents/AsyncDiffCodeBlock.swift:469-488 — 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 `Tool/Sources/CodeDiff/CodeDiff.swift:577` 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 × 3) Tool/Sources/OpenAIService/APIs/OllamaEmbeddingService.swift:38— Tool/Sources/OpenAIService/APIs/OllamaEmbeddingService.swift:38-50 | Tool/Sources/OpenAIService/APIs/OpenAIEmbeddingService.swift:48-60 | Tool/Sources/OpenAIService/APIs/OpenAIEmbeddingService.swift:89-101 — 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 (13 lines × 3) Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:462— Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:462-474 | Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:477-489 | Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:492-504 — 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 `Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:462` 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 (11–12 lines × 2) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:604— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:604-615 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:421-431 — before extracting anything, compare `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift` and `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 180 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/AccountSettings/ChatModelManagement/ChatModelEditView.swift:604` 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. 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, `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:431` calls `padding`, `sheet`, `CustomHeaderSettingsView` and `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:615` 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 (11–12 lines × 2) Tool/Sources/ChatContextCollectors/ActiveDocumentChatContextCollector/ActiveDocumentChatContextCollector.swift:90— Tool/Sources/ChatContextCollectors/ActiveDocumentChatContextCollector/ActiveDocumentChatContextCollector.swift:90-100 | Tool/Sources/FocusedCodeFinder/ActiveDocumentContext.swift:85-96 — 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 `Tool/Sources/ChatContextCollectors/ActiveDocumentChatContextCollector/ActiveDocumentChatContextCollector.swift:90` 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 (10–11 lines × 3) Tool/Sources/AppActivator/AppActivator.swift:98— Tool/Sources/AppActivator/AppActivator.swift:98-108 | Tool/Sources/CodeiumService/Services/CodeiumService.swift:445-454 | Tool/Sources/XcodeInspector/XcodeInspector+TriggerCommand.swift:149-159 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/AppActivator/AppActivator.swift:98` 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 (10–11 lines × 3) Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:778— Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:778-788 | Tool/Sources/OpenAIService/APIs/OpenAIEmbeddingService.swift:134-143 | Tool/Sources/OpenAIService/APIs/OpenAIResponsesRawService.swift:180-190 — before extracting anything, compare `Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift` and `Tool/Sources/OpenAIService/APIs/OpenAIResponsesRawService.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:778` 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 (10 lines × 2) Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:115— Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:115-124 | Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:183-192 — 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/OpenAIService/APIs/OpenAIChatCompletionsService.swift:115` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 2) Core/Sources/HostApp/FeatureSettings/Suggestion/SuggestionFeatureDisabledLanguageListView.swift:91— Core/Sources/HostApp/FeatureSettings/Suggestion/SuggestionFeatureDisabledLanguageListView.swift:91-100 | Core/Sources/HostApp/FeatureSettings/Suggestion/SuggestionFeatureEnabledProjectListView.swift:129-138 — before extracting anything, compare `Core/Sources/HostApp/FeatureSettings/Suggestion/SuggestionFeatureDisabledLanguageListView.swift` and `Core/Sources/HostApp/FeatureSettings/Suggestion/SuggestionFeatureEnabledProjectListView.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Swallowed exception (empty catch) Tool/Sources/SharedUIComponents/SyntaxHighlighting.swift:303— 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/ChatService/ChatService.swift:112— 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.
RequestBody.init (cyclomatic 54) Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:1049— RequestBody.init has cyclomatic complexity 54 (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 (cyclomatic 50) Core/Sources/ChatGPTChatTab/Chat.swift:128— Chat.body has cyclomatic complexity 50 (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.
ChatPanel.body (cyclomatic 47) Core/Sources/SuggestionWidget/FeatureReducers/ChatPanel.swift:96— ChatPanel.body has cyclomatic complexity 47 (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.
Widget.body (cyclomatic 38) Core/Sources/SuggestionWidget/FeatureReducers/Widget.swift:129— Widget.body has cyclomatic complexity 38 (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.
ChatModelEdit.body (cyclomatic 37) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift:98— ChatModelEdit.body has cyclomatic complexity 37 (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.
ExplanationThenCodeStreamParser.yield (cyclomatic 37) Tool/Sources/ModificationBasic/ExplanationThenCodeStreamParser.swift:81— ExplanationThenCodeStreamParser.yield has cyclomatic complexity 37 (threshold 15). Of this number, 35 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PromptToCodeGroup.body (cyclomatic 33) Core/Sources/SuggestionWidget/FeatureReducers/PromptToCodeGroup.swift:51— PromptToCodeGroup.body has cyclomatic complexity 33 (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.
General.body (cyclomatic 31) Core/Sources/HostApp/General.swift:56— General.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.
PromptToCodePanel.body (cyclomatic 31) Core/Sources/SuggestionWidget/FeatureReducers/PromptToCodePanel.swift:110— PromptToCodePanel.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.
EmbeddingModelEdit.body (cyclomatic 30) Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEdit.swift:83— EmbeddingModelEdit.body has cyclomatic complexity 30 (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 30) Core/Sources/Service/GUI/GraphicalUserInterfaceController.swift:82— GUI.body has cyclomatic complexity 30 (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.
GitHubCopilotView.body (cyclomatic 25) Core/Sources/HostApp/AccountSettings/GitHubCopilotView.swift:145— GitHubCopilotView.body has cyclomatic complexity 25 (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.
RequestBody.init (cyclomatic 25) Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift:403— RequestBody.init has cyclomatic complexity 25 (threshold 15). Of this number, 13 points are the body's own statements and 12 belong to 4 function items inside it that branch. 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.generateWidgetLocation (cyclomatic 23) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:277— WidgetWindowsController.generateWidgetLocation has cyclomatic complexity 23 (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.
XcodeInspector.restart (cyclomatic 23) Tool/Sources/XcodeInspector/XcodeInspector.swift:231— 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.
ChatGPTService.send (cyclomatic 22) Tool/Sources/OpenAIService/ChatGPTService.swift:138— ChatGPTService.send 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.
TabToAcceptSuggestion.handleTab (cyclomatic 21) Core/Sources/KeyBindingManager/TabToAcceptSuggestion.swift:116— TabToAcceptSuggestion.handleTab has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DependencyUpdater.update (cyclomatic 21) Core/Sources/Service/DependencyUpdater.swift:9— DependencyUpdater.update has cyclomatic complexity 21 (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.
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.
CodeiumChatBrowser.body (cyclomatic 21) Tool/Sources/CodeiumService/ChatTab/CodeiumChatBrowser.swift:47— CodeiumChatBrowser.body has cyclomatic complexity 21 (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.
CustomCommandFeature.body (cyclomatic 20) Core/Sources/HostApp/CustomCommandSettings/CustomCommand.swift:29— CustomCommandFeature.body 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.
SimpleModificationAgent.modifyCode (cyclomatic 20) Core/Sources/PromptToCodeService/OpenAIPromptToCodeService.swift:47— SimpleModificationAgent.modifyCode has cyclomatic complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RealtimeSuggestionController.handleFocusElementChange (cyclomatic 20) Core/Sources/Service/RealtimeSuggestionController.swift:45— RealtimeSuggestionController.handleFocusElementChange 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.
CodeDiff.diff (cyclomatic 20) Tool/Sources/CodeDiff/CodeDiff.swift:137— CodeDiff.diff 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.
MemoryTemplate.defaultTruncateRule (cyclomatic 20) Tool/Sources/OpenAIService/Memory/TemplateChatGPTMemory.swift:203— MemoryTemplate.defaultTruncateRule 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.
LegacyChatPluginWrapper.send (cyclomatic 19) Core/Sources/ChatService/AllPlugins.swift:46— LegacyChatPluginWrapper.send 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.
WidgetWindowsController.updateWindowOpacity (cyclomatic 19) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:387— WidgetWindowsController.updateWindowOpacity 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.
WidgetPanel.body (cyclomatic 19) Core/Sources/SuggestionWidget/FeatureReducers/WidgetPanel.swift:45— WidgetPanel.body 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.
GitHubCopilotChatService.sendMessage (cyclomatic 19) Tool/Sources/GitHubCopilotService/Services/GitHubCopilotChatService.swift:17— GitHubCopilotChatService.sendMessage 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.openChat (cyclomatic 18) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:417— PseudoCommandHandler.openChat has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ServerNotificationHandler.handleNotification (cyclomatic 18) Tool/Sources/GitHubCopilotService/LanguageServer/CopilotLocalProcessServer.swift:309— ServerNotificationHandler.handleNotification 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.
CodeHighlighting.convertToCodeLines (cyclomatic 18) Tool/Sources/SharedUIComponents/SyntaxHighlighting.swift:223— CodeHighlighting.convertToCodeLines has cyclomatic complexity 18 (threshold 15). Of this number, 15 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.
ChatModelManagement.body (cyclomatic 17) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift:67— ChatModelManagement.body has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EmbeddingModelManagement.body (cyclomatic 17) Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelManagement.swift:59— EmbeddingModelManagement.body has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
XcodeThemeController.syncXcodeThemeIfNeeded (cyclomatic 17) Core/Sources/XcodeThemeController/XcodeThemeController.swift:77— XcodeThemeController.syncXcodeThemeIfNeeded has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AXNotificationStream.init (cyclomatic 17) Tool/Sources/AXNotificationStream/AXNotificationStream.swift:46— AXNotificationStream.init has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, 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.
ObjectiveCScopeHierarchySyntaxVisitor.visit (cyclomatic 17) Tool/Sources/FocusedCodeFinder/ObjectiveC/ObjectiveCScopeHierarchySyntaxVisitor.swift:39— ObjectiveCScopeHierarchySyntaxVisitor.visit has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GitHubCopilotBaseService.init (cyclomatic 17) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:129— GitHubCopilotBaseService.init has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: GitHubCopilotError.errorDescription (cyclomatic 20) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
OpenAIEmbedding.getLenSafeEmbeddings (cyclomatic 17) Tool/Sources/LangChain/Embedding/OpenAIEmbedding.swift:58— OpenAIEmbedding.getLenSafeEmbeddings has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EditCustomCommand.body (cyclomatic 16) Core/Sources/HostApp/CustomCommandSettings/EditCustomCommand.swift:98— EditCustomCommand.body has cyclomatic complexity 16 (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.
XcodeAppInstanceInspector.observeAXNotifications (cyclomatic 16) Tool/Sources/XcodeInspector/Apps/XcodeAppInstanceInspector.swift:256— XcodeAppInstanceInspector.observeAXNotifications 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.
HackComment Core/Sources/HostApp/SharedComponents/EditableText.swift:4— // Hack to disable smart quotes and dashes in TextEditor — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
RequestBody.init (cognitive 145) Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:1049— RequestBody.init has cognitive complexity 145 (threshold 15). Drivers by points: ternaries 16 (78 pts), if/else 23 (49 pts), boolean chains 6, loops 3 (6 pts), match/switch 3 (6 pts) (nesting depth added 94). 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.
ExplanationThenCodeStreamParser.yield (cognitive 100) Tool/Sources/ModificationBasic/ExplanationThenCodeStreamParser.swift:81— ExplanationThenCodeStreamParser.yield has cognitive complexity 100 (threshold 15). Drivers by points: if/else 24 (79 pts), match/switch 4 (11 pts), boolean chains 9, loops 1 (nesting depth added 62). Of this number, 94 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChatGPTService.send (cognitive 75) Tool/Sources/OpenAIService/ChatGPTService.swift:138— ChatGPTService.send has cognitive complexity 75 (threshold 15). Drivers by points: if/else 8 (34 pts), loops 6 (28 pts), match/switch 2 (11 pts), boolean chains 1, error handling 1 (nesting depth added 57). 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.body (cognitive 53) Core/Sources/SuggestionWidget/FeatureReducers/ChatPanel.swift:96— ChatPanel.body has cognitive complexity 53 (threshold 15). Drivers by points: if/else 23 (46 pts), boolean chains 6, match/switch 1 (nesting depth added 23). 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.
CodeDiff.diff (cognitive 50) Tool/Sources/CodeDiff/CodeDiff.swift:137— CodeDiff.diff has cognitive complexity 50 (threshold 15). Drivers by points: if/else 14 (40 pts), loops 4 (9 pts), boolean chains 1 (nesting depth added 31). 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.
ChatGPTMemory.streamMessage (cognitive 49) Tool/Sources/OpenAIService/Memory/ChatGPTMemory.swift:83— ChatGPTMemory.streamMessage has cognitive complexity 49 (threshold 15). Drivers by points: if/else 17 (45 pts), loops 1 (4 pts) (nesting depth added 31). 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.
PromptToCodePanel.body (cognitive 42) Core/Sources/SuggestionWidget/FeatureReducers/PromptToCodePanel.swift:110— PromptToCodePanel.body has cognitive complexity 42 (threshold 15). Drivers by points: if/else 5 (15 pts), error handling 4 (12 pts), loops 2 (8 pts), match/switch 2 (5 pts), boolean chains 2 (nesting depth added 27). 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.
XcodeInspector.restart (cognitive 42) Tool/Sources/XcodeInspector/XcodeInspector.swift:231— 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.
Widget.body (cognitive 41) Core/Sources/SuggestionWidget/FeatureReducers/Widget.swift:129— Widget.body has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (25 pts), match/switch 5 (7 pts), loops 3 (6 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 17). 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.
Chat.body (cognitive 40) Core/Sources/ChatGPTChatTab/Chat.swift:128— Chat.body has cognitive complexity 40 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 6 (12 pts), boolean chains 3, error handling 1 (3 pts), match/switch 2 (3 pts) (nesting depth added 18). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CodeHighlighting.convertToCodeLines (cognitive 39) Tool/Sources/SharedUIComponents/SyntaxHighlighting.swift:223— CodeHighlighting.convertToCodeLines has cognitive complexity 39 (threshold 15). Drivers by points: if/else 11 (24 pts), loops 5 (11 pts), error handling 1 (4 pts) (nesting depth added 22). Of this number, 36 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.
WidgetWindowsController.generateWidgetLocation (cognitive 37) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:277— WidgetWindowsController.generateWidgetLocation has cognitive complexity 37 (threshold 15). Drivers by points: boolean chains 13, if/else 7 (13 pts), match/switch 3 (11 pts) (nesting depth added 14). 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 36) Core/Sources/Service/RealtimeSuggestionController.swift:45— RealtimeSuggestionController.handleFocusElementChange has cognitive complexity 36 (threshold 15). Drivers by points: if/else 16 (26 pts), loops 4 (8 pts), error handling 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SimpleModificationAgent.modifyCode (cognitive 35) Core/Sources/PromptToCodeService/OpenAIPromptToCodeService.swift:47— SimpleModificationAgent.modifyCode has cognitive complexity 35 (threshold 15). Drivers by points: if/else 15 (21 pts), match/switch 4 (6 pts), loops 2 (4 pts), ternaries 3, error handling 1 (nesting depth added 10). Of this number, 29 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PromptToCodeGroup.body (cognitive 35) Core/Sources/SuggestionWidget/FeatureReducers/PromptToCodeGroup.swift:51— PromptToCodeGroup.body has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 6, loops 3 (6 pts), match/switch 2 (nesting depth added 13). 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.
XcodeAppInstanceInspector.observeAXNotifications (cognitive 34) Tool/Sources/XcodeInspector/Apps/XcodeAppInstanceInspector.swift:256— XcodeAppInstanceInspector.observeAXNotifications has cognitive complexity 34 (threshold 15). Drivers by points: if/else 11 (28 pts), match/switch 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GitHubCopilotChatService.sendMessage (cognitive 33) Tool/Sources/GitHubCopilotService/Services/GitHubCopilotChatService.swift:17— GitHubCopilotChatService.sendMessage has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (24 pts), error handling 4 (6 pts), boolean chains 2, match/switch 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.
GUI.body (cognitive 32) Core/Sources/Service/GUI/GraphicalUserInterfaceController.swift:82— GUI.body has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (23 pts), boolean chains 5, loops 1 (2 pts), match/switch 2 (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.
AppDelegate.menuWillOpen (cognitive 32) ExtensionService/AppDelegate+Menu.swift:128— AppDelegate.menuWillOpen has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 3 (9 pts), ternaries 3 (8 pts), match/switch 1 (nesting depth added 16). 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 31) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:387— WidgetWindowsController.updateWindowOpacity has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (16 pts), ternaries 5 (10 pts), boolean chains 5 (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.
General.body (cognitive 30) Core/Sources/HostApp/General.swift:56— General.body has cognitive complexity 30 (threshold 15). Drivers by points: error handling 8 (17 pts), if/else 5 (10 pts), match/switch 2 (3 pts) (nesting depth added 15). 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.
OpenAIEmbedding.getLenSafeEmbeddings (cognitive 30) Tool/Sources/LangChain/Embedding/OpenAIEmbedding.swift:58— OpenAIEmbedding.getLenSafeEmbeddings has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 6 (8 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 14). 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.
LegacyChatPluginWrapper.send (cognitive 29) Core/Sources/ChatService/AllPlugins.swift:46— LegacyChatPluginWrapper.send has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (15 pts), match/switch 3 (11 pts), loops 1 (2 pts), error handling 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppInstanceInspector.triggerMenuItem (cognitive 29) Tool/Sources/XcodeInspector/XcodeInspector+TriggerCommand.swift:23— AppInstanceInspector.triggerMenuItem has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (24 pts), error handling 1 (2 pts), loops 1 (2 pts), boolean chains 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.
ChatModelEdit.body (cognitive 28) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift:98— ChatModelEdit.body has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (21 pts), match/switch 3 (5 pts), error handling 1 (2 pts) (nesting depth added 13). 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.
RequestBody.init (cognitive 28) Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift:403— RequestBody.init has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (12 pts), match/switch 4 (9 pts), boolean chains 4, loops 2, ternaries 1 (nesting depth added 7). Of this number, 17 points are the body's own statements and 11 belong to 4 function items inside it that branch. 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.
SuggestionInjector.acceptSuggestions (cognitive 28) Tool/Sources/SuggestionInjector/SuggestionInjector.swift:90— SuggestionInjector.acceptSuggestions has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 2 (3 pts), match/switch 1 (3 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.
TabToAcceptSuggestion.handleTab (cognitive 27) Core/Sources/KeyBindingManager/TabToAcceptSuggestion.swift:116— TabToAcceptSuggestion.handleTab has cognitive complexity 27 (threshold 15). Drivers by points: if/else 21 (24 pts), boolean chains 2, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
PseudoCommandHandler.openChat (cognitive 27) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:417— PseudoCommandHandler.openChat has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 4, loops 1 (2 pts), match/switch 1 (nesting depth added 12). Of this number, 23 points are the body's own statements and 4 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.
HorizontalMovable.framesForWindows (cognitive 27) Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:104— HorizontalMovable.framesForWindows has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 5 (13 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.
MemoryTemplate.defaultTruncateRule (cognitive 27) Tool/Sources/OpenAIService/Memory/TemplateChatGPTMemory.swift:203— MemoryTemplate.defaultTruncateRule has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (22 pts), boolean chains 2, loops 2, 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.
CustomCommandFeature.body (cognitive 25) Core/Sources/HostApp/CustomCommandSettings/CustomCommand.swift:29— CustomCommandFeature.body has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (15 pts), error handling 2 (4 pts), match/switch 2 (4 pts), boolean chains 2 (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.
PseudoCommandHandler.acceptModification (cognitive 24) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:208— PseudoCommandHandler.acceptModification has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (15 pts), error handling 4 (8 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.
OverlayWindowController.handleOverlayStatusChange (cognitive 24) OverlayWindow/Sources/OverlayWindow/OverlayWindowController.swift:156— OverlayWindowController.handleOverlayStatusChange has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 5 (10 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.
TextSplitter.mergeSplits (cognitive 24) Tool/Sources/LangChain/DocumentTransformer/TextSplitter.swift:112— TextSplitter.mergeSplits has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 3 (5 pts), boolean chains 1, ternaries 1 (nesting depth added 11). Of this number, 22 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WidgetWindowsController.adjustChatPanelWindowLevel (cognitive 23) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:543— WidgetWindowsController.adjustChatPanelWindowLevel has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 3, match/switch 1 (3 pts) (nesting depth added 6). 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.
TerminalChatPlugin.send (cognitive 22) Core/Sources/LegacyChatPlugin/TerminalChatPlugin.swift:20— TerminalChatPlugin.send has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (18 pts), error handling 2, loops 1 (2 pts) (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.
RequestBody.joinMessageContent (cognitive 22) Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:1004— RequestBody.joinMessageContent has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (18 pts), match/switch 2 (4 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.
ServerNotificationHandler.handleNotification (cognitive 22) Tool/Sources/GitHubCopilotService/LanguageServer/CopilotLocalProcessServer.swift:309— ServerNotificationHandler.handleNotification has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (17 pts), error handling 1 (2 pts), boolean chains 1, loops 1, match/switch 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.
GitHubCopilotBaseService.init (cognitive 22) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:129— GitHubCopilotBaseService.init has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 5 (8 pts), error handling 1 (3 pts), loops 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.
ChatGPTService.sendRequest (cognitive 22) Tool/Sources/OpenAIService/ChatGPTService.swift:294— ChatGPTService.sendRequest has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (17 pts), error handling 3, loops 1 (2 pts) (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.
Terminal.streamCommand (cognitive 21) Tool/Sources/Terminal/Terminal.swift:51— Terminal.streamCommand has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 6, error handling 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.
DependencyUpdater.update (cognitive 20) Core/Sources/Service/DependencyUpdater.swift:9— DependencyUpdater.update has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 4 (10 pts), loops 2 (6 pts), error handling 2 (4 pts) (nesting depth added 12). 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.
GlobalShortcutManager.start (cognitive 20) Core/Sources/Service/GlobalShortcutManager.swift:20— GlobalShortcutManager.start has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 4, 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.
PseudoCommandHandler.acceptActiveSuggestionLineInGroup (cognitive 20) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:285— PseudoCommandHandler.acceptActiveSuggestionLineInGroup 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. This shape REPEATS in the file: one other method here (PseudoCommandHandler.acceptSuggestion) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PseudoCommandHandler.acceptSuggestion (cognitive 20) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:347— PseudoCommandHandler.acceptSuggestion 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. This shape REPEATS in the file: one other method here (PseudoCommandHandler.acceptActiveSuggestionLineInGroup) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
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.
XcodeThemeController.syncXcodeThemeIfNeeded (cognitive 20) Core/Sources/XcodeThemeController/XcodeThemeController.swift:77— XcodeThemeController.syncXcodeThemeIfNeeded has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (13 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.
CodeiumLanguageServer.sendRequest (cognitive 20) Tool/Sources/CodeiumService/LanguageServer/CodeiumLanguageServer.swift:164— CodeiumLanguageServer.sendRequest has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (16 pts), error handling 2 (4 pts) (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.
GitHubCopilotChatService.convertHistory (cognitive 20) Tool/Sources/GitHubCopilotService/Services/GitHubCopilotChatService.swift:158— GitHubCopilotChatService.convertHistory has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (17 pts), match/switch 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.
XcodeInspector.setActiveXcode (cognitive 20) Tool/Sources/XcodeInspector/XcodeInspector.swift:374— XcodeInspector.setActiveXcode has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 3 (5 pts), boolean chains 2 (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.
EmbeddingModelEdit.body (cognitive 19) Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEdit.swift:83— EmbeddingModelEdit.body has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 2 (3 pts), error handling 1 (2 pts), boolean chains 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.
GitHubCopilotService.getCompletions (cognitive 19) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:449— GitHubCopilotService.getCompletions has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (9 pts), error handling 6, match/switch 2 (4 pts) (nesting depth added 6). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to one function item inside it that branches (sendRequest). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
RelevantInformationExtractionChain.callLogic (cognitive 19) Tool/Sources/LangChain/Chains/RelevantInformationExtractionChain.swift:97— RelevantInformationExtractionChain.callLogic has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (9 pts), error handling 2 (6 pts), loops 3 (4 pts) (nesting depth added 10). Of this number, 10 points are the body's own statements and 9 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.
BingSearchResultParser.parse (cognitive 19) Tool/Sources/WebSearchService/SearchServices/HeadlessBrowserSearchService.swift:251— BingSearchResultParser.parse has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (12 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkspaceXcodeWindowInspector.extractProjectURL (cognitive 19) Tool/Sources/XcodeInspector/XcodeWindowInspector.swift:141— 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.
PseudoCommandHandler.generateRealtimeSuggestions (cognitive 18) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:64— PseudoCommandHandler.generateRealtimeSuggestions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (13 pts), error handling 2, match/switch 1 (2 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
NearbyTextCursor.framesForSuggestionWindow (cognitive 18) Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:291— NearbyTextCursor.framesForSuggestionWindow has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 2, ternaries 1 (2 pts), match/switch 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.
WidgetWindowsController.observe (cognitive 18) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:205— WidgetWindowsController.observe has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (4 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.
ActiveDocumentChatContextCollector.extractSystemPrompt (cognitive 18) Tool/Sources/ChatContextCollectors/ActiveDocumentChatContextCollector/ActiveDocumentChatContextCollector.swift:106— ActiveDocumentChatContextCollector.extractSystemPrompt has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 6 (11 pts), boolean chains 5, if/else 2 (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.
CodeiumChatBrowser.body (cognitive 18) Tool/Sources/CodeiumService/ChatTab/CodeiumChatBrowser.swift:47— CodeiumChatBrowser.body has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (6 pts), error handling 1 (2 pts), 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.
RecursiveCharacterTextSplitter.split (cognitive 18) Tool/Sources/LangChain/DocumentTransformer/RecursiveCharacterTextSplitter.swift:58— RecursiveCharacterTextSplitter.split has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (17 pts), 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.
GoogleAIChatCompletionsService.convertMessages (cognitive 18) Tool/Sources/OpenAIService/APIs/GoogleAIChatCompletionsService.swift:134— GoogleAIChatCompletionsService.convertMessages has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 1 (3 pts), 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.
ShortcutChatPlugin.sendForComplicatedResponse (cognitive 17) ChatPlugins/Sources/ShortcutChatPlugin/ShortcutChatPlugin.swift:50— ShortcutChatPlugin.sendForComplicatedResponse has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), error handling 2 (3 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.
ChatPluginController.handleContent (cognitive 17) Core/Sources/ChatService/ChatPluginController.swift:29— ChatPluginController.handleContent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (17 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.
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.
CodeiumLanguageServer.start (cognitive 17) Tool/Sources/CodeiumService/LanguageServer/CodeiumLanguageServer.swift:89— CodeiumLanguageServer.start has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (4 pts), error handling 1 (nesting depth added 9). Of this number, 10 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.
SourceEditor.observeAXNotifications (cognitive 17) Tool/Sources/XcodeInspector/SourceEditor.swift:83— 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.
ChatModelManagement.body (cognitive 16) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift:67— ChatModelManagement.body has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 1, 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.
EmbeddingModelManagement.body (cognitive 16) Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelManagement.swift:59— EmbeddingModelManagement.body has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 1, 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.
WidgetAnimatedCapsule.updateBreathingAnimation (cognitive 16) Core/Sources/SuggestionWidget/WidgetView.swift:119— WidgetAnimatedCapsule.updateBreathingAnimation has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CodeBlockSuggestionPanelView.body (cognitive 16) Core/Sources/SuggestionWidget/SuggestionPanelContent/CodeBlockSuggestionPanelView.swift:221— CodeBlockSuggestionPanelView.body has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 2, match/switch 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AXUIElement.child (cognitive 16) Tool/Sources/AXExtension/AXUIElement.swift:220— AXUIElement.child has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, loops 2 (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.
TextSplitter.split (cognitive 16) Tool/Sources/LangChain/DocumentTransformer/TextSplitter.swift:179— TextSplitter.split has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 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.
AutoManagedChatGPTMemory.generateRetrievedContentMessage (cognitive 16) Tool/Sources/OpenAIService/Memory/AutoManagedChatGPTMemory.swift:268— AutoManagedChatGPTMemory.generateRetrievedContentMessage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (14 pts), loops 2 (nesting depth added 3). None of this is in the body itself: all 16 points belong to 3 function items inside it that branch (buildMessageThatFits, buildMessage, buildMessageThatFits::checkValid). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
FunctionTooLong: PromptToCodePanelView.swift.top-level code Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1083— FunctionTooLong — top-level code runs 152 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× 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.
ClassTooLong: PseudoCommandHandler Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:30— ClassTooLong — 432 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 32 over it, 1.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Change coupling clique: SuggestionCommandHandler.swift, SourceEditorExtension.swift, XPCServiceProtocol.swift Core/Sources/Service/SuggestionCommandHandler/SuggestionCommandHandler.swift— 3 files — `Core/Sources/Service/SuggestionCommandHandler/SuggestionCommandHandler.swift`, `EditorExtension/SourceEditorExtension.swift`, `Tool/Sources/XPCShared/XPCServiceProtocol.swift` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
Change-coupling hub: ChatGPTService.swift → AskChatGPT.swift, OpenAIChat.swift, GoogleAIChatCompletionsService.swift, Models.swift Tool/Sources/OpenAIService/ChatGPTService.swift— `Tool/Sources/OpenAIService/ChatGPTService.swift` changes together with 4 other files — `Core/Sources/LegacyChatPlugin/AskChatGPT.swift`, `Tool/Sources/LangChain/ChatModel/OpenAIChat.swift`, `Tool/Sources/OpenAIService/APIs/GoogleAIChatCompletionsService.swift`, `Tool/Sources/OpenAIService/Models.swift` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
Near-duplicate member pair (58 shared lines) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:11— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:11-94 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:10-70 — These two members are variants of one another: 58 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (32 shared lines) Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift:225— Tool/Sources/OpenAIService/APIs/ClaudeChatCompletionsService.swift:225-290 | Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:636-697 — These two members are variants of one another: 32 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (77 corresponding lines) · ×1
Edited copy of a member (77 corresponding lines) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift:67— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift:67-143 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelManagement.swift:59-135 — These two members are one piece of code written twice and then edited apart: 77 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 (78 corresponding lines) · ×1
Edited copy of a member (78 corresponding lines) Core/Sources/HostApp/AccountSettings/APIKeyManagement/APIKeyManagementView.swift:8— Core/Sources/HostApp/AccountSettings/APIKeyManagement/APIKeyManagementView.swift:8-91 | Core/Sources/HostApp/FeatureSettings/Suggestion/SuggestionFeatureEnabledProjectListView.swift:20-97 — These two members are one piece of code written twice and then edited apart: 78 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 (61 corresponding lines) · ×1
Edited copy of a member (61 corresponding lines) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:208— Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:208-273 | Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:285-345 — These two members are one piece of code written twice and then edited apart: 61 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 (46 corresponding lines) · ×1
Edited copy of a member (46 corresponding lines) Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift:68— Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift:68-118 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotInstallationManager.swift:29-74 — These two members are one piece of code written twice and then edited apart: 46 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 (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) Tool/Sources/CodeiumService/Services/CodeiumService.swift:165— Tool/Sources/CodeiumService/Services/CodeiumService.swift:165-200 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:312-349 — These two members are one piece of code written twice and then edited apart: 36 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 (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) Tool/Sources/WebSearchService/SearchServices/HeadlessBrowserSearchService.swift:140— Tool/Sources/WebSearchService/SearchServices/HeadlessBrowserSearchService.swift:140-170 | Tool/Sources/WebSearchService/SearchServices/HeadlessBrowserSearchService.swift:251-283 — These two members are one piece of code written twice and then edited apart: 31 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, 39+ corresponding lines) · ×1
Edited copies of one member (3 members, 39+ corresponding lines) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:327— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:327-377 | Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:531-574 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:249-287 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 39 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 (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) Tool/Sources/WebSearchService/SearchServices/AppleDocumentationSearchService.swift:28— Tool/Sources/WebSearchService/SearchServices/AppleDocumentationSearchService.swift:28-58 | Tool/Sources/WebSearchService/SearchServices/HeadlessBrowserSearchService.swift:57-81 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (49 corresponding lines) · ×1
Edited copy of a member (49 corresponding lines) Tool/Sources/OpenAIService/APIs/ChatCompletionsAPIBuilder.swift:23— Tool/Sources/OpenAIService/APIs/ChatCompletionsAPIBuilder.swift:23-71 | Tool/Sources/OpenAIService/APIs/ChatCompletionsAPIBuilder.swift:73-121 — These two members are one piece of code written twice and then edited apart: 49 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 (38 corresponding lines) · ×1
Edited copy of a member (38 corresponding lines) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:404— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:404-451 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:311-348 — These two members are one piece of code written twice and then edited apart: 38 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 (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) Tool/Sources/FocusedCodeFinder/ObjectiveC/ObjectiveCCodeFinder.swift:181— Tool/Sources/FocusedCodeFinder/ObjectiveC/ObjectiveCCodeFinder.swift:181-206 | Tool/Sources/FocusedCodeFinder/ObjectiveC/ObjectiveCCodeFinder.swift:212-234 — 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 (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:499— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:499-526 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:355-388 — 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 (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:32— Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:32-54 | Tool/Sources/SharedUIComponents/AsyncDiffCodeBlock.swift:30-51 — 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 copies of one member (3 members, 22+ corresponding lines) · ×1
Edited copies of one member (3 members, 22+ corresponding lines) EditorExtension/AcceptPromptToCodeCommand.swift:9— EditorExtension/AcceptPromptToCodeCommand.swift:9-30 | EditorExtension/AcceptSuggestionCommand.swift:10-31 | EditorExtension/AcceptSuggestionCommand.swift:37-59 — 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 copy of a member (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) Tool/Sources/FocusedCodeFinder/ObjectiveC/ObjectiveCCodeFinder.swift:26— Tool/Sources/FocusedCodeFinder/ObjectiveC/ObjectiveCCodeFinder.swift:26-45 | Tool/Sources/FocusedCodeFinder/Swift/SwiftFocusedCodeFinder.swift:21-41 — 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 (3 members, 17+ corresponding lines) · ×1
Edited copies of one member (3 members, 17+ corresponding lines) Core/Sources/HostApp/CustomCommandSettings/EditCustomCommandView.swift:277— Core/Sources/HostApp/CustomCommandSettings/EditCustomCommandView.swift:277-294 | Core/Sources/HostApp/CustomCommandSettings/EditCustomCommandView.swift:300-316 | Core/Sources/HostApp/CustomCommandSettings/EditCustomCommandView.swift:323-340 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 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/SharedUIComponents/SyntaxHighlighting.swift:120— Tool/Sources/SharedUIComponents/SyntaxHighlighting.swift:120-138 | Tool/Sources/SharedUIComponents/SyntaxHighlighting.swift:140-158 | Tool/Sources/SharedUIComponents/SyntaxHighlighting.swift:160-179 — 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 (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) Core/Sources/HostApp/AccountSettings/WebSearchView.swift:150— Core/Sources/HostApp/AccountSettings/WebSearchView.swift:150-174 | Core/Sources/HostApp/AccountSettings/WebSearchView.swift:176-193 — 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 copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:113— Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:113-127 | Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:137-153 | Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:180-196 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 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, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) Tool/Sources/ChatTab/ChatTab.swift:96— Tool/Sources/ChatTab/ChatTab.swift:96-106 | Tool/Sources/ChatTab/ChatTab.swift:110-120 | Tool/Sources/ChatTab/ChatTab.swift:135-145 — 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 copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) Core/Sources/Service/SuggestionCommandHandler/WindowBaseCommandHandler.swift:77— Core/Sources/Service/SuggestionCommandHandler/WindowBaseCommandHandler.swift:77-90 | Core/Sources/Service/SuggestionCommandHandler/WindowBaseCommandHandler.swift:103-116 | Core/Sources/Service/SuggestionCommandHandler/WindowBaseCommandHandler.swift:129-138 — 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 (3 members, 12+ corresponding lines) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) Tool/Sources/BuiltinExtension/BuiltinExtensionWorkspacePlugin.swift:35— Tool/Sources/BuiltinExtension/BuiltinExtensionWorkspacePlugin.swift:35-46 | Tool/Sources/BuiltinExtension/BuiltinExtensionWorkspacePlugin.swift:48-60 | Tool/Sources/BuiltinExtension/BuiltinExtensionWorkspacePlugin.swift:62-73 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 9+ corresponding lines) · ×1
Edited copies of one member (4 members, 9+ corresponding lines) Core/Sources/ChatGPTChatTab/ChatPanel.swift:573— Core/Sources/ChatGPTChatTab/ChatPanel.swift:573-581 | Core/Sources/ChatGPTChatTab/ChatPanel.swift:585-593 | Core/Sources/ChatGPTChatTab/ChatPanel.swift:597-612 | Core/Sources/ChatGPTChatTab/ChatPanel.swift:616-624 — 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 (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) Tool/Sources/Preferences/UserDefaults.swift:149— Tool/Sources/Preferences/UserDefaults.swift:149-156 | Tool/Sources/Preferences/UserDefaults.swift:158-166 | Tool/Sources/Preferences/UserDefaults.swift:224-232 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 11+ corresponding lines) · ×1
Edited copies of one member (5 members, 11+ corresponding lines) Tool/Sources/CodeiumService/CodeiumExtension.swift:46— Tool/Sources/CodeiumService/CodeiumExtension.swift:46-56 | Tool/Sources/CodeiumService/CodeiumExtension.swift:58-68 | Tool/Sources/CodeiumService/CodeiumExtension.swift:94-104 | Tool/Sources/GitHubCopilotService/GitHubCopilotExtension.swift:72-82 | Tool/Sources/GitHubCopilotService/GitHubCopilotExtension.swift:84-94 — 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 copy of a member (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) Tool/Sources/Preferences/UserDefaults.swift:134— Tool/Sources/Preferences/UserDefaults.swift:134-139 | Tool/Sources/Preferences/UserDefaults.swift:281-287 — 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.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×1
Edited copy of a member (7 corresponding lines) Tool/Sources/LangChain/Chains/CombineAnswersChain.swift:56— Tool/Sources/LangChain/Chains/CombineAnswersChain.swift:56-62 | Tool/Sources/LangChain/Chains/StructuredOutputChatModelChain.swift:99-105 — 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 (57 lines × 2) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagementView.swift:27— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagementView.swift:27-83 | Core/Sources/HostApp/AccountSettings/SharedModelManagement/AIModelManagementVIew.swift:195-251 — 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/HostApp/AccountSettings/ChatModelManagement/ChatModelManagementView.swift:27` 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 (55 lines × 2) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:286— Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:286-340 | Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:348-402 — 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:286` 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 (41 lines × 2) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift:74— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift:74-114 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelManagement.swift:66-106 — `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift` and `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelManagement.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 68 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelManagement.swift:74` 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 (31–32 lines × 2) Core/Sources/SuggestionWidget/SuggestionPanelContent/CodeBlockSuggestionPanelView.swift:367— Core/Sources/SuggestionWidget/SuggestionPanelContent/CodeBlockSuggestionPanelView.swift:367-397 | Core/Sources/SuggestionWidget/SuggestionPanelContent/CodeBlockSuggestionPanelView.swift:400-431 — 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/SuggestionPanelContent/CodeBlockSuggestionPanelView.swift:367` 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 (32 lines × 2) Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:765— Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:765-796 | Tool/Sources/OpenAIService/APIs/OpenAIResponsesRawService.swift:167-198 — before extracting anything, compare `Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift` and `Tool/Sources/OpenAIService/APIs/OpenAIResponsesRawService.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (30 lines × 2) Tool/Sources/AppActivator/AppActivator.swift:93— Tool/Sources/AppActivator/AppActivator.swift:93-122 | Tool/Sources/XcodeInspector/XcodeInspector+TriggerCommand.swift:144-173 — 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 (28–29 lines × 2) Core/Sources/Service/DependencyUpdater.swift:14— Core/Sources/Service/DependencyUpdater.swift:14-42 | Core/Sources/Service/DependencyUpdater.swift:47-74 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/Service/DependencyUpdater.swift:14` 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 (28 lines × 3) Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1115— Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1115-1142 | Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1182-1209 | Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1237-1264 — 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/PromptToCodePanelView.swift:1115` 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 (25–26 lines × 2) Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:168— Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:168-193 | Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:232-256 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:168` 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 (24 lines × 2) Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift:90— Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift:90-113 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotInstallationManager.swift:45-68 — before extracting anything, compare `Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift` and `Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotInstallationManager.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift:90` 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) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:72— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:72-94 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:48-70 — before extracting anything, compare `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift` and `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 180 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/AccountSettings/ChatModelManagement/ChatModelEditView.swift:72` 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 (21–23 lines × 2) Core/Sources/SuggestionWidget/SuggestionPanelContent/CodeBlockSuggestionPanelView.swift:61— Core/Sources/SuggestionWidget/SuggestionPanelContent/CodeBlockSuggestionPanelView.swift:61-83 | Core/Sources/SuggestionWidget/SuggestionPanelContent/CodeBlockSuggestionPanelView.swift:136-156 — 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/SuggestionPanelContent/CodeBlockSuggestionPanelView.swift:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:515— Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:515-536 | Tool/Sources/SharedUIComponents/AsyncDiffCodeBlock.swift:429-450 — before extracting anything, compare `Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift` and `Tool/Sources/SharedUIComponents/AsyncDiffCodeBlock.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:515` 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 (38–39 lines × 3) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:217— Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:217-255 | Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:290-327 | Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:352-389 — 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/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:217` 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 (21 lines × 2) Core/Sources/HostApp/AccountSettings/CodeiumView.swift:67— Core/Sources/HostApp/AccountSettings/CodeiumView.swift:67-87 | Core/Sources/HostApp/AccountSettings/GitHubCopilotView.swift:55-75 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (19 lines × 4) Tool/Sources/CodeiumService/Services/CodeiumSuggestionService.swift:62— Tool/Sources/CodeiumService/Services/CodeiumSuggestionService.swift:62-80 | Tool/Sources/CodeiumService/Services/CodeiumSuggestionService.swift:85-103 | Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift:64-82 | Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift:87-105 — before extracting anything, compare `Tool/Sources/CodeiumService/Services/CodeiumSuggestionService.swift` and `Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `Tool/Sources/CodeiumService/Services/CodeiumSuggestionService.swift:62` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 3) Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:744— Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:744-762 | Tool/Sources/OpenAIService/APIs/OpenAIEmbeddingService.swift:107-125 | Tool/Sources/OpenAIService/APIs/OpenAIResponsesRawService.swift:146-164 — before extracting anything, compare `Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift` and `Tool/Sources/OpenAIService/APIs/OpenAIResponsesRawService.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:744` 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 (19 lines × 2) Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:256— Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:256-274 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:397-415 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:417` calls `Button`, `toggle` and `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:276` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (17–19 lines × 2) Tool/Sources/FocusedCodeFinder/ObjectiveC/ObjectiveCCodeFinder.swift:188— Tool/Sources/FocusedCodeFinder/ObjectiveC/ObjectiveCCodeFinder.swift:188-206 | Tool/Sources/FocusedCodeFinder/ObjectiveC/ObjectiveCCodeFinder.swift:218-234 — 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/FocusedCodeFinder/ObjectiveC/ObjectiveCCodeFinder.swift:188` 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 (18 lines × 2) Tool/Sources/SharedUIComponents/SubSection.swift:78— Tool/Sources/SharedUIComponents/SubSection.swift:78-95 | Tool/Sources/SharedUIComponents/SubSection.swift:97-114 — 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/SharedUIComponents/SubSection.swift:78` 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 (13–17 lines × 4) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:327— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:327-339 | Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:457-473 | Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:531-544 | Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift:249-261 — before extracting anything, compare `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift` and `Core/Sources/HostApp/AccountSettings/EmbeddingModelManagement/EmbeddingModelEditView.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 180 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/AccountSettings/ChatModelManagement/ChatModelEditView.swift:327` 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 lines × 3) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:257— Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:257-273 | Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:329-345 | Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:391-407 — 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/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:257` 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 (17 lines × 2) Core/Sources/PromptToCodeService/OpenAIPromptToCodeService.swift:134— Core/Sources/PromptToCodeService/OpenAIPromptToCodeService.swift:134-150 | Core/Sources/PromptToCodeService/OpenAIPromptToCodeService.swift:152-168 — 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 (16 lines × 3) Tool/Sources/SharedUIComponents/SubSection.swift:78— Tool/Sources/SharedUIComponents/SubSection.swift:78-93 | Tool/Sources/SharedUIComponents/SubSection.swift:97-112 | Tool/Sources/SharedUIComponents/SubSection.swift:116-131 — 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 `Tool/Sources/SharedUIComponents/SubSection.swift:78` 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 (15–16 lines × 2) Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift:159— Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift:159-173 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotInstallationManager.swift:115-130 — before extracting anything, compare `Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift` and `Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotInstallationManager.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `Tool/Sources/CodeiumService/LanguageServer/CodeiumInstallationManager.swift:159` 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 register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (12–15 lines × 2) Core/Sources/Service/RealtimeSuggestionController.swift:75— Core/Sources/Service/RealtimeSuggestionController.swift:75-86 | Core/Sources/Service/RealtimeSuggestionController.swift:94-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. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/Service/RealtimeSuggestionController.swift:75` 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 (22–24 lines × 2) Tool/Sources/CodeiumService/Services/CodeiumService.swift:177— Tool/Sources/CodeiumService/Services/CodeiumService.swift:177-200 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:328-349 — 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 `Tool/Sources/CodeiumService/Services/CodeiumService.swift:177` 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 `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 (12 lines × 3) Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1083— Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1083-1094 | Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1165-1176 | Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1220-1231 — 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/PromptToCodePanelView.swift:1083` 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/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1096` calls `init` and `Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1178` 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 (11–12 lines × 3) Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1097— Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1097-1107 | Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1177-1188 | Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1232-1243 — 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/PromptToCodePanelView.swift:1097` 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 lines × 3) Tool/Sources/OpenAIService/EmbeddingService.swift:13— Tool/Sources/OpenAIService/EmbeddingService.swift:13-22 | Tool/Sources/OpenAIService/EmbeddingService.swift:49-58 | Tool/Sources/OpenAIService/EmbeddingService.swift:85-94 — 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 `Tool/Sources/OpenAIService/EmbeddingService.swift:13` 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–9 lines × 7) Tool/Sources/FocusedCodeFinder/Swift/SwiftFocusedCodeFinder.swift:76— Tool/Sources/FocusedCodeFinder/Swift/SwiftFocusedCodeFinder.swift:76-84 | Tool/Sources/FocusedCodeFinder/Swift/SwiftFocusedCodeFinder.swift:89-97 | Tool/Sources/FocusedCodeFinder/Swift/SwiftFocusedCodeFinder.swift:102-110 | Tool/Sources/FocusedCodeFinder/Swift/SwiftFocusedCodeFinder.swift:115-123 | Tool/Sources/FocusedCodeFinder/Swift/SwiftFocusedCodeFinder.swift:126-132 | Tool/Sources/FocusedCodeFinder/Swift/SwiftFocusedCodeFinder.swift:140-148 | Tool/Sources/FocusedCodeFinder/Swift/SwiftFocusedCodeFinder.swift:153-161 — all 7 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/FocusedCodeFinder/Swift/SwiftFocusedCodeFinder.swift:126` 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. 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 (9 lines × 3) Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:1154— Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:1154-1162 | Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:1188-1196 | Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:1212-1220 — 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 `Tool/Sources/OpenAIService/APIs/OpenAIChatCompletionsService.swift:1154` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–9 lines × 2) Tool/Sources/XPCShared/XPCExtensionService.swift:242— Tool/Sources/XPCShared/XPCExtensionService.swift:242-249 | Tool/Sources/XPCShared/XPCExtensionService.swift:269-277 — 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:242` 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 lines × 3) Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:265— Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:265-272 | Core/Sources/HostApp/AccountSettings/CodeiumView.swift:248-255 | Core/Sources/HostApp/SharedComponents/EditableText.swift:51-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:265` 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/HostApp/AccountSettings/CodeiumView.swift:258` calls `Spacer` and `Core/Sources/HostApp/SharedComponents/EditableText.swift:60` 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 (7–8 lines × 2) Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:491— Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:491-498 | Tool/Sources/SharedUIComponents/AsyncCodeBlock.swift:506-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. 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 × 4) Tool/Sources/GitHubCopilotService/GitHubCopilotExtension.swift:279— Tool/Sources/GitHubCopilotService/GitHubCopilotExtension.swift:279-285 | Tool/Sources/OpenAIService/APIs/GitHubCopilotChatCompletionsService.swift:101-107 | Tool/Sources/OpenAIService/APIs/GitHubCopilotEmbeddingService.swift:61-67 | Tool/Sources/OpenAIService/APIs/OpenAIResponsesRawService.swift:203-209 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (7 lines × 3) Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1157— Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1157-1163 | Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1212-1218 | Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanelView.swift:1269-1275 — 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/PromptToCodePanelView.swift:1157` 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 (11–15 lines × 2) Core/Sources/PromptToCodeService/OpenAIPromptToCodeService.swift:274— Core/Sources/PromptToCodeService/OpenAIPromptToCodeService.swift:274-284 | Core/Sources/PromptToCodeService/OpenAIPromptToCodeService.swift:286-300 — 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 (3–5 lines × 4) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:234— Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:234-238 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:250-254 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:300-302 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:316-320 — 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:234` 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:302` calls `JSONDecoder`, `decode`, `hash` and `Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:238` 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 (14 lines × 4) Core/Sources/HostApp/AccountSettings/CodeiumView.swift:101— Core/Sources/HostApp/AccountSettings/CodeiumView.swift:101-114 | Core/Sources/HostApp/AccountSettings/CodeiumView.swift:116-129 | Core/Sources/HostApp/AccountSettings/GitHubCopilotView.swift:106-119 | Core/Sources/HostApp/AccountSettings/GitHubCopilotView.swift:121-134 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (10 lines × 6) 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/RealtimeSuggestionCommand.swift:9-18 | EditorExtension/RejectSuggestionCommand.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 6 call sites, so a change lands once.
Duplicated block (5 lines × 4) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:400— Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:400-404 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:425-429 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:444-448 | Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:461-465 — 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. 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 CI gate on code changes — A workflow is configured, but the repository's only workflow is `REDACTED`, which neither runs on a code change (no `push` or `pull_request` trigger) nor checks the code out — so nothing here builds or tests a change before it merges. This is automation for the repository's ISSUES AND HOUSEKEEPING, not a gate on its code: a pull request can land without anything having compiled or run it. The rows about missing build and test steps are deliberately not reported beside this one, because there is no pipeline for them to be missing from — adding the gate is one action, not three.
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.
Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:19— `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:23— `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:31— `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:35— `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:39— `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:48— `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:53— `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:57— `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:155— `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:163— `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:201— `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:209— `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:217— `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.
Silent fallback default in catch Tool/Sources/ChatContextCollector/ChatContextCollector.swift:93— `parseScopes` 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/GitIgnoreCheck/GitIgnoreCheck.swift:87— `checkIfGitIgnored` 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/OpenAIService/Configuration/ChatGPTConfiguration.swift:123— `apiKey` 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 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· `codeiumPortalUrl` spells `Url` where 42 names in the project spell it `URL` · ×1
`codeiumPortalUrl` spells `Url` where 42 names in the project spell it `URL` Core/Sources/HostApp/AccountSettings/CodeiumView.swift:15— 42 of 44 names in project Core~ChatContextCollectors spell the token `URL` (42 of 44; unit: names in project Core~ChatContextCollectors containing `URL`). Peers: FileChangeChecker.init(fileURL) (Core/Sources/FileChangeChecker/FileChangeChecker.swift:10); State.baseURL (Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift:23); State.isFullURL (Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift:24); State.baseURLSelection (Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift:30); Core~HostApp.BaseURLTextField (Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:152). Rename to `codeiumPortalURL`. [rule N6]
D21 · Naming Consistency· `codeiumApiUrl` spells `Url` where 42 names in the project spell it `URL` · ×1
`codeiumApiUrl` spells `Url` where 42 names in the project spell it `URL` Core/Sources/HostApp/AccountSettings/CodeiumView.swift:16— 42 of 44 names in project Core~ChatContextCollectors spell the token `URL` (42 of 44; unit: names in project Core~ChatContextCollectors containing `URL`). Peers: FileChangeChecker.init(fileURL) (Core/Sources/FileChangeChecker/FileChangeChecker.swift:10); State.baseURL (Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift:23); State.isFullURL (Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift:24); State.baseURLSelection (Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEdit.swift:30); Core~HostApp.BaseURLTextField (Core/Sources/HostApp/AccountSettings/ChatModelManagement/ChatModelEditView.swift:152). Rename to `codeiumApiURL`. [rule N6]
D21 · Naming Consistency· `codeiumPortalUrl` spells `Url` where 151 names in the project spell it `URL` · ×1
`codeiumPortalUrl` spells `Url` where 151 names in the project spell it `URL` Tool/Sources/Preferences/Keys.swift:224— 151 of 155 names in project Tool~AIModel spell the token `URL` (151 of 155; unit: names in project Tool~AIModel containing `URL`). Peers: Workspace.isFilespaceExpired(fileURL) (Core/Sources/Service/WorkspaceExtension/Workspace+Cleanup.swift:17); Info.baseURL (Tool/Sources/AIModel/ChatModel.swift:109); Info.isFullURL (Tool/Sources/AIModel/ChatModel.swift:111); Info.init(baseURL) (Tool/Sources/AIModel/ChatModel.swift:136); Info.init(isFullURL) (Tool/Sources/AIModel/ChatModel.swift:136). Rename to `codeiumPortalURL`. [rule N6]
D21 · Naming Consistency· `codeiumApiUrl` spells `Url` where 151 names in the project spell it `URL` · ×1
`codeiumApiUrl` spells `Url` where 151 names in the project spell it `URL` Tool/Sources/Preferences/Keys.swift:228— 151 of 155 names in project Tool~AIModel spell the token `URL` (151 of 155; unit: names in project Tool~AIModel containing `URL`). Peers: Workspace.isFilespaceExpired(fileURL) (Core/Sources/Service/WorkspaceExtension/Workspace+Cleanup.swift:17); Info.baseURL (Tool/Sources/AIModel/ChatModel.swift:109); Info.isFullURL (Tool/Sources/AIModel/ChatModel.swift:111); Info.init(baseURL) (Tool/Sources/AIModel/ChatModel.swift:136); Info.init(isFullURL) (Tool/Sources/AIModel/ChatModel.swift:136). Rename to `codeiumApiURL`. [rule N6]
D21 · Naming Consistency· `webSearchUrl` spells `Url` where 151 names in the project spell it `URL` · ×1
`webSearchUrl` spells `Url` where 151 names in the project spell it `URL` Tool/Sources/WebSearchService/SearchServices/BingSearchService.swift:7— 151 of 155 names in project Tool~AIModel spell the token `URL` (151 of 155; unit: names in project Tool~AIModel containing `URL`). Peers: Workspace.isFilespaceExpired(fileURL) (Core/Sources/Service/WorkspaceExtension/Workspace+Cleanup.swift:17); Info.baseURL (Tool/Sources/AIModel/ChatModel.swift:109); Info.isFullURL (Tool/Sources/AIModel/ChatModel.swift:111); Info.init(baseURL) (Tool/Sources/AIModel/ChatModel.swift:136); Info.init(isFullURL) (Tool/Sources/AIModel/ChatModel.swift:136). Rename to `webSearchURL`. [rule N6]
D21 · Naming Consistency· `displayUrl` spells `Url` where 151 names in the project spell it `URL` · ×1
`displayUrl` spells `Url` where 151 names in the project spell it `URL` Tool/Sources/WebSearchService/SearchServices/BingSearchService.swift:15— 151 of 155 names in project Tool~AIModel spell the token `URL` (151 of 155; unit: names in project Tool~AIModel containing `URL`). Peers: Workspace.isFilespaceExpired(fileURL) (Core/Sources/Service/WorkspaceExtension/Workspace+Cleanup.swift:17); Info.baseURL (Tool/Sources/AIModel/ChatModel.swift:109); Info.isFullURL (Tool/Sources/AIModel/ChatModel.swift:111); Info.init(baseURL) (Tool/Sources/AIModel/ChatModel.swift:136); Info.init(isFullURL) (Tool/Sources/AIModel/ChatModel.swift:136). Rename to `displayURL`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 5 project(s) overshoot their size bounds, lowering Project Cohesion to 2.0/10. The most over is `Tool` (29277 LoC, 864 module-visible types across 70 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.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
Outdated: aexml — `aexml` is resolved at 4.7.0, but 4.7.3 is the newest release tagged on https://github.com/tadija/AEXML.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 aexml` reaches this one with no change to Package.swift.
Outdated: cgeventoverride — `cgeventoverride` is resolved at 1.2.3, but 1.3.1 is the newest release tagged on https://github.com/intitni/CGEventOverride within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update cgeventoverride` reaches this one with no change to Package.swift.
Outdated: combine-schedulers — `combine-schedulers` is resolved at 1.0.3, 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: combine-schedulers — `combine-schedulers` is resolved at 0.10.0, but 0.11.0 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: highlightr — `highlightr` is resolved at 2.1.2, but 2.3.0 is the newest release tagged on https://github.com/raspu/Highlightr within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update highlightr` reaches this one with no change to Package.swift.
Outdated: jsonrpc — `jsonrpc` is resolved at 0.6.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: languageclient — `languageclient` is resolved at 0.3.1, but 0.8.2 is the newest release tagged on https://github.com/ChimeHQ/LanguageClient within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update languageclient` reaches this one with no change to Package.swift.
Outdated: languageserverprotocol — `languageserverprotocol` is resolved at 0.8.0, 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: sourcekitten — `sourcekitten` is resolved at 0.37.0, but 0.39.0 is the newest release tagged on https://github.com/jpsim/SourceKitten within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update sourcekitten` reaches this one with no change to Package.swift.
Outdated: sparkle — `sparkle` is resolved at 2.9.2, 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: 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.4, 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.7.0, 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.6, 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-clocks — `swift-clocks` is resolved at 0.3.0, but 0.4.0 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-cmark — `swift-cmark` is resolved at 0.6.0, but 0.9.0 is the newest release tagged on https://github.com/swiftlang/swift-cmark 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-cmark` reaches this one with no change to Package.swift.
Outdated: swift-collections — `swift-collections` is resolved at 1.1.4, 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-collections — `swift-collections` is resolved at 1.0.4, but 1.7.6 is the newest release tagged on https://github.com/apple/swift-collections.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-collections` reaches this one with no change to Package.swift.
Outdated: swift-composable-architecture — `swift-composable-architecture` is resolved at 1.16.1, 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-composable-architecture — `swift-composable-architecture` is resolved at 0.55.0, but 0.59.0 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.3.1, 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.3, 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-custom-dump — `swift-custom-dump` is resolved at 0.11.0, but 0.11.2 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 0.5.1, but 0.6.0 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-dependencies — `swift-dependencies` is resolved at 1.9.2, 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.
+ 12 more in this group — see findings.md.
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 58 file(s) — `CommunicationBridge/ServiceDelegate.swift`, `Core/Sources/ChatGPTChatTab/ChatPanel.swift`, `Core/Sources/ChatGPTChatTab/Views/BotMessage.swift`, `Core/Sources/ChatGPTChatTab/Views/FunctionMessage.swift`, `Core/Sources/ChatGPTChatTab/Views/UserMessage.swift`, … (+53 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1d93a-914b-77dc-8ddd-38110a5022fc · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 9 · Warnings: 438 · Recommendations: 30 · Info: 37 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 08:44 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.