Executive summary
github/CopilotForXcode falls short of our standard for a preview release, in part because it has pages that don't say their language. It scores 52 out of 100 and is rated Adequate, and five of its nine critical findings are security problems in the packages it uses.
Accessibility, at 45, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 4 points. Structuring the pages would lift Accessibility itself, worth about 3 points. Raising Accessibility to 65 would lift the score to about 57.
Five known security holes in the packages the code depends on can be used by attackers. Updating the vulnerable packages would close this risk. The two pages that don't say their language need their language set.
The product code is 73,217 lines, about €76,000 to rebuild.
If Accessibility rose from 45 to 65, the lowest score rated Strong, the score would rise from 52 to about 57.
Fixed since the last survey: 1 finding
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Rebuild cost: about €76,000 · Estimate
| Cost to rebuild | €25,000 to €130,000, for 419 to 1,329 hours of work, about 0.5 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 52. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 73,217 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Core~UserDefaultsObserver | 2 Tool~Preferences | 3 Core~LaunchAgentManager | 4 Tool~ActiveApplicationMonitor | 5 Tool~GitHelper | 6 Tool~Logger | 7 Tool~Persist | 8 Tool~SuggestionBasic | 9 Tool~TelemetryServiceProvider | 10 Tool~Toast | 11 Core~PromptToCodeService | 12 Tool~ChatTab | 13 Tool~SuggestionProvider | 14 Core~SuggestionService | 15 Tool~BuiltinExtension | 16 Tool~WorkspaceSuggestionService | 17 Tool~GitHubCopilotService | 18 Tool~Status | 19 Tool~XcodeInspector | 20 Tool~ChatAPIService | 21 Tool~ConversationServiceProvider | 22 Tool~SharedUIComponents | 23 Tool~Workspace | 24 Core~KeyBindingManager | 25 Core~Service | 26 Tool~XPCShared | 27 repository | 28 Tool~AXExtension | 29 Core~SuggestionWidget | 30 Core~XcodeThemeController | 31 Tool~FileSystem | 32 Core~GitHubCopilotViewModel | 33 Core~HostApp | 34 Core~PersistMiddleware | 35 Tool~AXNotificationStream | 36 Tool~TelemetryService | 37 Tool~Terminal | 38 Core~ConversationTab | 39 Core~ChatService | 40 Tool~HostAppActivator |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Core~UserDefaultsObserver | 1 | |||||||||||||||||||||||||||||||||||||||
| 2 Tool~Preferences | 2 | 13 | 1 | |||||||||||||||||||||||||||||||||||||
| 3 Core~LaunchAgentManager | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 4 Tool~ActiveApplicationMonitor | 2 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 5 Tool~GitHelper | 1 | 7 | 5 | |||||||||||||||||||||||||||||||||||||
| 6 Tool~Logger | 3 | 2 | 3 | 9 | ||||||||||||||||||||||||||||||||||||
| 7 Tool~Persist | 9 | 2 | 1 | 3 | 12 | 3 | ||||||||||||||||||||||||||||||||||
| 8 Tool~SuggestionBasic | 8 | 1 | 9 | 3 | ||||||||||||||||||||||||||||||||||||
| 9 Tool~TelemetryServiceProvider | 2 | 1 | 5 | |||||||||||||||||||||||||||||||||||||
| 10 Tool~Toast | 2 | 4 | 3 | |||||||||||||||||||||||||||||||||||||
| 11 Core~PromptToCodeService | 3 | 2 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 12 Tool~ChatTab | 7 | 3 | 2 | 2 | 9 | 4 | ||||||||||||||||||||||||||||||||||
| 13 Tool~SuggestionProvider | 4 | 7 | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 14 Core~SuggestionService | 1 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 15 Tool~BuiltinExtension | 2 | 1 | 4 | 2 | 20 | 3 | 4 | 7 | 3 | |||||||||||||||||||||||||||||||
| 16 Tool~WorkspaceSuggestionService | 1 | 3 | 4 | 1 | 4 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 17 Tool~GitHubCopilotService | 69 | 3 | 9 | 9 | 6 | 2 | 1 | 1 | 4 | 1 | 90 | 4 | 1 | 1 | 3 | 113 | 12 | |||||||||||||||||||||||
| 18 Tool~Status | 8 | 1 | 5 | 1 | 11 | |||||||||||||||||||||||||||||||||||
| 19 Tool~XcodeInspector | 6 | 2 | 1 | 1 | 6 | 7 | 2 | 1 | 7 | 5 | 1 | |||||||||||||||||||||||||||||
| 20 Tool~ChatAPIService | 7 | 1 | 2 | 1 | 11 | 1 | 16 | 5 | ||||||||||||||||||||||||||||||||
| 21 Tool~ConversationServiceProvider | 36 | 2 | 1 | 2 | 1 | 82 | 9 | |||||||||||||||||||||||||||||||||
| 22 Tool~SharedUIComponents | 38 | 3 | 1 | 1 | 12 | 1 | 21 | 48 | ||||||||||||||||||||||||||||||||
| 23 Tool~Workspace | 1 | 20 | 4 | 1 | 2 | 2 | 1 | 7 | 1 | 1 | 2 | 1 | 12 | 19 | ||||||||||||||||||||||||||
| 24 Core~KeyBindingManager | 1 | 3 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 25 Core~Service | 8 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 4 | 1 | 7 | 3 | 2 | 4 | 5 | 3 | 8 | 7 | ||||||||||||||||||||||
| 26 Tool~XPCShared | 7 | 3 | 4 | 17 | 3 | 1 | 5 | 1 | 3 | 6 | 14 | |||||||||||||||||||||||||||||
| 27 repository | 4 | 1 | 1 | 4 | 27 | 2 | ||||||||||||||||||||||||||||||||||
| 28 Tool~AXExtension | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 Core~SuggestionWidget | 1 | 74 | 4 | 11 | 1 | 4 | 1 | 8 | 14 | 3 | 3 | 8 | 5 | 2 | 42 | 100 | ||||||||||||||||||||||||
| 30 Core~XcodeThemeController | 7 | 1 | 1 | 6 | 3 | |||||||||||||||||||||||||||||||||||
| 31 Tool~FileSystem | 28 | 1 | 1 | 4 | 22 | 1 | ||||||||||||||||||||||||||||||||||
| 32 Core~GitHubCopilotViewModel | 1 | 4 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 33 Core~HostApp | 73 | 1 | 1 | 1 | 3 | 1 | 2 | 41 | 3 | 1 | 16 | 2 | 2 | 1 | 3 | 2 | 2 | 7 | 1 | 77 | 1 | |||||||||||||||||||
| 34 Core~PersistMiddleware | 4 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 35 Tool~AXNotificationStream | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 Tool~TelemetryService | 1 | 5 | 3 | 2 | 4 | |||||||||||||||||||||||||||||||||||
| 37 Tool~Terminal | 5 | 1 | 6 | 2 | ||||||||||||||||||||||||||||||||||||
| 38 Core~ConversationTab | 120 | 1 | 5 | 2 | 1 | 1 | 18 | 69 | 5 | 5 | 7 | 4 | 65 | 2 | 5 | |||||||||||||||||||||||||
| 39 Core~ChatService | 29 | 2 | 2 | 3 | 2 | 10 | 2 | 10 | 31 | 1 | 2 | 1 | 2 | 1 | 28 | 6 | ||||||||||||||||||||||||
| 40 Tool~HostAppActivator | 1 | 1 | 1 | 2 | 1 |
1→33 Core~UserDefaultsObserver uses Core~HostApp part of a loop✕
- Connections
- 1 pair of types, where a type in Core~UserDefaultsObserver uses a type in Core~HostApp.
- The types involved
Core~UserDefaultsObserver.UserDefaultsObserver→Core~HostApp.String
- Direction
- Core~UserDefaultsObserver uses Core~HostApp, so a change to Core~HostApp can break Core~UserDefaultsObserver, while a change to Core~UserDefaultsObserver can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2→31 Tool~Preferences uses Tool~FileSystem part of a loop✕
- Connections
- 2 pairs of types, where a type in Tool~Preferences uses a type in Tool~FileSystem.
- The types involved
Tool~Preferences.Digest→Tool~FileSystem.UInt8Tool~Preferences.Double→Tool~FileSystem.Date
- Direction
- Tool~Preferences uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~Preferences, while a change to Tool~Preferences can't break Tool~FileSystem.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2→33 Tool~Preferences uses Core~HostApp part of a loop✕
- Connections
- 13 pairs of types, where a type in Tool~Preferences uses a type in Core~HostApp.
- The types involved
Tool~Preferences.CodingKeys→Core~HostApp.StringTool~Preferences.CustomCommand→Core~HostApp.StringTool~Preferences.DeprecatedPreferenceKey→Core~HostApp.StringTool~Preferences.Digest→Core~HostApp.StringTool~Preferences.FeatureFlag→Core~HostApp.StringTool~Preferences.Locale→Core~HostApp.StringTool~Preferences.PreferenceKey→Core~HostApp.StringTool~Preferences.SensitiveFileRule→Core~HostApp.StringTool~Preferences.StorableFont→Core~HostApp.StringTool~Preferences.SuggestionFeatureProvider→Core~HostApp.StringTool~Preferences.UserDefaultPreferenceKey→Core~HostApp.StringTool~Preferences.UserDefaultsStorageBox→Core~HostApp.StringTool~Preferences.UserDefaultsType→Core~HostApp.String
- Direction
- Tool~Preferences uses Core~HostApp, so a change to Core~HostApp can break Tool~Preferences, while a change to Tool~Preferences can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2→38 Tool~Preferences uses Core~ConversationTab part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~Preferences uses a type in Core~ConversationTab.
- The types involved
Tool~Preferences.StorableColor→Core~ConversationTab.Color
- Direction
- Tool~Preferences uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~Preferences, while a change to Tool~Preferences can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→2 Core~LaunchAgentManager uses Tool~Preferences✕
- Connections
- 1 pair of types, where a type in Core~LaunchAgentManager uses a type in Tool~Preferences.
- The types involved
Core~LaunchAgentManager.LaunchAgentManager→Tool~Preferences.Bool
- Direction
- Core~LaunchAgentManager uses Tool~Preferences, so a change to Tool~Preferences can break Core~LaunchAgentManager, while a change to Core~LaunchAgentManager can't break Tool~Preferences.
- Position
- Below the diagonal: Core~LaunchAgentManager uses a module listed above it, which is the healthy direction.
3→30 Core~LaunchAgentManager uses Core~XcodeThemeController part of a loop✕
- Connections
- 1 pair of types, where a type in Core~LaunchAgentManager uses a type in Core~XcodeThemeController.
- The types involved
Core~LaunchAgentManager.E→Core~XcodeThemeController.Error
- Direction
- Core~LaunchAgentManager uses Core~XcodeThemeController, so a change to Core~XcodeThemeController can break Core~LaunchAgentManager, while a change to Core~LaunchAgentManager can't break Core~XcodeThemeController.
- 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→33 Core~LaunchAgentManager uses Core~HostApp part of a loop✕
- Connections
- 3 pairs of types, where a type in Core~LaunchAgentManager uses a type in Core~HostApp.
- The types involved
Core~LaunchAgentManager.E→Core~HostApp.StringCore~LaunchAgentManager.LaunchAgentManager→Core~HostApp.StringCore~LaunchAgentManager.LaunchAgentManager.swift→Core~HostApp.String
- Direction
- Core~LaunchAgentManager uses Core~HostApp, so a change to Core~HostApp can break Core~LaunchAgentManager, while a change to Core~LaunchAgentManager can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→38 Core~LaunchAgentManager uses Core~ConversationTab part of a loop✕
- Connections
- 1 pair of types, where a type in Core~LaunchAgentManager uses a type in Core~ConversationTab.
- The types involved
Core~LaunchAgentManager.LaunchAgentManager→Core~ConversationTab.URL
- Direction
- Core~LaunchAgentManager uses Core~ConversationTab, so a change to Core~ConversationTab can break Core~LaunchAgentManager, while a change to Core~LaunchAgentManager can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→2 Tool~ActiveApplicationMonitor uses Tool~Preferences✕
- Connections
- 2 pairs of types, where a type in Tool~ActiveApplicationMonitor uses a type in Tool~Preferences.
- The types involved
Tool~ActiveApplicationMonitor.RunningApplicationInfo→Tool~Preferences.BoolTool~ActiveApplicationMonitor.RunningApplicationInfo→Tool~Preferences.Int
- Direction
- 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→27 Tool~ActiveApplicationMonitor uses repository part of a loop✕
- Connections
- 2 pairs of types, where a type in Tool~ActiveApplicationMonitor uses a type in repository.
- The types involved
Tool~ActiveApplicationMonitor.ActiveApplicationMonitor→repository.NSRunningApplicationTool~ActiveApplicationMonitor.RunningApplicationInfo→repository.NSRunningApplication
- Direction
- 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→31 Tool~ActiveApplicationMonitor uses Tool~FileSystem part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~ActiveApplicationMonitor uses a type in Tool~FileSystem.
- The types involved
Tool~ActiveApplicationMonitor.RunningApplicationInfo→Tool~FileSystem.Date
- Direction
- 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→33 Tool~ActiveApplicationMonitor uses Core~HostApp part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~ActiveApplicationMonitor uses a type in Core~HostApp.
- The types involved
Tool~ActiveApplicationMonitor.RunningApplicationInfo→Core~HostApp.String
- Direction
- Tool~ActiveApplicationMonitor uses Core~HostApp, so a change to Core~HostApp can break Tool~ActiveApplicationMonitor, while a change to Tool~ActiveApplicationMonitor can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→38 Tool~ActiveApplicationMonitor uses Core~ConversationTab part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~ActiveApplicationMonitor uses a type in Core~ConversationTab.
- The types involved
Tool~ActiveApplicationMonitor.RunningApplicationInfo→Core~ConversationTab.URL
- Direction
- Tool~ActiveApplicationMonitor uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~ActiveApplicationMonitor, while a change to Tool~ActiveApplicationMonitor can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→2 Tool~GitHelper uses Tool~Preferences✕
- Connections
- 1 pair of types, where a type in Tool~GitHelper uses a type in Tool~Preferences.
- The types involved
Tool~GitHelper.GitHunk→Tool~Preferences.Int
- Direction
- Tool~GitHelper uses Tool~Preferences, so a change to Tool~Preferences can break Tool~GitHelper, while a change to Tool~GitHelper can't break Tool~Preferences.
- Position
- Below the diagonal: Tool~GitHelper uses a module listed above it, which is the healthy direction.
5→33 Tool~GitHelper uses Core~HostApp part of a loop✕
- Connections
- 7 pairs of types, where a type in Tool~GitHelper uses a type in Core~HostApp.
- The types involved
Tool~GitHelper.CurrentChangeService→Core~HostApp.StringTool~GitHelper.GitDiff→Core~HostApp.StringTool~GitHelper.GitHunk→Core~HostApp.StringTool~GitHelper.GitShow→Core~HostApp.StringTool~GitHelper.GitStatus→Core~HostApp.StringTool~GitHelper.PRChange→Core~HostApp.StringTool~GitHelper.UntrackedFilesOption→Core~HostApp.String
- Direction
- Tool~GitHelper uses Core~HostApp, so a change to Core~HostApp can break Tool~GitHelper, while a change to Tool~GitHelper can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→38 Tool~GitHelper uses Core~ConversationTab part of a loop✕
- Connections
- 5 pairs of types, where a type in Tool~GitHelper uses a type in Core~ConversationTab.
- The types involved
Tool~GitHelper.CurrentChangeService→Core~ConversationTab.URLTool~GitHelper.GitChange→Core~ConversationTab.URLTool~GitHelper.GitDiff→Core~ConversationTab.URLTool~GitHelper.GitShow→Core~ConversationTab.URLTool~GitHelper.GitStatus→Core~ConversationTab.URL
- Direction
- Tool~GitHelper uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~GitHelper, while a change to Tool~GitHelper can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→2 Tool~Logger uses Tool~Preferences✕
- Connections
- 3 pairs of types, where a type in Tool~Logger uses a type in Tool~Preferences.
- The types involved
Tool~Logger.BaseFileLoggerImplementation→Tool~Preferences.IntTool~Logger.Logger→Tool~Preferences.DoubleTool~Logger.MCPRuntimeFileLogger→Tool~Preferences.Double
- Direction
- Tool~Logger uses Tool~Preferences, so a change to Tool~Preferences can break Tool~Logger, while a change to Tool~Logger can't break Tool~Preferences.
- Position
- Below the diagonal: Tool~Logger uses a module listed above it, which is the healthy direction.
6→30 Tool~Logger uses Core~XcodeThemeController part of a loop✕
- Connections
- 2 pairs of types, where a type in Tool~Logger uses a type in Core~XcodeThemeController.
- The types involved
Tool~Logger.Logger→Core~XcodeThemeController.ErrorTool~Logger.TelemetryLoggerProvider→Core~XcodeThemeController.Error
- Direction
- Tool~Logger uses Core~XcodeThemeController, so a change to Core~XcodeThemeController can break Tool~Logger, while a change to Tool~Logger can't break Core~XcodeThemeController.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→31 Tool~Logger uses Tool~FileSystem part of a loop✕
- Connections
- 3 pairs of types, where a type in Tool~Logger uses a type in Tool~FileSystem.
- The types involved
Tool~Logger.Logger→Tool~FileSystem.StaticStringTool~Logger.Signposter→Tool~FileSystem.StaticStringTool~Logger.TelemetryLoggerProvider→Tool~FileSystem.StaticString
- Direction
- Tool~Logger uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~Logger, while a change to Tool~Logger 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.
6→33 Tool~Logger uses Core~HostApp part of a loop✕
- Connections
- 9 pairs of types, where a type in Tool~Logger uses a type in Core~HostApp.
- The types involved
Tool~Logger.BaseFileLoggerImplementation→Core~HostApp.StringTool~Logger.FileLogger→Core~HostApp.StringTool~Logger.FileLoggerImplementation→Core~HostApp.StringTool~Logger.LogLevel→Core~HostApp.StringTool~Logger.Logger→Core~HostApp.StringTool~Logger.MCPRuntimeFileLogger→Core~HostApp.StringTool~Logger.MCPRuntimeFileLoggerImplementation→Core~HostApp.StringTool~Logger.Signposter→Core~HostApp.StringTool~Logger.TelemetryLoggerProvider→Core~HostApp.String
- Direction
- Tool~Logger uses Core~HostApp, so a change to Core~HostApp can break Tool~Logger, while a change to Tool~Logger can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→2 Tool~Persist uses Tool~Preferences✕
- Connections
- 9 pairs of types, where a type in Tool~Persist uses a type in Tool~Preferences.
- The types involved
Tool~Persist.AppState→Tool~Preferences.BoolTool~Persist.AppState→Tool~Preferences.IntTool~Persist.ConfigPathUtils→Tool~Preferences.IntTool~Persist.ConversationItem→Tool~Preferences.BoolTool~Persist.ConversationPreviewItem→Tool~Preferences.BoolTool~Persist.ConversationStorage→Tool~Preferences.DoubleTool~Persist.ConversationStorageService→Tool~Preferences.BoolTool~Persist.JSONValue→Tool~Preferences.BoolTool~Persist.JSONValue→Tool~Preferences.Double
- Direction
- Tool~Persist uses Tool~Preferences, so a change to Tool~Preferences can break Tool~Persist, while a change to Tool~Persist can't break Tool~Preferences.
- Position
- Below the diagonal: Tool~Persist uses a module listed above it, which is the healthy direction.
7→21 Tool~Persist uses Tool~ConversationServiceProvider part of a loop✕
- Connections
- 2 pairs of types, where a type in Tool~Persist uses a type in Tool~ConversationServiceProvider.
- The types involved
Tool~Persist.AppState→Tool~ConversationServiceProvider.PromptTemplateScopeTool~Persist.AppState→Tool~ConversationServiceProvider.ToolStatusUpdate
- Direction
- Tool~Persist uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Tool~Persist, while a change to Tool~Persist can't break Tool~ConversationServiceProvider.
- Position
- 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→30 Tool~Persist uses Core~XcodeThemeController part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~Persist uses a type in Core~XcodeThemeController.
- The types involved
Tool~Persist.DatabaseError→Core~XcodeThemeController.Error
- Direction
- Tool~Persist uses Core~XcodeThemeController, so a change to Core~XcodeThemeController can break Tool~Persist, while a change to Tool~Persist can't break Core~XcodeThemeController.
- 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→31 Tool~Persist uses Tool~FileSystem part of a loop✕
- Connections
- 3 pairs of types, where a type in Tool~Persist uses a type in Tool~FileSystem.
- The types involved
Tool~Persist.ConversationItem→Tool~FileSystem.DateTool~Persist.ConversationPreviewItem→Tool~FileSystem.DateTool~Persist.TurnItem→Tool~FileSystem.Date
- Direction
- Tool~Persist uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~Persist, while a change to Tool~Persist 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→33 Tool~Persist uses Core~HostApp part of a loop✕
- Connections
- 12 pairs of types, where a type in Tool~Persist uses a type in Core~HostApp.
- The types involved
Tool~Persist.AppState→Core~HostApp.StringTool~Persist.Blob→Core~HostApp.StringTool~Persist.ConfigPathUtils→Core~HostApp.StringTool~Persist.ConversationItem→Core~HostApp.StringTool~Persist.ConversationPreviewItem→Core~HostApp.StringTool~Persist.ConversationStorage→Core~HostApp.StringTool~Persist.ConversationStorageProtocol→Core~HostApp.StringTool~Persist.ConversationStorageService→Core~HostApp.StringTool~Persist.ConversationStorageServiceProtocol→Core~HostApp.StringTool~Persist.JSONValue→Core~HostApp.StringTool~Persist.StorageMetadata→Core~HostApp.StringTool~Persist.TurnItem→Core~HostApp.String
- Direction
- Tool~Persist uses Core~HostApp, so a change to Core~HostApp can break Tool~Persist, while a change to Tool~Persist can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→38 Tool~Persist uses Core~ConversationTab part of a loop✕
- Connections
- 3 pairs of types, where a type in Tool~Persist uses a type in Core~ConversationTab.
- The types involved
Tool~Persist.AppState→Core~ConversationTab.LLMModelTool~Persist.AppState→Core~ConversationTab.URLTool~Persist.ConfigPathUtils→Core~ConversationTab.URL
- Direction
- Tool~Persist uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~Persist, while a change to Tool~Persist can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→2 Tool~SuggestionBasic uses Tool~Preferences✕
- Connections
- 8 pairs of types, where a type in Tool~SuggestionBasic uses a type in Tool~Preferences.
- The types involved
Tool~SuggestionBasic.CodeLanguage→Tool~Preferences.IntTool~SuggestionBasic.CodeSuggestion→Tool~Preferences.BoolTool~SuggestionBasic.CursorRange→Tool~Preferences.BoolTool~SuggestionBasic.CursorRange→Tool~Preferences.IntTool~SuggestionBasic.EditorInformation→Tool~Preferences.BoolTool~SuggestionBasic.LineAnnotation→Tool~Preferences.BoolTool~SuggestionBasic.LineAnnotation→Tool~Preferences.IntTool~SuggestionBasic.SourceEditorContent→Tool~Preferences.Int
- Direction
- 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.
8→28 Tool~SuggestionBasic uses Tool~AXExtension part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~SuggestionBasic uses a type in Tool~AXExtension.
- The types involved
Tool~SuggestionBasic.SourceEditorContent→Tool~AXExtension.AXUIElement
- Direction
- Tool~SuggestionBasic uses Tool~AXExtension, so a change to Tool~AXExtension can break Tool~SuggestionBasic, while a change to Tool~SuggestionBasic can't break Tool~AXExtension.
- Position
- 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→33 Tool~SuggestionBasic uses Core~HostApp part of a loop✕
- Connections
- 9 pairs of types, where a type in Tool~SuggestionBasic uses a type in Core~HostApp.
- The types involved
Tool~SuggestionBasic.CodeLanguage→Core~HostApp.StringTool~SuggestionBasic.CodeSuggestion→Core~HostApp.StringTool~SuggestionBasic.CodeSuggestionType→Core~HostApp.StringTool~SuggestionBasic.CursorPosition→Core~HostApp.StringTool~SuggestionBasic.CursorRange→Core~HostApp.StringTool~SuggestionBasic.EditorInformation→Core~HostApp.StringTool~SuggestionBasic.LanguageIdentifier→Core~HostApp.StringTool~SuggestionBasic.LineAnnotation→Core~HostApp.StringTool~SuggestionBasic.SourceEditorContent→Core~HostApp.String
- Direction
- Tool~SuggestionBasic uses Core~HostApp, so a change to Core~HostApp can break Tool~SuggestionBasic, while a change to Tool~SuggestionBasic can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→38 Tool~SuggestionBasic uses Core~ConversationTab part of a loop✕
- Connections
- 3 pairs of types, where a type in Tool~SuggestionBasic uses a type in Core~ConversationTab.
- The types involved
Tool~SuggestionBasic.CodeLanguage→Core~ConversationTab.URLTool~SuggestionBasic.EditorInformation→Core~ConversationTab.URLTool~SuggestionBasic.LanguageIdentifierFromFilePath.swift→Core~ConversationTab.URL
- Direction
- Tool~SuggestionBasic uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~SuggestionBasic, while a change to Tool~SuggestionBasic can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→2 Tool~TelemetryServiceProvider uses Tool~Preferences✕
- Connections
- 2 pairs of types, where a type in Tool~TelemetryServiceProvider uses a type in Tool~Preferences.
- The types involved
Tool~TelemetryServiceProvider.PositionNumberType→Tool~Preferences.IntTool~TelemetryServiceProvider.StackTraceFrame→Tool~Preferences.Bool
- Direction
- Tool~TelemetryServiceProvider uses Tool~Preferences, so a change to Tool~Preferences can break Tool~TelemetryServiceProvider, while a change to Tool~TelemetryServiceProvider can't break Tool~Preferences.
- Position
- Below the diagonal: Tool~TelemetryServiceProvider uses a module listed above it, which is the healthy direction.
9→21 Tool~TelemetryServiceProvider uses Tool~ConversationServiceProvider part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~TelemetryServiceProvider uses a type in Tool~ConversationServiceProvider.
- The types involved
Tool~TelemetryServiceProvider.TelemetryServiceType→Tool~ConversationServiceProvider.WorkspaceInfo
- Direction
- Tool~TelemetryServiceProvider uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Tool~TelemetryServiceProvider, while a change to Tool~TelemetryServiceProvider can't break Tool~ConversationServiceProvider.
- Position
- 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→33 Tool~TelemetryServiceProvider uses Core~HostApp part of a loop✕
- Connections
- 5 pairs of types, where a type in Tool~TelemetryServiceProvider uses a type in Core~HostApp.
- The types involved
Tool~TelemetryServiceProvider.CodingKeys→Core~HostApp.StringTool~TelemetryServiceProvider.ExceptionDetail→Core~HostApp.StringTool~TelemetryServiceProvider.PositionNumberType→Core~HostApp.StringTool~TelemetryServiceProvider.StackTraceFrame→Core~HostApp.StringTool~TelemetryServiceProvider.TelemetryExceptionRequest→Core~HostApp.String
- Direction
- Tool~TelemetryServiceProvider uses Core~HostApp, so a change to Core~HostApp can break Tool~TelemetryServiceProvider, while a change to Tool~TelemetryServiceProvider can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→2 Tool~Toast uses Tool~Preferences✕
- Connections
- 2 pairs of types, where a type in Tool~Toast uses a type in Tool~Preferences.
- The types involved
Tool~Toast.State→Tool~Preferences.BoolTool~Toast.ToastButton→Tool~Preferences.Bool
- Direction
- Tool~Toast uses Tool~Preferences, so a change to Tool~Preferences can break Tool~Toast, while a change to Tool~Toast can't break Tool~Preferences.
- Position
- Below the diagonal: Tool~Toast uses a module listed above it, which is the healthy direction.
10→33 Tool~Toast uses Core~HostApp part of a loop✕
- Connections
- 4 pairs of types, where a type in Tool~Toast uses a type in Core~HostApp.
- The types involved
Tool~Toast.Message→Core~HostApp.StringTool~Toast.ToastButton→Core~HostApp.StringTool~Toast.ToastController→Core~HostApp.StringTool~Toast.ToastLevel→Core~HostApp.String
- Direction
- Tool~Toast uses Core~HostApp, so a change to Core~HostApp can break Tool~Toast, while a change to Tool~Toast can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→38 Tool~Toast uses Core~ConversationTab part of a loop✕
- Connections
- 3 pairs of types, where a type in Tool~Toast uses a type in Core~ConversationTab.
- The types involved
Tool~Toast.AutoDismissMessage→Core~ConversationTab.ViewTool~Toast.NotificationView→Core~ConversationTab.ViewTool~Toast.ToastLevel→Core~ConversationTab.Color
- Direction
- Tool~Toast uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~Toast, while a change to Tool~Toast can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→2 Core~PromptToCodeService uses Tool~Preferences✕
- Connections
- 3 pairs of types, where a type in Core~PromptToCodeService uses a type in Tool~Preferences.
- The types involved
Core~PromptToCodeService.ContextAwarePromptToCodeService→Tool~Preferences.BoolCore~PromptToCodeService.PreviewPromptToCodeService→Tool~Preferences.BoolCore~PromptToCodeService.PromptToCodeServiceType→Tool~Preferences.Bool
- 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.
11→8 Core~PromptToCodeService uses Tool~SuggestionBasic✕
- Connections
- 2 pairs of types, where a type in Core~PromptToCodeService uses a type in Tool~SuggestionBasic.
- The types involved
Core~PromptToCodeService.PromptToCodeSource→Tool~SuggestionBasic.CodeLanguageCore~PromptToCodeService.PromptToCodeSource→Tool~SuggestionBasic.CursorRange
- 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.
11→33 Core~PromptToCodeService uses Core~HostApp part of a loop✕
- Connections
- 4 pairs of types, where a type in Core~PromptToCodeService uses a type in Core~HostApp.
- The types involved
Core~PromptToCodeService.ContextAwarePromptToCodeService→Core~HostApp.StringCore~PromptToCodeService.PreviewPromptToCodeService→Core~HostApp.StringCore~PromptToCodeService.PromptToCodeServiceType→Core~HostApp.StringCore~PromptToCodeService.PromptToCodeSource→Core~HostApp.String
- Direction
- Core~PromptToCodeService uses Core~HostApp, so a change to Core~HostApp can break Core~PromptToCodeService, while a change to Core~PromptToCodeService can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→38 Core~PromptToCodeService uses Core~ConversationTab part of a loop✕
- Connections
- 1 pair of types, where a type in Core~PromptToCodeService uses a type in Core~ConversationTab.
- The types involved
Core~PromptToCodeService.PromptToCodeSource→Core~ConversationTab.URL
- Direction
- Core~PromptToCodeService uses Core~ConversationTab, so a change to Core~ConversationTab can break Core~PromptToCodeService, while a change to Core~PromptToCodeService can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→2 Tool~ChatTab uses Tool~Preferences✕
- Connections
- 7 pairs of types, where a type in Tool~ChatTab uses a type in Tool~Preferences.
- The types involved
Tool~ChatTab.AnyChatTabBuilder→Tool~Preferences.BoolTool~ChatTab.BaseChatTab→Tool~Preferences.BoolTool~ChatTab.ChatTabInfo→Tool~Preferences.BoolTool~ChatTab.ChatTabInfo→Tool~Preferences.IntTool~ChatTab.ChatTabPreviewInfo→Tool~Preferences.BoolTool~ChatTab.ChatTabType→Tool~Preferences.DataTool~ChatTab.EmptyChatTab→Tool~Preferences.Data
- Direction
- 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.
12→7 Tool~ChatTab uses Tool~Persist✕
- Connections
- 3 pairs of types, where a type in Tool~ChatTab uses a type in Tool~Persist.
- The types involved
Tool~ChatTab.ChatTabInfo→Tool~Persist.ConversationItemTool~ChatTab.ChatTabInfo→Tool~Persist.StorageMetadataTool~ChatTab.ChatTabPreviewInfo→Tool~Persist.ConversationPreviewItem
- Direction
- Tool~ChatTab uses Tool~Persist, so a change to Tool~Persist can break Tool~ChatTab, while a change to Tool~ChatTab can't break Tool~Persist.
- Position
- Below the diagonal: Tool~ChatTab uses a module listed above it, which is the healthy direction.
12→29 Tool~ChatTab uses Core~SuggestionWidget part of a loop✕
- Connections
- 2 pairs of types, where a type in Tool~ChatTab uses a type in Core~SuggestionWidget.
- The types involved
Tool~ChatTab.ChatTabPool→Core~SuggestionWidget.ChatTabKindTool~ChatTab.ChatTabPool→Core~SuggestionWidget.ChatWorkspace
- Direction
- Tool~ChatTab uses Core~SuggestionWidget, so a change to Core~SuggestionWidget can break Tool~ChatTab, while a change to Tool~ChatTab can't break Core~SuggestionWidget.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→31 Tool~ChatTab uses Tool~FileSystem part of a loop✕
- Connections
- 2 pairs of types, where a type in Tool~ChatTab uses a type in Tool~FileSystem.
- The types involved
Tool~ChatTab.ChatTabInfo→Tool~FileSystem.DateTool~ChatTab.ChatTabPreviewInfo→Tool~FileSystem.Date
- Direction
- Tool~ChatTab uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~ChatTab, while a change to Tool~ChatTab 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→33 Tool~ChatTab uses Core~HostApp part of a loop✕
- Connections
- 9 pairs of types, where a type in Tool~ChatTab uses a type in Core~HostApp.
- The types involved
Tool~ChatTab.BaseChatTab→Core~HostApp.StringTool~ChatTab.Builder→Core~HostApp.StringTool~ChatTab.ChatTabBuilder→Core~HostApp.StringTool~ChatTab.ChatTabInfo→Core~HostApp.StringTool~ChatTab.ChatTabPool→Core~HostApp.StringTool~ChatTab.ChatTabPreviewInfo→Core~HostApp.StringTool~ChatTab.ChatTabType→Core~HostApp.StringTool~ChatTab.DisabledChatTabBuilder→Core~HostApp.StringTool~ChatTab.EmptyChatTab→Core~HostApp.String
- Direction
- Tool~ChatTab uses Core~HostApp, so a change to Core~HostApp can break Tool~ChatTab, while a change to Tool~ChatTab can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→38 Tool~ChatTab uses Core~ConversationTab part of a loop✕
- Connections
- 4 pairs of types, where a type in Tool~ChatTab uses a type in Core~ConversationTab.
- The types involved
Tool~ChatTab.BaseChatTab→Core~ConversationTab.ViewTool~ChatTab.ChatTabType→Core~ConversationTab.ViewTool~ChatTab.ContentView→Core~ConversationTab.ViewTool~ChatTab.EmptyChatTab→Core~ConversationTab.View
- Direction
- Tool~ChatTab uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~ChatTab, while a change to Tool~ChatTab can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→2 Tool~SuggestionProvider uses Tool~Preferences✕
- Connections
- 4 pairs of types, where a type in Tool~SuggestionProvider uses a type in Tool~Preferences.
- The types involved
Tool~SuggestionProvider.PostProcessingSuggestionServiceMiddleware→Tool~Preferences.BoolTool~SuggestionProvider.RelevantCodeSnippet→Tool~Preferences.IntTool~SuggestionProvider.SuggestionRequest→Tool~Preferences.BoolTool~SuggestionProvider.SuggestionRequest→Tool~Preferences.Int
- Direction
- 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.
13→8 Tool~SuggestionProvider uses Tool~SuggestionBasic✕
- Connections
- 7 pairs of types, where a type in Tool~SuggestionProvider uses a type in Tool~SuggestionBasic.
- The types involved
Tool~SuggestionProvider.DebugSuggestionServiceMiddleware→Tool~SuggestionBasic.CodeSuggestionTool~SuggestionProvider.DisabledLanguageSuggestionServiceMiddleware→Tool~SuggestionBasic.CodeSuggestionTool~SuggestionProvider.NESSuggestionServiceType→Tool~SuggestionBasic.CodeSuggestionTool~SuggestionProvider.PostProcessingSuggestionServiceMiddleware→Tool~SuggestionBasic.CodeSuggestionTool~SuggestionProvider.SuggestionRequest→Tool~SuggestionBasic.CursorPositionTool~SuggestionProvider.SuggestionServiceMiddleware→Tool~SuggestionBasic.CodeSuggestionTool~SuggestionProvider.SuggestionServiceProvider→Tool~SuggestionBasic.CodeSuggestion
- 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.
13→21 Tool~SuggestionProvider uses Tool~ConversationServiceProvider part of a loop✕
- Connections
- 2 pairs of types, where a type in Tool~SuggestionProvider uses a type in Tool~ConversationServiceProvider.
- The types involved
Tool~SuggestionProvider.NESSuggestionServiceType→Tool~ConversationServiceProvider.WorkspaceInfoTool~SuggestionProvider.SuggestionServiceProvider→Tool~ConversationServiceProvider.WorkspaceInfo
- Direction
- Tool~SuggestionProvider uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Tool~SuggestionProvider, while a change to Tool~SuggestionProvider can't break Tool~ConversationServiceProvider.
- Position
- 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→26 Tool~SuggestionProvider uses Tool~XPCShared part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~SuggestionProvider uses a type in Tool~XPCShared.
- The types involved
Tool~SuggestionProvider.SuggestionRequest→Tool~XPCShared.EditorContent
- Direction
- Tool~SuggestionProvider uses Tool~XPCShared, so a change to Tool~XPCShared can break Tool~SuggestionProvider, while a change to Tool~SuggestionProvider can't break Tool~XPCShared.
- Position
- 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→33 Tool~SuggestionProvider uses Core~HostApp part of a loop✕
- Connections
- 2 pairs of types, where a type in Tool~SuggestionProvider uses a type in Core~HostApp.
- The types involved
Tool~SuggestionProvider.RelevantCodeSnippet→Core~HostApp.StringTool~SuggestionProvider.SuggestionRequest→Core~HostApp.String
- Direction
- Tool~SuggestionProvider uses Core~HostApp, so a change to Core~HostApp can break Tool~SuggestionProvider, while a change to Tool~SuggestionProvider can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→38 Tool~SuggestionProvider uses Core~ConversationTab part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~SuggestionProvider uses a type in Core~ConversationTab.
- The types involved
Tool~SuggestionProvider.SuggestionRequest→Core~ConversationTab.URL
- Direction
- Tool~SuggestionProvider uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~SuggestionProvider, while a change to Tool~SuggestionProvider can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→2 Core~SuggestionService uses Tool~Preferences✕
- Connections
- 1 pair of types, where a type in Core~SuggestionService uses a type in Tool~Preferences.
- The types involved
Core~SuggestionService.SuggestionService→Tool~Preferences.SuggestionFeatureProvider
- Direction
- 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.
14→8 Core~SuggestionService uses Tool~SuggestionBasic✕
- Connections
- 1 pair of types, where a type in Core~SuggestionService uses a type in Tool~SuggestionBasic.
- The types involved
Core~SuggestionService.SuggestionService→Tool~SuggestionBasic.CodeSuggestion
- 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.
14→13 Core~SuggestionService uses Tool~SuggestionProvider✕
- Connections
- 4 pairs of types, where a type in Core~SuggestionService uses a type in Tool~SuggestionProvider.
- The types involved
Core~SuggestionService.SuggestionService→Tool~SuggestionProvider.SuggestionRequestCore~SuggestionService.SuggestionService→Tool~SuggestionProvider.SuggestionServiceMiddlewareCore~SuggestionService.SuggestionService→Tool~SuggestionProvider.SuggestionServiceProviderCore~SuggestionService.SuggestionServiceType→Tool~SuggestionProvider.SuggestionServiceProvider
- 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.
14→21 Core~SuggestionService uses Tool~ConversationServiceProvider part of a loop✕
- Connections
- 1 pair of types, where a type in Core~SuggestionService uses a type in Tool~ConversationServiceProvider.
- The types involved
Core~SuggestionService.SuggestionService→Tool~ConversationServiceProvider.WorkspaceInfo
- Direction
- Core~SuggestionService uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Core~SuggestionService, while a change to Core~SuggestionService can't break Tool~ConversationServiceProvider.
- Position
- 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→2 Tool~BuiltinExtension uses Tool~Preferences✕
- Connections
- 2 pairs of types, where a type in Tool~BuiltinExtension uses a type in Tool~Preferences.
- The types involved
Tool~BuiltinExtension.BuiltinExtension→Tool~Preferences.BuiltInSuggestionFeatureProviderTool~BuiltinExtension.BuiltinExtensionConversationServiceProvider→Tool~Preferences.Int
- Direction
- 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.
15→8 Tool~BuiltinExtension uses Tool~SuggestionBasic✕
- Connections
- 1 pair of types, where a type in Tool~BuiltinExtension uses a type in Tool~SuggestionBasic.
- The types involved
Tool~BuiltinExtension.BuiltinExtensionSuggestionServiceProvider→Tool~SuggestionBasic.CodeSuggestion
- 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.
15→9 Tool~BuiltinExtension uses Tool~TelemetryServiceProvider✕
- Connections
- 4 pairs of types, where a type in Tool~BuiltinExtension uses a type in Tool~TelemetryServiceProvider.
- The types involved
Tool~BuiltinExtension.BuiltinExtensionTelemetryServiceProvider→Tool~TelemetryServiceProvider.TelemetryExceptionRequestTool~BuiltinExtension.BuiltinExtensionTelemetryServiceProvider→Tool~TelemetryServiceProvider.TelemetryServiceProviderTool~BuiltinExtension.BuiltinExtensionTelemetryServiceProvider→Tool~TelemetryServiceProvider.TelemetryServiceTypeTool~BuiltinExtension.CopilotForXcodeTelemetryCapability→Tool~TelemetryServiceProvider.TelemetryServiceType
- Direction
- Tool~BuiltinExtension uses Tool~TelemetryServiceProvider, so a change to Tool~TelemetryServiceProvider can break Tool~BuiltinExtension, while a change to Tool~BuiltinExtension can't break Tool~TelemetryServiceProvider.
- Position
- Below the diagonal: Tool~BuiltinExtension uses a module listed above it, which is the healthy direction.
15→13 Tool~BuiltinExtension uses Tool~SuggestionProvider✕
- Connections
- 2 pairs of types, where a type in Tool~BuiltinExtension uses a type in Tool~SuggestionProvider.
- The types involved
Tool~BuiltinExtension.BuiltinExtensionSuggestionServiceProvider→Tool~SuggestionProvider.SuggestionRequestTool~BuiltinExtension.BuiltinExtensionSuggestionServiceProvider→Tool~SuggestionProvider.SuggestionServiceProvider
- 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.
15→21 Tool~BuiltinExtension uses Tool~ConversationServiceProvider part of a loop✕
- Connections
- 20 pairs of types, where a type in Tool~BuiltinExtension uses a type in Tool~ConversationServiceProvider.
- The types involved
Tool~BuiltinExtension.BuiltinExtensionConversationServiceProvider→Tool~ConversationServiceProvider.ChangeTool~BuiltinExtension.BuiltinExtensionConversationServiceProvider→Tool~ConversationServiceProvider.ChatAgentTool~BuiltinExtension.BuiltinExtensionConversationServiceProvider→Tool~ConversationServiceProvider.ChatTemplateTool~BuiltinExtension.BuiltinExtensionConversationServiceProvider→Tool~ConversationServiceProvider.CodeReviewResultTool~BuiltinExtension.BuiltinExtensionConversationServiceProvider→Tool~ConversationServiceProvider.ConversationCreateResponseTool~BuiltinExtension.BuiltinExtensionConversationServiceProvider→Tool~ConversationServiceProvider.ConversationModeTool~BuiltinExtension.BuiltinExtensionConversationServiceProvider→Tool~ConversationServiceProvider.ConversationRatingTool~BuiltinExtension.BuiltinExtensionConversationServiceProvider→Tool~ConversationServiceProvider.ConversationRequestTool~BuiltinExtension.BuiltinExtensionConversationServiceProvider→Tool~ConversationServiceProvider.ConversationServiceProviderTool~BuiltinExtension.BuiltinExtensionConversationServiceProvider→Tool~ConversationServiceProvider.ConversationServiceTypeTool~BuiltinExtension.BuiltinExtensionConversationServiceProvider→Tool~ConversationServiceProvider.CopilotModelTool~BuiltinExtension.BuiltinExtensionConversationServiceProvider→Tool~ConversationServiceProvider.CopyCodeRequestTool~BuiltinExtension.BuiltinExtensionConversationServiceProvider→Tool~ConversationServiceProvider.DidChangeWatchedFilesEventTool~BuiltinExtension.BuiltinExtensionConversationServiceProvider→Tool~ConversationServiceProvider.GenerateThinkingTitleParamsTool~BuiltinExtension.BuiltinExtensionConversationServiceProvider→Tool~ConversationServiceProvider.GenerateThinkingTitleResponseTool~BuiltinExtension.BuiltinExtensionConversationServiceProvider→Tool~ConversationServiceProvider.WorkspaceInfoTool~BuiltinExtension.BuiltinExtensionSuggestionServiceProvider→Tool~ConversationServiceProvider.WorkspaceInfoTool~BuiltinExtension.BuiltinExtensionTelemetryServiceProvider→Tool~ConversationServiceProvider.WorkspaceInfoTool~BuiltinExtension.CopilotForXcodeChatCapability→Tool~ConversationServiceProvider.ConversationServiceTypeTool~BuiltinExtension.CopilotForXcodeExtensionCapability→Tool~ConversationServiceProvider.WorkspaceInfo
- Direction
- Tool~BuiltinExtension uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Tool~BuiltinExtension, while a change to Tool~BuiltinExtension can't break Tool~ConversationServiceProvider.
- Position
- 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 Tool~BuiltinExtension uses Tool~Workspace part of a loop✕
- Connections
- 3 pairs of types, where a type in Tool~BuiltinExtension uses a type in Tool~Workspace.
- The types involved
Tool~BuiltinExtension.BuiltinExtensionWorkspacePlugin→Tool~Workspace.FilespaceTool~BuiltinExtension.BuiltinExtensionWorkspacePlugin→Tool~Workspace.WorkspaceTool~BuiltinExtension.BuiltinExtensionWorkspacePlugin→Tool~Workspace.WorkspacePlugin
- 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
- 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→30 Tool~BuiltinExtension uses Core~XcodeThemeController part of a loop✕
- Connections
- 4 pairs of types, where a type in Tool~BuiltinExtension uses a type in Core~XcodeThemeController.
- The types involved
Tool~BuiltinExtension.BuiltinExtensionActiveWorkspaceInfoNotFoundError→Core~XcodeThemeController.ErrorTool~BuiltinExtension.BuiltinExtensionChatServiceNotFoundError→Core~XcodeThemeController.ErrorTool~BuiltinExtension.BuiltinExtensionSuggestionServiceNotFoundError→Core~XcodeThemeController.ErrorTool~BuiltinExtension.BuiltinExtensionTelemetryServiceNotFoundError→Core~XcodeThemeController.Error
- Direction
- Tool~BuiltinExtension uses Core~XcodeThemeController, so a change to Core~XcodeThemeController can break Tool~BuiltinExtension, while a change to Tool~BuiltinExtension can't break Core~XcodeThemeController.
- 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→33 Tool~BuiltinExtension uses Core~HostApp part of a loop✕
- Connections
- 7 pairs of types, where a type in Tool~BuiltinExtension uses a type in Core~HostApp.
- The types involved
Tool~BuiltinExtension.BuiltinExtensionActiveWorkspaceInfoNotFoundError→Core~HostApp.StringTool~BuiltinExtension.BuiltinExtensionChatServiceNotFoundError→Core~HostApp.StringTool~BuiltinExtension.BuiltinExtensionConversationServiceProvider→Core~HostApp.StringTool~BuiltinExtension.BuiltinExtensionSuggestionServiceNotFoundError→Core~HostApp.StringTool~BuiltinExtension.BuiltinExtensionTelemetryServiceNotFoundError→Core~HostApp.StringTool~BuiltinExtension.BuiltinExtensionWorkspacePlugin→Core~HostApp.StringTool~BuiltinExtension.CopilotForXcodeExtensionCapability→Core~HostApp.String
- Direction
- Tool~BuiltinExtension uses Core~HostApp, so a change to Core~HostApp can break Tool~BuiltinExtension, while a change to Tool~BuiltinExtension can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→38 Tool~BuiltinExtension uses Core~ConversationTab part of a loop✕
- Connections
- 3 pairs of types, where a type in Tool~BuiltinExtension uses a type in Core~ConversationTab.
- The types involved
Tool~BuiltinExtension.BuiltinExtensionConversationServiceProvider→Core~ConversationTab.URLTool~BuiltinExtension.BuiltinExtensionWorkspacePlugin→Core~ConversationTab.URLTool~BuiltinExtension.CopilotForXcodeExtensionCapability→Core~ConversationTab.URL
- Direction
- Tool~BuiltinExtension uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~BuiltinExtension, while a change to Tool~BuiltinExtension can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→1 Tool~WorkspaceSuggestionService uses Core~UserDefaultsObserver✕
- Connections
- 1 pair of types, where a type in Tool~WorkspaceSuggestionService uses a type in Core~UserDefaultsObserver.
- The types involved
Tool~WorkspaceSuggestionService.SuggestionServiceWorkspacePlugin→Core~UserDefaultsObserver.UserDefaultsObserver
- Direction
- Tool~WorkspaceSuggestionService uses Core~UserDefaultsObserver, so a change to Core~UserDefaultsObserver can break Tool~WorkspaceSuggestionService, while a change to Tool~WorkspaceSuggestionService can't break Core~UserDefaultsObserver.
- Position
- Below the diagonal: Tool~WorkspaceSuggestionService uses a module listed above it, which is the healthy direction.
16→2 Tool~WorkspaceSuggestionService uses Tool~Preferences✕
- Connections
- 3 pairs of types, where a type in Tool~WorkspaceSuggestionService uses a type in Tool~Preferences.
- The types involved
Tool~WorkspaceSuggestionService.FilespaceSuggestionSnapshot→Tool~Preferences.BoolTool~WorkspaceSuggestionService.FilespaceSuggestionSnapshot→Tool~Preferences.IntTool~WorkspaceSuggestionService.SuggestionServiceWorkspacePlugin→Tool~Preferences.Bool
- Direction
- Tool~WorkspaceSuggestionService uses Tool~Preferences, so a change to Tool~Preferences can break Tool~WorkspaceSuggestionService, while a change to Tool~WorkspaceSuggestionService can't break Tool~Preferences.
- Position
- Below the diagonal: Tool~WorkspaceSuggestionService uses a module listed above it, which is the healthy direction.
16→8 Tool~WorkspaceSuggestionService uses Tool~SuggestionBasic✕
- Connections
- 4 pairs of types, where a type in Tool~WorkspaceSuggestionService uses a type in Tool~SuggestionBasic.
- The types involved
Tool~WorkspaceSuggestionService.FilespaceSuggestionSnapshot→Tool~SuggestionBasic.CursorPositionTool~WorkspaceSuggestionService.LineEdit→Tool~SuggestionBasic.CodeSuggestionTool~WorkspaceSuggestionService.LineEdit→Tool~SuggestionBasic.CursorPositionTool~WorkspaceSuggestionService.SuggestionServiceWorkspacePlugin→Tool~SuggestionBasic.CodeSuggestion
- 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.
16→13 Tool~WorkspaceSuggestionService uses Tool~SuggestionProvider✕
- Connections
- 1 pair of types, where a type in Tool~WorkspaceSuggestionService uses a type in Tool~SuggestionProvider.
- The types involved
Tool~WorkspaceSuggestionService.SuggestionServiceWorkspacePlugin→Tool~SuggestionProvider.SuggestionServiceProvider
- 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.
16→23 Tool~WorkspaceSuggestionService uses Tool~Workspace part of a loop✕
- Connections
- 4 pairs of types, where a type in Tool~WorkspaceSuggestionService uses a type in Tool~Workspace.
- The types involved
Tool~WorkspaceSuggestionService.FilespaceNESSuggestionSnapshotKey→Tool~Workspace.FilespacePropertyKeyTool~WorkspaceSuggestionService.FilespaceSuggestionSnapshotKey→Tool~Workspace.FilespacePropertyKeyTool~WorkspaceSuggestionService.SuggestionServiceWorkspacePlugin→Tool~Workspace.WorkspaceTool~WorkspaceSuggestionService.SuggestionServiceWorkspacePlugin→Tool~Workspace.WorkspacePlugin
- Direction
- 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.
16→26 Tool~WorkspaceSuggestionService uses Tool~XPCShared part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~WorkspaceSuggestionService uses a type in Tool~XPCShared.
- The types involved
Tool~WorkspaceSuggestionService.FilespaceSuggestionSnapshot→Tool~XPCShared.EditorContent
- Direction
- Tool~WorkspaceSuggestionService uses Tool~XPCShared, so a change to Tool~XPCShared can break Tool~WorkspaceSuggestionService, while a change to Tool~WorkspaceSuggestionService can't break Tool~XPCShared.
- Position
- 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→33 Tool~WorkspaceSuggestionService uses Core~HostApp part of a loop✕
- Connections
- 2 pairs of types, where a type in Tool~WorkspaceSuggestionService uses a type in Core~HostApp.
- The types involved
Tool~WorkspaceSuggestionService.FilespaceSuggestionSnapshot→Core~HostApp.StringTool~WorkspaceSuggestionService.LineEdit→Core~HostApp.String
- Direction
- Tool~WorkspaceSuggestionService uses Core~HostApp, so a change to Core~HostApp can break Tool~WorkspaceSuggestionService, while a change to Tool~WorkspaceSuggestionService can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→2 Tool~GitHubCopilotService uses Tool~Preferences✕
- Connections
- 69 pairs of types, where a type in Tool~GitHubCopilotService uses a type in Tool~Preferences. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Tool~GitHubCopilotService.AnyCodingKey→Tool~Preferences.IntTool~GitHubCopilotService.BYOKListModelsParams→Tool~Preferences.BoolTool~GitHubCopilotService.BYOKModelCapabilities→Tool~Preferences.BoolTool~GitHubCopilotService.BYOKModelCapabilities→Tool~Preferences.IntTool~GitHubCopilotService.BYOKModelInfo→Tool~Preferences.BoolTool~GitHubCopilotService.BYOKModelManager→Tool~Preferences.BoolTool~GitHubCopilotService.BYOKProviderName→Tool~Preferences.BoolTool~GitHubCopilotService.BYOKSaveModelResponse→Tool~Preferences.BoolTool~GitHubCopilotService.CLSErrorCode→Tool~Preferences.IntTool~GitHubCopilotService.CLSErrorInfo→Tool~Preferences.BoolTool~GitHubCopilotService.CLSErrorInfo→Tool~Preferences.IntTool~GitHubCopilotService.CompressionCompletedNotification→Tool~Preferences.IntTool~GitHubCopilotService.CompressionStartedNotification→Tool~Preferences.IntTool~GitHubCopilotService.CopilotLanguageModelToolManager→Tool~Preferences.BoolTool~GitHubCopilotService.CopilotLocalProcessServer→Tool~Preferences.BoolTool~GitHubCopilotService.CopilotLocalProcessServer→Tool~Preferences.DataTool~GitHubCopilotService.CopilotMCPToolManager→Tool~Preferences.BoolTool~GitHubCopilotService.CopilotModelManager→Tool~Preferences.BoolTool~GitHubCopilotService.CopilotPolicy→Tool~Preferences.BoolTool~GitHubCopilotService.CopyCodeParams→Tool~Preferences.IntTool~GitHubCopilotService.CustomJSONRPCServerConnection→Tool~Preferences.DataTool~GitHubCopilotService.DidChangeFeatureFlagsParams→Tool~Preferences.BoolTool~GitHubCopilotService.DynamicOAuthInput→Tool~Preferences.BoolTool~GitHubCopilotService.DynamicOAuthRequestHandlerImpl→Tool~Preferences.BoolTool~GitHubCopilotService.FeatureFlags→Tool~Preferences.Bool
- 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.
17→3 Tool~GitHubCopilotService uses Core~LaunchAgentManager✕
- Connections
- 3 pairs of types, where a type in Tool~GitHubCopilotService uses a type in Core~LaunchAgentManager.
- The types involved
Tool~GitHubCopilotService.GitHubCopilotLSP→Core~LaunchAgentManager.ETool~GitHubCopilotService.GitHubCopilotService→Core~LaunchAgentManager.ETool~GitHubCopilotService.SafeInitializingServer→Core~LaunchAgentManager.E
- Direction
- Tool~GitHubCopilotService uses Core~LaunchAgentManager, so a change to Core~LaunchAgentManager can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Core~LaunchAgentManager.
- Position
- Below the diagonal: Tool~GitHubCopilotService uses a module listed above it, which is the healthy direction.
17→7 Tool~GitHubCopilotService uses Tool~Persist✕
- Connections
- 9 pairs of types, where a type in Tool~GitHubCopilotService uses a type in Tool~Persist.
- The types involved
Tool~GitHubCopilotService.CompressionCompletedNotification→Tool~Persist.JSONValueTool~GitHubCopilotService.CompressionStartedNotification→Tool~Persist.JSONValueTool~GitHubCopilotService.CopilotLocalProcessServer.swift→Tool~Persist.JSONValueTool~GitHubCopilotService.CopilotProgressParams→Tool~Persist.JSONValueTool~GitHubCopilotService.GetAllToolsParams→Tool~Persist.JSONValueTool~GitHubCopilotService.GitHubCopilotRequest.swift→Tool~Persist.JSONValueTool~GitHubCopilotService.GitHubCopilotService→Tool~Persist.JSONValueTool~GitHubCopilotService.MCPRuntimeNotification→Tool~Persist.JSONValueTool~GitHubCopilotService.StatusNotification→Tool~Persist.JSONValue
- Direction
- Tool~GitHubCopilotService uses Tool~Persist, so a change to Tool~Persist can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Tool~Persist.
- Position
- Below the diagonal: Tool~GitHubCopilotService uses a module listed above it, which is the healthy direction.
17→8 Tool~GitHubCopilotService uses Tool~SuggestionBasic✕
- Connections
- 9 pairs of types, where a type in Tool~GitHubCopilotService uses a type in Tool~SuggestionBasic.
- The types involved
Tool~GitHubCopilotService.CopilotInlineEditsParams→Tool~SuggestionBasic.CursorPositionTool~GitHubCopilotService.GitHubCopilotCodeSuggestion→Tool~SuggestionBasic.CursorPositionTool~GitHubCopilotService.GitHubCopilotCodeSuggestion→Tool~SuggestionBasic.CursorRangeTool~GitHubCopilotService.GitHubCopilotDoc→Tool~SuggestionBasic.CodeLanguageTool~GitHubCopilotService.GitHubCopilotService→Tool~SuggestionBasic.CodeSuggestionTool~GitHubCopilotService.GitHubCopilotService→Tool~SuggestionBasic.CursorPositionTool~GitHubCopilotService.GitHubCopilotSuggestionService→Tool~SuggestionBasic.CodeSuggestionTool~GitHubCopilotService.GitHubCopilotSuggestionServiceType→Tool~SuggestionBasic.CodeSuggestionTool~GitHubCopilotService.GitHubCopilotSuggestionServiceType→Tool~SuggestionBasic.CursorPosition
- 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.
17→9 Tool~GitHubCopilotService uses Tool~TelemetryServiceProvider✕
- Connections
- 6 pairs of types, where a type in Tool~GitHubCopilotService uses a type in Tool~TelemetryServiceProvider.
- The types involved
Tool~GitHubCopilotService.GitHubCopilotExtension→Tool~TelemetryServiceProvider.TelemetryServiceTypeTool~GitHubCopilotService.GitHubCopilotService→Tool~TelemetryServiceProvider.ExceptionDetailTool~GitHubCopilotService.GitHubCopilotTelemetryService→Tool~TelemetryServiceProvider.TelemetryExceptionRequestTool~GitHubCopilotService.GitHubCopilotTelemetryService→Tool~TelemetryServiceProvider.TelemetryServiceTypeTool~GitHubCopilotService.GitHubCopilotTelemetryServiceType→Tool~TelemetryServiceProvider.ExceptionDetailTool~GitHubCopilotService.TelemetryExceptionParams→Tool~TelemetryServiceProvider.ExceptionDetail
- Direction
- Tool~GitHubCopilotService uses Tool~TelemetryServiceProvider, so a change to Tool~TelemetryServiceProvider can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Tool~TelemetryServiceProvider.
- Position
- Below the diagonal: Tool~GitHubCopilotService uses a module listed above it, which is the healthy direction.
17→13 Tool~GitHubCopilotService uses Tool~SuggestionProvider✕
- Connections
- 2 pairs of types, where a type in Tool~GitHubCopilotService uses a type in Tool~SuggestionProvider.
- The types involved
Tool~GitHubCopilotService.GitHubCopilotSuggestionService→Tool~SuggestionProvider.NESSuggestionServiceTypeTool~GitHubCopilotService.GitHubCopilotSuggestionService→Tool~SuggestionProvider.SuggestionRequest
- 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.
17→14 Tool~GitHubCopilotService uses Core~SuggestionService✕
- Connections
- 1 pair of types, where a type in Tool~GitHubCopilotService uses a type in Core~SuggestionService.
- The types involved
Tool~GitHubCopilotService.GitHubCopilotSuggestionService→Core~SuggestionService.SuggestionServiceType
- 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.
17→15 Tool~GitHubCopilotService uses Tool~BuiltinExtension✕
- Connections
- 1 pair of types, where a type in Tool~GitHubCopilotService uses a type in Tool~BuiltinExtension.
- The types involved
Tool~GitHubCopilotService.GitHubCopilotExtension→Tool~BuiltinExtension.BuiltinExtension
- 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.
17→18 Tool~GitHubCopilotService uses Tool~Status part of a loop✕
- Connections
- 4 pairs of types, where a type in Tool~GitHubCopilotService uses a type in Tool~Status.
- The types involved
Tool~GitHubCopilotService.GitHubCopilotAuthServiceType→Tool~Status.GitHubCopilotQuotaInfoTool~GitHubCopilotService.GitHubCopilotService→Tool~Status.GitHubCopilotQuotaInfoTool~GitHubCopilotService.MCPRegistryServerDetail→Tool~Status.IconTool~GitHubCopilotService.QuotaNotifierImpl→Tool~Status.GitHubCopilotQuotaInfo
- Direction
- Tool~GitHubCopilotService uses Tool~Status, so a change to Tool~Status can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Tool~Status.
- Position
- 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→20 Tool~GitHubCopilotService uses Tool~ChatAPIService part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~GitHubCopilotService uses a type in Tool~ChatAPIService.
- The types involved
Tool~GitHubCopilotService.StatusKind→Tool~ChatAPIService.Status
- Direction
- Tool~GitHubCopilotService uses Tool~ChatAPIService, so a change to Tool~ChatAPIService can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Tool~ChatAPIService.
- 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→21 Tool~GitHubCopilotService uses Tool~ConversationServiceProvider part of a loop✕
- Connections
- 90 pairs of types, where a type in Tool~GitHubCopilotService uses a type in Tool~ConversationServiceProvider. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Tool~GitHubCopilotService.BYOKModelManager→Tool~ConversationServiceProvider.PromptTemplateScopeTool~GitHubCopilotService.ClientToolRegistry.swift→Tool~ConversationServiceProvider.LanguageModelToolTool~GitHubCopilotService.CompressionCompletedNotification→Tool~ConversationServiceProvider.ContextSizeInfoTool~GitHubCopilotService.ConversationProgressEnd→Tool~ConversationServiceProvider.ConversationFollowUpTool~GitHubCopilotService.ConversationProgressEnd→Tool~ConversationServiceProvider.CopilotLanguageServerErrorTool~GitHubCopilotService.ConversationProgressReport→Tool~ConversationServiceProvider.AgentRoundTool~GitHubCopilotService.ConversationProgressReport→Tool~ConversationServiceProvider.ContextSizeInfoTool~GitHubCopilotService.ConversationProgressReport→Tool~ConversationServiceProvider.ConversationProgressStepTool~GitHubCopilotService.ConversationProgressReport→Tool~ConversationServiceProvider.FileReferenceTool~GitHubCopilotService.ConversationProgressReport→Tool~ConversationServiceProvider.ThinkingTool~GitHubCopilotService.ConversationRatingParams→Tool~ConversationServiceProvider.ConversationRatingTool~GitHubCopilotService.ConversationRatingParams→Tool~ConversationServiceProvider.ConversationSourceTool~GitHubCopilotService.ConversationRatingParams→Tool~ConversationServiceProvider.DocTool~GitHubCopilotService.CopilotLanguageModelToolManager→Tool~ConversationServiceProvider.LanguageModelToolTool~GitHubCopilotService.CopilotModelManager→Tool~ConversationServiceProvider.CopilotModelTool~GitHubCopilotService.CopilotModelManager→Tool~ConversationServiceProvider.PromptTemplateScopeTool~GitHubCopilotService.CopyCodeParams→Tool~ConversationServiceProvider.ConversationSourceTool~GitHubCopilotService.CopyCodeParams→Tool~ConversationServiceProvider.CopyKindTool~GitHubCopilotService.CopyCodeParams→Tool~ConversationServiceProvider.DocTool~GitHubCopilotService.CreateConversation→Tool~ConversationServiceProvider.ConversationCreateParamsTool~GitHubCopilotService.GenerateThinkingTitle→Tool~ConversationServiceProvider.GenerateThinkingTitleParamsTool~GitHubCopilotService.GitHubCopilotConversationService→Tool~ConversationServiceProvider.ChangeTool~GitHubCopilotService.GitHubCopilotConversationService→Tool~ConversationServiceProvider.ChatAgentTool~GitHubCopilotService.GitHubCopilotConversationService→Tool~ConversationServiceProvider.ChatTemplateTool~GitHubCopilotService.GitHubCopilotConversationService→Tool~ConversationServiceProvider.CodeReviewResult
- Direction
- Tool~GitHubCopilotService uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Tool~ConversationServiceProvider.
- Position
- 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~GitHubCopilotService uses Tool~Workspace part of a loop✕
- Connections
- 4 pairs of types, where a type in Tool~GitHubCopilotService uses a type in Tool~Workspace.
- The types involved
Tool~GitHubCopilotService.GitHubCopilotExtension→Tool~Workspace.WorkspacePoolTool~GitHubCopilotService.GitHubCopilotWorkspacePlugin→Tool~Workspace.WorkspaceTool~GitHubCopilotService.GitHubCopilotWorkspacePlugin→Tool~Workspace.WorkspacePluginTool~GitHubCopilotService.ServiceLocator→Tool~Workspace.WorkspacePool
- 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
- 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→25 Tool~GitHubCopilotService uses Core~Service part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~GitHubCopilotService uses a type in Core~Service.
- The types involved
Tool~GitHubCopilotService.GitHubCopilotSuggestionActor→Core~Service.TheActor
- Direction
- Tool~GitHubCopilotService uses Core~Service, so a change to Core~Service can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Core~Service.
- 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→27 Tool~GitHubCopilotService uses repository part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~GitHubCopilotService uses a type in repository.
- The types involved
Tool~GitHubCopilotService.SafeInitializingServer→repository.Task
- Direction
- Tool~GitHubCopilotService uses repository, so a change to repository can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break repository.
- Position
- 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→30 Tool~GitHubCopilotService uses Core~XcodeThemeController part of a loop✕
- Connections
- 3 pairs of types, where a type in Tool~GitHubCopilotService uses a type in Core~XcodeThemeController.
- The types involved
Tool~GitHubCopilotService.GitHubCopilotError→Core~XcodeThemeController.ErrorTool~GitHubCopilotService.ServerError→Core~XcodeThemeController.ErrorTool~GitHubCopilotService.ServerRequestHandlerImpl→Core~XcodeThemeController.Error
- Direction
- Tool~GitHubCopilotService uses Core~XcodeThemeController, so a change to Core~XcodeThemeController can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Core~XcodeThemeController.
- 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→33 Tool~GitHubCopilotService uses Core~HostApp part of a loop✕
- Connections
- 113 pairs of types, where a type in Tool~GitHubCopilotService uses a type in Core~HostApp. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Tool~GitHubCopilotService.AnyCodingKey→Core~HostApp.StringTool~GitHubCopilotService.ArgumentFormat→Core~HostApp.StringTool~GitHubCopilotService.ArgumentType→Core~HostApp.StringTool~GitHubCopilotService.BYOKApiKeyInfo→Core~HostApp.StringTool~GitHubCopilotService.BYOKDeleteModelParams→Core~HostApp.StringTool~GitHubCopilotService.BYOKListApiKeysParams→Core~HostApp.StringTool~GitHubCopilotService.BYOKModelCapabilities→Core~HostApp.StringTool~GitHubCopilotService.BYOKModelInfo→Core~HostApp.StringTool~GitHubCopilotService.BYOKProviderName→Core~HostApp.BYOKAuthTypeTool~GitHubCopilotService.BYOKProviderName→Core~HostApp.StringTool~GitHubCopilotService.BYOKSaveApiKeyParams→Core~HostApp.StringTool~GitHubCopilotService.BYOKSaveModelResponse→Core~HostApp.StringTool~GitHubCopilotService.BaseConversationProgress→Core~HostApp.StringTool~GitHubCopilotService.CLSErrorInfo→Core~HostApp.StringTool~GitHubCopilotService.CodingKeys→Core~HostApp.StringTool~GitHubCopilotService.Command→Core~HostApp.StringTool~GitHubCopilotService.CompressionCompletedNotification→Core~HostApp.StringTool~GitHubCopilotService.CompressionStartedNotification→Core~HostApp.StringTool~GitHubCopilotService.CompressionTrigger→Core~HostApp.StringTool~GitHubCopilotService.ConversationContextParams→Core~HostApp.StringTool~GitHubCopilotService.ConversationProgressBegin→Core~HostApp.StringTool~GitHubCopilotService.ConversationProgressEnd→Core~HostApp.StringTool~GitHubCopilotService.ConversationProgressHandlerImpl→Core~HostApp.StringTool~GitHubCopilotService.ConversationProgressKind→Core~HostApp.StringTool~GitHubCopilotService.ConversationProgressReport→Core~HostApp.String
- Direction
- Tool~GitHubCopilotService uses Core~HostApp, so a change to Core~HostApp can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→38 Tool~GitHubCopilotService uses Core~ConversationTab part of a loop✕
- Connections
- 12 pairs of types, where a type in Tool~GitHubCopilotService uses a type in Core~ConversationTab.
- The types involved
Tool~GitHubCopilotService.BYOKModelManager→Core~ConversationTab.LLMModelTool~GitHubCopilotService.CopilotModelManager→Core~ConversationTab.LLMModelTool~GitHubCopilotService.GitHubCopilotBaseService→Core~ConversationTab.URLTool~GitHubCopilotService.GitHubCopilotConversationService→Core~ConversationTab.URLTool~GitHubCopilotService.GitHubCopilotExtension→Core~ConversationTab.URLTool~GitHubCopilotService.GitHubCopilotService→Core~ConversationTab.URLTool~GitHubCopilotService.GitHubCopilotSuggestionServiceType→Core~ConversationTab.URLTool~GitHubCopilotService.ServerRequestHandler→Core~ConversationTab.URLTool~GitHubCopilotService.ServerRequestHandlerImpl→Core~ConversationTab.URLTool~GitHubCopilotService.WarningAction→Core~ConversationTab.URLTool~GitHubCopilotService.WatchedFilesHandler→Core~ConversationTab.URLTool~GitHubCopilotService.WatchedFilesHandlerImpl→Core~ConversationTab.URL
- Direction
- Tool~GitHubCopilotService uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~GitHubCopilotService, while a change to Tool~GitHubCopilotService can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→2 Tool~Status uses Tool~Preferences✕
- Connections
- 8 pairs of types, where a type in Tool~Status uses a type in Tool~Preferences.
- The types involved
Tool~Status.CLSStatus→Tool~Preferences.BoolTool~Status.ExtensionPermissionStatus→Tool~Preferences.IntTool~Status.GitHubCopilotQuotaInfo→Tool~Preferences.BoolTool~Status.ObservedAXStatus→Tool~Preferences.IntTool~Status.QuotaSnapshot→Tool~Preferences.BoolTool~Status.QuotaSnapshot→Tool~Preferences.DoubleTool~Status.Status→Tool~Preferences.BoolTool~Status.StatusResponse→Tool~Preferences.Bool
- Direction
- Tool~Status uses Tool~Preferences, so a change to Tool~Preferences can break Tool~Status, while a change to Tool~Status can't break Tool~Preferences.
- Position
- Below the diagonal: Tool~Status uses a module listed above it, which is the healthy direction.
18→17 Tool~Status uses Tool~GitHubCopilotService✕
- Connections
- 1 pair of types, where a type in Tool~Status uses a type in Tool~GitHubCopilotService.
- The types involved
Tool~Status.QuotaSnapshot→Tool~GitHubCopilotService.QuotaSnapshotNotificationParams
- Direction
- Tool~Status uses Tool~GitHubCopilotService, so a change to Tool~GitHubCopilotService can break Tool~Status, while a change to Tool~Status can't break Tool~GitHubCopilotService.
- Position
- Below the diagonal: Tool~Status uses a module listed above it, which is the healthy direction.
18→20 Tool~Status uses Tool~ChatAPIService part of a loop✕
- Connections
- 5 pairs of types, where a type in Tool~Status uses a type in Tool~ChatAPIService.
- The types involved
Tool~Status.AuthStatus→Tool~ChatAPIService.StatusTool~Status.AuthStatusInfo→Tool~ChatAPIService.StatusTool~Status.CLSStatus→Tool~ChatAPIService.StatusTool~Status.Status→Tool~ChatAPIService.StatusTool~Status.StatusResponse→Tool~ChatAPIService.Status
- Direction
- Tool~Status uses Tool~ChatAPIService, so a change to Tool~ChatAPIService can break Tool~Status, while a change to Tool~Status can't break Tool~ChatAPIService.
- 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→31 Tool~Status uses Tool~FileSystem part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~Status uses a type in Tool~FileSystem.
- The types involved
Tool~Status.QuotaFormatting→Tool~FileSystem.Date
- Direction
- Tool~Status uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~Status, while a change to Tool~Status 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.
18→33 Tool~Status uses Core~HostApp part of a loop✕
- Connections
- 11 pairs of types, where a type in Tool~Status uses a type in Core~HostApp.
- The types involved
Tool~Status.AccessibilityStatusInfo→Core~HostApp.StringTool~Status.AuthStatus→Core~HostApp.StringTool~Status.AuthStatusInfo→Core~HostApp.StringTool~Status.CLSStatus→Core~HostApp.StringTool~Status.CLSStatusInfo→Core~HostApp.StringTool~Status.GitHubCopilotQuotaInfo→Core~HostApp.StringTool~Status.Icon→Core~HostApp.StringTool~Status.QuotaFormatting→Core~HostApp.StringTool~Status.QuotaSnapshot→Core~HostApp.StringTool~Status.Status→Core~HostApp.StringTool~Status.StatusResponse→Core~HostApp.String
- Direction
- Tool~Status uses Core~HostApp, so a change to Core~HostApp can break Tool~Status, while a change to Tool~Status can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→2 Tool~XcodeInspector uses Tool~Preferences✕
- Connections
- 6 pairs of types, where a type in Tool~XcodeInspector uses a type in Tool~Preferences.
- The types involved
Tool~XcodeInspector.AppInstanceInspector→Tool~Preferences.BoolTool~XcodeInspector.DisabledLanguageList→Tool~Preferences.BoolTool~XcodeInspector.FileManager→Tool~Preferences.BoolTool~XcodeInspector.SourceEditor→Tool~Preferences.BoolTool~XcodeInspector.XcodeAppInstanceInspector→Tool~Preferences.BoolTool~XcodeInspector.XcodeInspector→Tool~Preferences.Bool
- Direction
- 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.
19→8 Tool~XcodeInspector uses Tool~SuggestionBasic✕
- Connections
- 2 pairs of types, where a type in Tool~XcodeInspector uses a type in Tool~SuggestionBasic.
- The types involved
Tool~XcodeInspector.DisabledLanguageList→Tool~SuggestionBasic.CodeLanguageTool~XcodeInspector.SourceEditor→Tool~SuggestionBasic.CursorRange
- 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.
19→10 Tool~XcodeInspector uses Tool~Toast✕
- Connections
- 1 pair of types, where a type in Tool~XcodeInspector uses a type in Tool~Toast.
- The types involved
Tool~XcodeInspector.XcodeInspector→Tool~Toast.ToastController
- 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.
19→18 Tool~XcodeInspector uses Tool~Status✕
- Connections
- 1 pair of types, where a type in Tool~XcodeInspector uses a type in Tool~Status.
- The types involved
Tool~XcodeInspector.XcodeAppInstanceInspector→Tool~Status.ExtensionPermissionStatus
- Direction
- Tool~XcodeInspector uses Tool~Status, so a change to Tool~Status can break Tool~XcodeInspector, while a change to Tool~XcodeInspector can't break Tool~Status.
- Position
- Below the diagonal: Tool~XcodeInspector uses a module listed above it, which is the healthy direction.
19→27 Tool~XcodeInspector uses repository part of a loop✕
- Connections
- 6 pairs of types, where a type in Tool~XcodeInspector uses a type in repository.
- The types involved
Tool~XcodeInspector.AppInstanceInspector→repository.NSRunningApplicationTool~XcodeInspector.SourceEditor→repository.NSRunningApplicationTool~XcodeInspector.SourceEditor→repository.TaskTool~XcodeInspector.WorkspaceXcodeWindowInspector→repository.NSRunningApplicationTool~XcodeInspector.WorkspaceXcodeWindowInspector→repository.TaskTool~XcodeInspector.XcodeAppInstanceInspector→repository.NSRunningApplication
- 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
- 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→28 Tool~XcodeInspector uses Tool~AXExtension part of a loop✕
- Connections
- 7 pairs of types, where a type in Tool~XcodeInspector uses a type in Tool~AXExtension.
- The types involved
Tool~XcodeInspector.AXNotification→Tool~AXExtension.AXUIElementTool~XcodeInspector.AppInstanceInspector→Tool~AXExtension.AXUIElementTool~XcodeInspector.SourceEditor→Tool~AXExtension.AXUIElementTool~XcodeInspector.WorkspaceXcodeWindowInspector→Tool~AXExtension.AXUIElementTool~XcodeInspector.XcodeAppInstanceInspector→Tool~AXExtension.AXUIElementTool~XcodeInspector.XcodeInspector→Tool~AXExtension.AXUIElementTool~XcodeInspector.XcodeWindowInspector→Tool~AXExtension.AXUIElement
- 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
- 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→29 Tool~XcodeInspector uses Core~SuggestionWidget part of a loop✕
- Connections
- 2 pairs of types, where a type in Tool~XcodeInspector uses a type in Core~SuggestionWidget.
- The types involved
Tool~XcodeInspector.SourceEditor→Core~SuggestionWidget.ContentTool~XcodeInspector.XcodeAppInstanceInspector→Core~SuggestionWidget.WorkspaceIdentifier
- Direction
- Tool~XcodeInspector uses Core~SuggestionWidget, so a change to Core~SuggestionWidget can break Tool~XcodeInspector, while a change to Tool~XcodeInspector can't break Core~SuggestionWidget.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→31 Tool~XcodeInspector uses Tool~FileSystem part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~XcodeInspector uses a type in Tool~FileSystem.
- The types involved
Tool~XcodeInspector.XcodeInspector→Tool~FileSystem.Date
- Direction
- Tool~XcodeInspector uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~XcodeInspector, while a change to Tool~XcodeInspector can't break Tool~FileSystem.
- Position
- 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→33 Tool~XcodeInspector uses Core~HostApp part of a loop✕
- Connections
- 7 pairs of types, where a type in Tool~XcodeInspector uses a type in Core~HostApp.
- The types involved
Tool~XcodeInspector.AppInstanceInspector→Core~HostApp.StringTool~XcodeInspector.DisabledLanguageList→Core~HostApp.StringTool~XcodeInspector.FileManager→Core~HostApp.StringTool~XcodeInspector.SourceEditor→Core~HostApp.StringTool~XcodeInspector.XcodeAppInstanceInspector→Core~HostApp.StringTool~XcodeInspector.XcodeInspector→Core~HostApp.StringTool~XcodeInspector.XcodeInspector+TriggerCommand.swift→Core~HostApp.String
- Direction
- Tool~XcodeInspector uses Core~HostApp, so a change to Core~HostApp can break Tool~XcodeInspector, while a change to Tool~XcodeInspector can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→38 Tool~XcodeInspector uses Core~ConversationTab part of a loop✕
- Connections
- 5 pairs of types, where a type in Tool~XcodeInspector uses a type in Core~ConversationTab.
- The types involved
Tool~XcodeInspector.AppInstanceInspector→Core~ConversationTab.URLTool~XcodeInspector.SourceEditor→Core~ConversationTab.URLTool~XcodeInspector.WorkspaceXcodeWindowInspector→Core~ConversationTab.URLTool~XcodeInspector.XcodeAppInstanceInspector→Core~ConversationTab.URLTool~XcodeInspector.XcodeInspector→Core~ConversationTab.URL
- Direction
- Tool~XcodeInspector uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~XcodeInspector, while a change to Tool~XcodeInspector can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→39 Tool~XcodeInspector uses Core~ChatService part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~XcodeInspector uses a type in Core~ChatService.
- The types involved
Tool~XcodeInspector.XcodeInspector→Core~ChatService.EditorInformation
- Direction
- Tool~XcodeInspector uses Core~ChatService, so a change to Core~ChatService can break Tool~XcodeInspector, while a change to Tool~XcodeInspector can't break Core~ChatService.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→2 Tool~ChatAPIService uses Tool~Preferences✕
- Connections
- 7 pairs of types, where a type in Tool~ChatAPIService uses a type in Tool~Preferences.
- The types involved
Tool~ChatAPIService.AutoManagedChatMemory→Tool~Preferences.IntTool~ChatAPIService.AutoManagedChatMemoryStrategy→Tool~Preferences.IntTool~ChatAPIService.ChatCompletionsRequestBody→Tool~Preferences.BoolTool~ChatAPIService.ChatCompletionsRequestBody→Tool~Preferences.DoubleTool~ChatAPIService.ConversationReference→Tool~Preferences.BoolTool~ChatAPIService.LineContent→Tool~Preferences.BoolTool~ChatAPIService.Role→Tool~Preferences.Bool
- Direction
- Tool~ChatAPIService uses Tool~Preferences, so a change to Tool~Preferences can break Tool~ChatAPIService, while a change to Tool~ChatAPIService can't break Tool~Preferences.
- Position
- Below the diagonal: Tool~ChatAPIService uses a module listed above it, which is the healthy direction.
20→7 Tool~ChatAPIService uses Tool~Persist✕
- Connections
- 1 pair of types, where a type in Tool~ChatAPIService uses a type in Tool~Persist.
- The types involved
Tool~ChatAPIService.ChatMessage→Tool~Persist.TurnItem
- Direction
- Tool~ChatAPIService uses Tool~Persist, so a change to Tool~Persist can break Tool~ChatAPIService, while a change to Tool~ChatAPIService can't break Tool~Persist.
- Position
- Below the diagonal: Tool~ChatAPIService uses a module listed above it, which is the healthy direction.
20→10 Tool~ChatAPIService uses Tool~Toast✕
- Connections
- 2 pairs of types, where a type in Tool~ChatAPIService uses a type in Tool~Toast.
- The types involved
Tool~ChatAPIService.ChatCompletionResponseBody→Tool~Toast.MessageTool~ChatAPIService.ChatCompletionsRequestBody→Tool~Toast.Message
- Direction
- Tool~ChatAPIService uses Tool~Toast, so a change to Tool~Toast can break Tool~ChatAPIService, while a change to Tool~ChatAPIService can't break Tool~Toast.
- Position
- Below the diagonal: Tool~ChatAPIService uses a module listed above it, which is the healthy direction.
20→19 Tool~ChatAPIService uses Tool~XcodeInspector✕
- Connections
- 1 pair of types, where a type in Tool~ChatAPIService uses a type in Tool~XcodeInspector.
- The types involved
Tool~ChatAPIService.AutoManagedChatMemoryActor→Tool~XcodeInspector.Actor
- Direction
- Tool~ChatAPIService uses Tool~XcodeInspector, so a change to Tool~XcodeInspector can break Tool~ChatAPIService, while a change to Tool~ChatAPIService can't break Tool~XcodeInspector.
- Position
- Below the diagonal: Tool~ChatAPIService uses a module listed above it, which is the healthy direction.
20→21 Tool~ChatAPIService uses Tool~ConversationServiceProvider part of a loop✕
- Connections
- 11 pairs of types, where a type in Tool~ChatAPIService uses a type in Tool~ConversationServiceProvider.
- The types involved
Tool~ChatAPIService.ChatMemory.swift→Tool~ConversationServiceProvider.MessageThinkingTool~ChatAPIService.ChatMessage→Tool~ConversationServiceProvider.AgentRoundTool~ChatAPIService.ChatMessage→Tool~ConversationServiceProvider.CodeReviewRoundTool~ChatAPIService.ChatMessage→Tool~ConversationServiceProvider.ConversationFollowUpTool~ChatAPIService.ChatMessage→Tool~ConversationServiceProvider.ConversationProgressStepTool~ChatAPIService.ChatMessage→Tool~ConversationServiceProvider.ConversationRatingTool~ChatAPIService.ChatMessage→Tool~ConversationServiceProvider.CopilotShowMessageParamsTool~ChatAPIService.ChatMessage→Tool~ConversationServiceProvider.ImageReferenceTool~ChatAPIService.ChatMessage→Tool~ConversationServiceProvider.MessageThinkingTool~ChatAPIService.ChatMessage→Tool~ConversationServiceProvider.TurnSchemaTool~ChatAPIService.FileEdit→Tool~ConversationServiceProvider.ToolName
- Direction
- Tool~ChatAPIService uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Tool~ChatAPIService, while a change to Tool~ChatAPIService can't break Tool~ConversationServiceProvider.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→31 Tool~ChatAPIService uses Tool~FileSystem part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~ChatAPIService uses a type in Tool~FileSystem.
- The types involved
Tool~ChatAPIService.ChatMessage→Tool~FileSystem.Date
- Direction
- Tool~ChatAPIService uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~ChatAPIService, while a change to Tool~ChatAPIService can't break Tool~FileSystem.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→33 Tool~ChatAPIService uses Core~HostApp part of a loop✕
- Connections
- 16 pairs of types, where a type in Tool~ChatAPIService uses a type in Core~HostApp.
- The types involved
Tool~ChatAPIService.AutoManagedChatMemory→Core~HostApp.StringTool~ChatAPIService.ChatCompletionResponseBody→Core~HostApp.StringTool~ChatAPIService.ChatCompletionsRequestBody→Core~HostApp.StringTool~ChatAPIService.ChatCompletionsStreamDataChunk→Core~HostApp.StringTool~ChatAPIService.ChatMemory→Core~HostApp.StringTool~ChatAPIService.ChatMessage→Core~HostApp.StringTool~ChatAPIService.ConversationReference→Core~HostApp.StringTool~ChatAPIService.Debugger→Core~HostApp.StringTool~ChatAPIService.Delta→Core~HostApp.StringTool~ChatAPIService.FileEdit→Core~HostApp.StringTool~ChatAPIService.Message→Core~HostApp.StringTool~ChatAPIService.ReferenceType→Core~HostApp.StringTool~ChatAPIService.RequestType→Core~HostApp.StringTool~ChatAPIService.Role→Core~HostApp.StringTool~ChatAPIService.Status→Core~HostApp.StringTool~ChatAPIService.TurnStatus→Core~HostApp.String
- Direction
- Tool~ChatAPIService uses Core~HostApp, so a change to Core~HostApp can break Tool~ChatAPIService, while a change to Tool~ChatAPIService can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→38 Tool~ChatAPIService uses Core~ConversationTab part of a loop✕
- Connections
- 5 pairs of types, where a type in Tool~ChatAPIService uses a type in Core~ConversationTab.
- The types involved
Tool~ChatAPIService.ChatMessage→Core~ConversationTab.RoleTool~ChatAPIService.ConversationReference→Core~ConversationTab.URLTool~ChatAPIService.Delta→Core~ConversationTab.RoleTool~ChatAPIService.FileEdit→Core~ConversationTab.URLTool~ChatAPIService.Message→Core~ConversationTab.Role
- Direction
- Tool~ChatAPIService uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~ChatAPIService, while a change to Tool~ChatAPIService can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→2 Tool~ConversationServiceProvider uses Tool~Preferences✕
- Connections
- 36 pairs of types, where a type in Tool~ConversationServiceProvider uses a type in Tool~Preferences. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Tool~ConversationServiceProvider.AgentModeToolHelpers→Tool~Preferences.BoolTool~ConversationServiceProvider.AgentRound→Tool~Preferences.IntTool~ConversationServiceProvider.AgentToolCall→Tool~Preferences.BoolTool~ConversationServiceProvider.AnyCodable→Tool~Preferences.BoolTool~ConversationServiceProvider.Capabilities→Tool~Preferences.BoolTool~ConversationServiceProvider.ContextSizeInfo→Tool~Preferences.DoubleTool~ConversationServiceProvider.ContextSizeInfo→Tool~Preferences.IntTool~ConversationServiceProvider.ConversationAttachedReference→Tool~Preferences.BoolTool~ConversationServiceProvider.ConversationCreateParams→Tool~Preferences.BoolTool~ConversationServiceProvider.ConversationDirectoryReference→Tool~Preferences.BoolTool~ConversationServiceProvider.ConversationDirectoryReference→Tool~Preferences.IntTool~ConversationServiceProvider.ConversationErrorCode→Tool~Preferences.IntTool~ConversationServiceProvider.ConversationFileReference→Tool~Preferences.BoolTool~ConversationServiceProvider.ConversationMode→Tool~Preferences.BoolTool~ConversationServiceProvider.ConversationRating→Tool~Preferences.IntTool~ConversationServiceProvider.ConversationRequest→Tool~Preferences.BoolTool~ConversationServiceProvider.ConversationServiceProvider→Tool~Preferences.IntTool~ConversationServiceProvider.ConversationServiceType→Tool~Preferences.IntTool~ConversationServiceProvider.CopilotLanguageServerError→Tool~Preferences.BoolTool~ConversationServiceProvider.CopilotLanguageServerError→Tool~Preferences.IntTool~ConversationServiceProvider.CopilotModel→Tool~Preferences.BoolTool~ConversationServiceProvider.CopilotModelBilling→Tool~Preferences.BoolTool~ConversationServiceProvider.CopilotModelBillingTokenPrices→Tool~Preferences.IntTool~ConversationServiceProvider.CopilotModelCapabilitiesLimits→Tool~Preferences.IntTool~ConversationServiceProvider.CopilotModelCapabilitiesSupports→Tool~Preferences.Bool
- Direction
- Tool~ConversationServiceProvider uses Tool~Preferences, so a change to Tool~Preferences can break Tool~ConversationServiceProvider, while a change to Tool~ConversationServiceProvider can't break Tool~Preferences.
- Position
- Below the diagonal: Tool~ConversationServiceProvider uses a module listed above it, which is the healthy direction.
21→5 Tool~ConversationServiceProvider uses Tool~GitHelper✕
- Connections
- 2 pairs of types, where a type in Tool~ConversationServiceProvider uses a type in Tool~GitHelper.
- The types involved
Tool~ConversationServiceProvider.CodeReviewRequest→Tool~GitHelper.PRChangeTool~ConversationServiceProvider.FileChange→Tool~GitHelper.PRChange
- Direction
- Tool~ConversationServiceProvider uses Tool~GitHelper, so a change to Tool~GitHelper can break Tool~ConversationServiceProvider, while a change to Tool~ConversationServiceProvider can't break Tool~GitHelper.
- Position
- Below the diagonal: Tool~ConversationServiceProvider uses a module listed above it, which is the healthy direction.
21→8 Tool~ConversationServiceProvider uses Tool~SuggestionBasic✕
- Connections
- 1 pair of types, where a type in Tool~ConversationServiceProvider uses a type in Tool~SuggestionBasic.
- The types involved
Tool~ConversationServiceProvider.FileReference→Tool~SuggestionBasic.CursorRange
- Direction
- Tool~ConversationServiceProvider uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Tool~ConversationServiceProvider, while a change to Tool~ConversationServiceProvider can't break Tool~SuggestionBasic.
- Position
- Below the diagonal: Tool~ConversationServiceProvider uses a module listed above it, which is the healthy direction.
21→20 Tool~ConversationServiceProvider uses Tool~ChatAPIService✕
- Connections
- 2 pairs of types, where a type in Tool~ConversationServiceProvider uses a type in Tool~ChatAPIService.
- The types involved
Tool~ConversationServiceProvider.CodeReviewRound→Tool~ChatAPIService.StatusTool~ConversationServiceProvider.Status→Tool~ChatAPIService.Status
- Direction
- Tool~ConversationServiceProvider uses Tool~ChatAPIService, so a change to Tool~ChatAPIService can break Tool~ConversationServiceProvider, while a change to Tool~ConversationServiceProvider can't break Tool~ChatAPIService.
- Position
- Below the diagonal: Tool~ConversationServiceProvider uses a module listed above it, which is the healthy direction.
21→29 Tool~ConversationServiceProvider uses Core~SuggestionWidget part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~ConversationServiceProvider uses a type in Core~SuggestionWidget.
- The types involved
Tool~ConversationServiceProvider.LanguageModelToolResult→Core~SuggestionWidget.Content
- Direction
- Tool~ConversationServiceProvider uses Core~SuggestionWidget, so a change to Core~SuggestionWidget can break Tool~ConversationServiceProvider, while a change to Tool~ConversationServiceProvider 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.
21→33 Tool~ConversationServiceProvider uses Core~HostApp part of a loop✕
- Connections
- 82 pairs of types, where a type in Tool~ConversationServiceProvider uses a type in Core~HostApp. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Tool~ConversationServiceProvider.ActionCommand→Core~HostApp.StringTool~ConversationServiceProvider.AgentModeToolHelpers→Core~HostApp.StringTool~ConversationServiceProvider.AgentRound→Core~HostApp.StringTool~ConversationServiceProvider.AgentToolCall→Core~HostApp.StringTool~ConversationServiceProvider.Capabilities→Core~HostApp.StringTool~ConversationServiceProvider.Change→Core~HostApp.StringTool~ConversationServiceProvider.ChatAgent→Core~HostApp.StringTool~ConversationServiceProvider.ChatCompletionContentPartImage→Core~HostApp.StringTool~ConversationServiceProvider.ChatCompletionContentPartText→Core~HostApp.StringTool~ConversationServiceProvider.ChatCompletionImageURL→Core~HostApp.StringTool~ConversationServiceProvider.ChatMode→Core~HostApp.StringTool~ConversationServiceProvider.ChatTemplate→Core~HostApp.StringTool~ConversationServiceProvider.CodeReviewRound→Core~HostApp.StringTool~ConversationServiceProvider.CodingKeys→Core~HostApp.StringTool~ConversationServiceProvider.ConversationAttachedReference→Core~HostApp.StringTool~ConversationServiceProvider.ConversationCreateParams→Core~HostApp.StringTool~ConversationServiceProvider.ConversationCreateResponse→Core~HostApp.StringTool~ConversationServiceProvider.ConversationDirectoryReference→Core~HostApp.StringTool~ConversationServiceProvider.ConversationFileReference→Core~HostApp.StringTool~ConversationServiceProvider.ConversationFollowUp→Core~HostApp.StringTool~ConversationServiceProvider.ConversationMode→Core~HostApp.StringTool~ConversationServiceProvider.ConversationModelInfo→Core~HostApp.StringTool~ConversationServiceProvider.ConversationProgressStep→Core~HostApp.StringTool~ConversationServiceProvider.ConversationRequest→Core~HostApp.StringTool~ConversationServiceProvider.ConversationServiceProvider→Core~HostApp.String
- Direction
- Tool~ConversationServiceProvider uses Core~HostApp, so a change to Core~HostApp can break Tool~ConversationServiceProvider, while a change to Tool~ConversationServiceProvider can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→38 Tool~ConversationServiceProvider uses Core~ConversationTab part of a loop✕
- Connections
- 9 pairs of types, where a type in Tool~ConversationServiceProvider uses a type in Core~ConversationTab.
- The types involved
Tool~ConversationServiceProvider.ConversationAttachedReference→Core~ConversationTab.URLTool~ConversationServiceProvider.ConversationDirectoryReference→Core~ConversationTab.URLTool~ConversationServiceProvider.ConversationFileReference→Core~ConversationTab.URLTool~ConversationServiceProvider.ConversationServiceProvider→Core~ConversationTab.URLTool~ConversationServiceProvider.ConversationServiceType→Core~ConversationTab.URLTool~ConversationServiceProvider.CopilotModel→Core~ConversationTab.LLMModelTool~ConversationServiceProvider.FileComment→Core~ConversationTab.URLTool~ConversationServiceProvider.ImageReference→Core~ConversationTab.URLTool~ConversationServiceProvider.PromptType→Core~ConversationTab.URL
- Direction
- Tool~ConversationServiceProvider uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~ConversationServiceProvider, while a change to Tool~ConversationServiceProvider can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→2 Tool~SharedUIComponents uses Tool~Preferences✕
- Connections
- 38 pairs of types, where a type in Tool~SharedUIComponents uses a type in Tool~Preferences. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Tool~SharedUIComponents.AsyncCodeBlock→Tool~Preferences.BoolTool~SharedUIComponents.AsyncCodeBlock→Tool~Preferences.DoubleTool~SharedUIComponents.AsyncCodeBlock→Tool~Preferences.IntTool~SharedUIComponents.AutoresizingCustomTextEditor→Tool~Preferences.BoolTool~SharedUIComponents.AutoresizingCustomTextEditor→Tool~Preferences.DoubleTool~SharedUIComponents.CodeBlock→Tool~Preferences.BoolTool~SharedUIComponents.CodeBlock→Tool~Preferences.IntTool~SharedUIComponents.CodeHighlighting→Tool~Preferences.BoolTool~SharedUIComponents.CollapsibleSearchField→Tool~Preferences.BoolTool~SharedUIComponents.Constants→Tool~Preferences.DoubleTool~SharedUIComponents.CopilotIntroSheet→Tool~Preferences.BoolTool~SharedUIComponents.CopyButton→Tool~Preferences.BoolTool~SharedUIComponents.CreateCustomCopilotFileView→Tool~Preferences.BoolTool~SharedUIComponents.CustomScrollView→Tool~Preferences.DoubleTool~SharedUIComponents.CustomScrollViewHeightPreferenceKey→Tool~Preferences.DoubleTool~SharedUIComponents.CustomScrollViewHeightPreferenceKey→Tool~Preferences.PreferenceKeyTool~SharedUIComponents.CustomTextEditor→Tool~Preferences.BoolTool~SharedUIComponents.CustomTextEditor→Tool~Preferences.DoubleTool~SharedUIComponents.DownvoteButton→Tool~Preferences.BoolTool~SharedUIComponents.FileIcon.swift→Tool~Preferences.BoolTool~SharedUIComponents.FontScaleManager→Tool~Preferences.DoubleTool~SharedUIComponents.HoverButtonStyle→Tool~Preferences.BoolTool~SharedUIComponents.HoverScrollView→Tool~Preferences.BoolTool~SharedUIComponents.Instruction→Tool~Preferences.BoolTool~SharedUIComponents.OverlayScrollView→Tool~Preferences.Bool
- 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.
22→18 Tool~SharedUIComponents uses Tool~Status✕
- Connections
- 3 pairs of types, where a type in Tool~SharedUIComponents uses a type in Tool~Status.
- The types involved
Tool~SharedUIComponents.QuotaPopoverView→Tool~Status.GitHubCopilotQuotaInfoTool~SharedUIComponents.QuotaPopoverView→Tool~Status.QuotaSnapshotTool~SharedUIComponents.QuotaPopoverView→Tool~Status.UsageLevel
- Direction
- Tool~SharedUIComponents uses Tool~Status, so a change to Tool~Status can break Tool~SharedUIComponents, while a change to Tool~SharedUIComponents can't break Tool~Status.
- Position
- Below the diagonal: Tool~SharedUIComponents uses a module listed above it, which is the healthy direction.
22→20 Tool~SharedUIComponents uses Tool~ChatAPIService✕
- Connections
- 1 pair of types, where a type in Tool~SharedUIComponents uses a type in Tool~ChatAPIService.
- The types involved
Tool~SharedUIComponents.SplitButtonMenuItem→Tool~ChatAPIService.Kind
- Direction
- Tool~SharedUIComponents uses Tool~ChatAPIService, so a change to Tool~ChatAPIService can break Tool~SharedUIComponents, while a change to Tool~SharedUIComponents can't break Tool~ChatAPIService.
- Position
- Below the diagonal: Tool~SharedUIComponents uses a module listed above it, which is the healthy direction.
22→21 Tool~SharedUIComponents uses Tool~ConversationServiceProvider✕
- Connections
- 1 pair of types, where a type in Tool~SharedUIComponents uses a type in Tool~ConversationServiceProvider.
- The types involved
Tool~SharedUIComponents.CreateCustomCopilotFileView→Tool~ConversationServiceProvider.PromptType
- Direction
- Tool~SharedUIComponents uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Tool~SharedUIComponents, while a change to Tool~SharedUIComponents can't break Tool~ConversationServiceProvider.
- Position
- Below the diagonal: Tool~SharedUIComponents uses a module listed above it, which is the healthy direction.
22→29 Tool~SharedUIComponents uses Core~SuggestionWidget part of a loop✕
- Connections
- 12 pairs of types, where a type in Tool~SharedUIComponents uses a type in Core~SuggestionWidget.
- The types involved
Tool~SharedUIComponents.ConditionalFontWeight→Core~SuggestionWidget.ContentTool~SharedUIComponents.CopilotIntroSheet→Core~SuggestionWidget.ContentTool~SharedUIComponents.CustomScrollViewUpdateHeightModifier→Core~SuggestionWidget.ContentTool~SharedUIComponents.DynamicHeightTextInFormWorkaroundModifier→Core~SuggestionWidget.ContentTool~SharedUIComponents.HoverScrollView→Core~SuggestionWidget.ContentTool~SharedUIComponents.OverlayScrollView→Core~SuggestionWidget.ContentTool~SharedUIComponents.ScaledConstraintFrameView→Core~SuggestionWidget.ContentTool~SharedUIComponents.ScaledFontView→Core~SuggestionWidget.ContentTool~SharedUIComponents.ScaledFrameView→Core~SuggestionWidget.ContentTool~SharedUIComponents.ScaledPaddingView→Core~SuggestionWidget.ContentTool~SharedUIComponents.ScaledScaleEffectView→Core~SuggestionWidget.ContentTool~SharedUIComponents.TextFieldsContainer→Core~SuggestionWidget.Content
- Direction
- Tool~SharedUIComponents uses Core~SuggestionWidget, so a change to Core~SuggestionWidget can break Tool~SharedUIComponents, while a change to Tool~SharedUIComponents 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.
22→31 Tool~SharedUIComponents uses Tool~FileSystem part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~SharedUIComponents uses a type in Tool~FileSystem.
- The types involved
Tool~SharedUIComponents.HalfCapsule→Tool~FileSystem.Path
- Direction
- Tool~SharedUIComponents uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~SharedUIComponents, while a change to Tool~SharedUIComponents can't break Tool~FileSystem.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→33 Tool~SharedUIComponents uses Core~HostApp part of a loop✕
- Connections
- 21 pairs of types, where a type in Tool~SharedUIComponents uses a type in Core~HostApp.
- The types involved
Tool~SharedUIComponents.AsyncCodeBlock→Core~HostApp.StringTool~SharedUIComponents.AutoresizingCustomTextEditor→Core~HostApp.StringTool~SharedUIComponents.CodeBlock→Core~HostApp.StringTool~SharedUIComponents.CodeHighlighting→Core~HostApp.StringTool~SharedUIComponents.CollapsibleSearchField→Core~HostApp.StringTool~SharedUIComponents.Coordinator→Core~HostApp.StringTool~SharedUIComponents.CopilotIntroItem→Core~HostApp.StringTool~SharedUIComponents.CreateCustomCopilotFileView→Core~HostApp.StringTool~SharedUIComponents.CustomTextEditor→Core~HostApp.StringTool~SharedUIComponents.DestructiveButtonStyle→Core~HostApp.ButtonStyleTool~SharedUIComponents.FontScaleManager→Core~HostApp.StringTool~SharedUIComponents.HoverButtonStyle→Core~HostApp.ButtonStyleTool~SharedUIComponents.MixedStateCheckbox→Core~HostApp.StringTool~SharedUIComponents.MixedStateCheckboxView→Core~HostApp.StringTool~SharedUIComponents.QuotaItem→Core~HostApp.StringTool~SharedUIComponents.QuotaPopoverView→Core~HostApp.StringTool~SharedUIComponents.SearchFieldRepresentable→Core~HostApp.StringTool~SharedUIComponents.SettingsDivider→Core~HostApp.StringTool~SharedUIComponents.SplitButton→Core~HostApp.StringTool~SharedUIComponents.SplitButtonMenuItem→Core~HostApp.StringTool~SharedUIComponents.SplitButtonRepresentable→Core~HostApp.String
- Direction
- Tool~SharedUIComponents uses Core~HostApp, so a change to Core~HostApp can break Tool~SharedUIComponents, while a change to Tool~SharedUIComponents can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→38 Tool~SharedUIComponents uses Core~ConversationTab part of a loop✕
- Connections
- 48 pairs of types, where a type in Tool~SharedUIComponents uses a type in Core~ConversationTab. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Tool~SharedUIComponents.AdaptiveHelpLink→Core~ConversationTab.ViewTool~SharedUIComponents.AsyncCodeBlock→Core~ConversationTab.ColorTool~SharedUIComponents.AsyncCodeBlock→Core~ConversationTab.ViewTool~SharedUIComponents.AutoresizingCustomTextEditor→Core~ConversationTab.ViewTool~SharedUIComponents.CodeBlock→Core~ConversationTab.ColorTool~SharedUIComponents.CodeBlock→Core~ConversationTab.ViewTool~SharedUIComponents.CodeBlock_Previews→Core~ConversationTab.ViewTool~SharedUIComponents.CollapsibleSearchField→Core~ConversationTab.ViewTool~SharedUIComponents.ConditionalFontWeight→Core~ConversationTab.ViewTool~SharedUIComponents.CopilotIntroContent→Core~ConversationTab.ViewTool~SharedUIComponents.CopilotIntroItem→Core~ConversationTab.ViewTool~SharedUIComponents.CopilotIntroSheet→Core~ConversationTab.ViewTool~SharedUIComponents.CopilotMessageHeader→Core~ConversationTab.ViewTool~SharedUIComponents.CopyButton→Core~ConversationTab.ColorTool~SharedUIComponents.CopyButton→Core~ConversationTab.ViewTool~SharedUIComponents.CreateCustomCopilotFileView→Core~ConversationTab.URLTool~SharedUIComponents.CreateCustomCopilotFileView→Core~ConversationTab.ViewTool~SharedUIComponents.CustomScrollView→Core~ConversationTab.ViewTool~SharedUIComponents.CustomScrollViewUpdateHeightModifier→Core~ConversationTab.ViewTool~SharedUIComponents.CustomTextEditor→Core~ConversationTab.CoordinatorTool~SharedUIComponents.DestructiveButtonStyle→Core~ConversationTab.ViewTool~SharedUIComponents.DownvoteButton→Core~ConversationTab.ViewTool~SharedUIComponents.DynamicHeightTextInFormWorkaroundModifier→Core~ConversationTab.ViewTool~SharedUIComponents.FileIcon.swift→Core~ConversationTab.URLTool~SharedUIComponents.FileIcon.swift→Core~ConversationTab.View
- Direction
- Tool~SharedUIComponents uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~SharedUIComponents, while a change to Tool~SharedUIComponents can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→1 Tool~Workspace uses Core~UserDefaultsObserver✕
- Connections
- 1 pair of types, where a type in Tool~Workspace uses a type in Core~UserDefaultsObserver.
- The types involved
Tool~Workspace.Workspace→Core~UserDefaultsObserver.UserDefaultsObserver
- Direction
- Tool~Workspace uses Core~UserDefaultsObserver, so a change to Core~UserDefaultsObserver can break Tool~Workspace, while a change to Tool~Workspace can't break Core~UserDefaultsObserver.
- Position
- Below the diagonal: Tool~Workspace uses a module listed above it, which is the healthy direction.
23→2 Tool~Workspace uses Tool~Preferences✕
- Connections
- 20 pairs of types, where a type in Tool~Workspace uses a type in Tool~Preferences.
- The types involved
Tool~Workspace.BatchingFileChangeWatcher→Tool~Preferences.BoolTool~Workspace.BatchingFileChangeWatcher→Tool~Preferences.IntTool~Workspace.FileChangeWatcherService→Tool~Preferences.BoolTool~Workspace.FileChangeWatcherWorkspaceFileProvider→Tool~Preferences.BoolTool~Workspace.FileWatcherProtocol→Tool~Preferences.BoolTool~Workspace.Filespace→Tool~Preferences.BoolTool~Workspace.Filespace→Tool~Preferences.IntTool~Workspace.FilespaceCodeMetadata→Tool~Preferences.BoolTool~Workspace.FilespaceCodeMetadata→Tool~Preferences.IntTool~Workspace.SingleFileWatcher→Tool~Preferences.BoolTool~Workspace.Workspace→Tool~Preferences.BoolTool~Workspace.Workspace→Tool~Preferences.IntTool~Workspace.WorkspaceDirectory→Tool~Preferences.BoolTool~Workspace.WorkspaceDirectoryIndex→Tool~Preferences.BoolTool~Workspace.WorkspaceDirectoryIndex→Tool~Preferences.IntTool~Workspace.WorkspaceFile→Tool~Preferences.BoolTool~Workspace.WorkspaceFile→Tool~Preferences.DataTool~Workspace.WorkspaceFileIndex→Tool~Preferences.BoolTool~Workspace.WorkspaceFileIndex→Tool~Preferences.IntTool~Workspace.WorkspaceFileProvider→Tool~Preferences.Bool
- 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.
23→8 Tool~Workspace uses Tool~SuggestionBasic✕
- Connections
- 4 pairs of types, where a type in Tool~Workspace uses a type in Tool~SuggestionBasic.
- The types involved
Tool~Workspace.Filespace→Tool~SuggestionBasic.CodeLanguageTool~Workspace.Filespace→Tool~SuggestionBasic.CodeSuggestionTool~Workspace.Filespace→Tool~SuggestionBasic.CursorPositionTool~Workspace.Workspace→Tool~SuggestionBasic.CodeSuggestion
- 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.
23→13 Tool~Workspace uses Tool~SuggestionProvider✕
- Connections
- 1 pair of types, where a type in Tool~Workspace uses a type in Tool~SuggestionProvider.
- The types involved
Tool~Workspace.Workspace→Tool~SuggestionProvider.SuggestionServiceProvider
- 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.
23→16 Tool~Workspace uses Tool~WorkspaceSuggestionService✕
- Connections
- 2 pairs of types, where a type in Tool~Workspace uses a type in Tool~WorkspaceSuggestionService.
- The types involved
Tool~Workspace.FilespacePropertyValues→Tool~WorkspaceSuggestionService.FilespaceSuggestionSnapshotTool~Workspace.Workspace→Tool~WorkspaceSuggestionService.SuggestionServiceWorkspacePlugin
- 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.
23→17 Tool~Workspace uses Tool~GitHubCopilotService✕
- Connections
- 2 pairs of types, where a type in Tool~Workspace uses a type in Tool~GitHubCopilotService.
- The types involved
Tool~Workspace.Workspace→Tool~GitHubCopilotService.GitHubCopilotServiceTool~Workspace.Workspace→Tool~GitHubCopilotService.GitHubCopilotWorkspacePlugin
- Direction
- Tool~Workspace uses Tool~GitHubCopilotService, so a change to Tool~GitHubCopilotService can break Tool~Workspace, while a change to Tool~Workspace can't break Tool~GitHubCopilotService.
- Position
- Below the diagonal: Tool~Workspace uses a module listed above it, which is the healthy direction.
23→19 Tool~Workspace uses Tool~XcodeInspector✕
- Connections
- 1 pair of types, where a type in Tool~Workspace uses a type in Tool~XcodeInspector.
- The types involved
Tool~Workspace.PoolActor→Tool~XcodeInspector.Actor
- Direction
- Tool~Workspace uses Tool~XcodeInspector, so a change to Tool~XcodeInspector can break Tool~Workspace, while a change to Tool~Workspace can't break Tool~XcodeInspector.
- Position
- Below the diagonal: Tool~Workspace uses a module listed above it, which is the healthy direction.
23→21 Tool~Workspace uses Tool~ConversationServiceProvider✕
- Connections
- 7 pairs of types, where a type in Tool~Workspace uses a type in Tool~ConversationServiceProvider.
- The types involved
Tool~Workspace.FileChangeWatcherWorkspaceFileProvider→Tool~ConversationServiceProvider.ConversationFileReferenceTool~Workspace.WorkspaceDirectory→Tool~ConversationServiceProvider.ConversationDirectoryReferenceTool~Workspace.WorkspaceDirectoryIndex→Tool~ConversationServiceProvider.ConversationDirectoryReferenceTool~Workspace.WorkspaceFile→Tool~ConversationServiceProvider.ConversationFileReferenceTool~Workspace.WorkspaceFile→Tool~ConversationServiceProvider.WorkspaceInfoTool~Workspace.WorkspaceFileIndex→Tool~ConversationServiceProvider.ConversationFileReferenceTool~Workspace.WorkspaceFileProvider→Tool~ConversationServiceProvider.ConversationFileReference
- Direction
- Tool~Workspace uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Tool~Workspace, while a change to Tool~Workspace can't break Tool~ConversationServiceProvider.
- Position
- Below the diagonal: Tool~Workspace uses a module listed above it, which is the healthy direction.
23→25 Tool~Workspace uses Core~Service part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~Workspace uses a type in Core~Service.
- The types involved
Tool~Workspace.WorkspaceActor→Core~Service.TheActor
- Direction
- Tool~Workspace uses Core~Service, so a change to Core~Service can break Tool~Workspace, while a change to Tool~Workspace can't break Core~Service.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→26 Tool~Workspace uses Tool~XPCShared part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~Workspace uses a type in Tool~XPCShared.
- The types involved
Tool~Workspace.Workspace→Tool~XPCShared.EditorContent
- Direction
- Tool~Workspace uses Tool~XPCShared, so a change to Tool~XPCShared can break Tool~Workspace, while a change to Tool~Workspace can't break Tool~XPCShared.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→30 Tool~Workspace uses Core~XcodeThemeController part of a loop✕
- Connections
- 2 pairs of types, where a type in Tool~Workspace uses a type in Core~XcodeThemeController.
- The types involved
Tool~Workspace.CantFindWorkspaceError→Core~XcodeThemeController.ErrorTool~Workspace.Error→Core~XcodeThemeController.Error
- Direction
- Tool~Workspace uses Core~XcodeThemeController, so a change to Core~XcodeThemeController can break Tool~Workspace, while a change to Tool~Workspace can't break Core~XcodeThemeController.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→31 Tool~Workspace uses Tool~FileSystem part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~Workspace uses a type in Tool~FileSystem.
- The types involved
Tool~Workspace.Filespace→Tool~FileSystem.Date
- Direction
- Tool~Workspace uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~Workspace, while a change to Tool~Workspace can't break Tool~FileSystem.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→33 Tool~Workspace uses Core~HostApp part of a loop✕
- Connections
- 12 pairs of types, where a type in Tool~Workspace uses a type in Core~HostApp.
- The types involved
Tool~Workspace.CantFindWorkspaceError→Core~HostApp.StringTool~Workspace.Error→Core~HostApp.StringTool~Workspace.FileChangeWatcherWorkspaceFileProvider→Core~HostApp.StringTool~Workspace.Filespace→Core~HostApp.StringTool~Workspace.FilespaceCodeMetadata→Core~HostApp.StringTool~Workspace.OpenedFileRecoverableStorage→Core~HostApp.StringTool~Workspace.ProjectInfo→Core~HostApp.StringTool~Workspace.Workspace→Core~HostApp.StringTool~Workspace.WorkspaceFile→Core~HostApp.StringTool~Workspace.WorkspaceFileError→Core~HostApp.StringTool~Workspace.WorkspaceFileProvider→Core~HostApp.StringTool~Workspace.WorkspacePlugin→Core~HostApp.String
- Direction
- Tool~Workspace uses Core~HostApp, so a change to Core~HostApp can break Tool~Workspace, while a change to Tool~Workspace can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→38 Tool~Workspace uses Core~ConversationTab part of a loop✕
- Connections
- 19 pairs of types, where a type in Tool~Workspace uses a type in Core~ConversationTab.
- The types involved
Tool~Workspace.BatchingFileChangeWatcher→Core~ConversationTab.URLTool~Workspace.DefaultFileWatcherFactory→Core~ConversationTab.URLTool~Workspace.DirectoryWatcherProtocol→Core~ConversationTab.URLTool~Workspace.FileChangeWatcherService→Core~ConversationTab.URLTool~Workspace.FileChangeWatcherServicePool→Core~ConversationTab.URLTool~Workspace.FileChangeWatcherWorkspaceFileProvider→Core~ConversationTab.URLTool~Workspace.FileSaveWatcher→Core~ConversationTab.URLTool~Workspace.FileWatcherFactory→Core~ConversationTab.URLTool~Workspace.Filespace→Core~ConversationTab.URLTool~Workspace.OpenedFileRecoverableStorage→Core~ConversationTab.URLTool~Workspace.SingleFileWatcher→Core~ConversationTab.URLTool~Workspace.Workspace→Core~ConversationTab.URLTool~Workspace.WorkspaceDirectory→Core~ConversationTab.URLTool~Workspace.WorkspaceDirectoryIndex→Core~ConversationTab.URLTool~Workspace.WorkspaceFile→Core~ConversationTab.URLTool~Workspace.WorkspaceFileIndex→Core~ConversationTab.URLTool~Workspace.WorkspaceFileProvider→Core~ConversationTab.URLTool~Workspace.WorkspacePlugin→Core~ConversationTab.URLTool~Workspace.WorkspacePool→Core~ConversationTab.URL
- Direction
- Tool~Workspace uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~Workspace, while a change to Tool~Workspace can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→1 Core~KeyBindingManager uses Core~UserDefaultsObserver✕
- Connections
- 1 pair of types, where a type in Core~KeyBindingManager uses a type in Core~UserDefaultsObserver.
- The types involved
Core~KeyBindingManager.TabToAcceptSuggestion→Core~UserDefaultsObserver.UserDefaultsObserver
- Direction
- Core~KeyBindingManager uses Core~UserDefaultsObserver, so a change to Core~UserDefaultsObserver can break Core~KeyBindingManager, while a change to Core~KeyBindingManager can't break Core~UserDefaultsObserver.
- Position
- Below the diagonal: Core~KeyBindingManager uses a module listed above it, which is the healthy direction.
24→2 Core~KeyBindingManager uses Tool~Preferences✕
- Connections
- 3 pairs of types, where a type in Core~KeyBindingManager uses a type in Tool~Preferences.
- The types involved
Core~KeyBindingManager.TabToAcceptSuggestion→Tool~Preferences.BoolCore~KeyBindingManager.ThreadSafeAccessToXcodeInspector→Tool~Preferences.BoolCore~KeyBindingManager.ThreadSafeAccessToXcodeInspectorProtocol→Tool~Preferences.Bool
- 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.
24→23 Core~KeyBindingManager uses Tool~Workspace✕
- Connections
- 2 pairs of types, where a type in Core~KeyBindingManager uses a type in Tool~Workspace.
- The types involved
Core~KeyBindingManager.KeyBindingManager→Tool~Workspace.WorkspacePoolCore~KeyBindingManager.TabToAcceptSuggestion→Tool~Workspace.WorkspacePool
- 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.
24→38 Core~KeyBindingManager uses Core~ConversationTab part of a loop✕
- Connections
- 2 pairs of types, where a type in Core~KeyBindingManager uses a type in Core~ConversationTab.
- The types involved
Core~KeyBindingManager.ThreadSafeAccessToXcodeInspector→Core~ConversationTab.URLCore~KeyBindingManager.ThreadSafeAccessToXcodeInspectorProtocol→Core~ConversationTab.URL
- Direction
- Core~KeyBindingManager uses Core~ConversationTab, so a change to Core~ConversationTab can break Core~KeyBindingManager, while a change to Core~KeyBindingManager can't break Core~ConversationTab.
- Position
- 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.
25→2 Core~Service uses Tool~Preferences✕
- Connections
- 8 pairs of types, where a type in Core~Service uses a type in Tool~Preferences.
- The types involved
Core~Service.NSError→Tool~Preferences.BoolCore~Service.PresentInWindowSuggestionPresenter→Tool~Preferences.BoolCore~Service.PseudoCommandHandler→Tool~Preferences.BoolCore~Service.RealtimeSuggestionController→Tool~Preferences.BoolCore~Service.Service→Tool~Preferences.DataCore~Service.WindowBaseCommandHandler→Tool~Preferences.BoolCore~Service.XPCService→Tool~Preferences.BoolCore~Service.XPCService→Tool~Preferences.Data
- 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.
25→6 Core~Service uses Tool~Logger✕
- Connections
- 1 pair of types, where a type in Core~Service uses a type in Tool~Logger.
- The types involved
Core~Service.TelemetryLogger→Tool~Logger.TelemetryLoggerProvider
- Direction
- Core~Service uses Tool~Logger, so a change to Tool~Logger can break Core~Service, while a change to Core~Service can't break Tool~Logger.
- Position
- Below the diagonal: Core~Service uses a module listed above it, which is the healthy direction.
25→8 Core~Service uses Tool~SuggestionBasic✕
- Connections
- 1 pair of types, where a type in Core~Service uses a type in Tool~SuggestionBasic.
- The types involved
Core~Service.PseudoCommandHandler→Tool~SuggestionBasic.CodeSuggestionType
- 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.
25→10 Core~Service uses Tool~Toast✕
- Connections
- 1 pair of types, where a type in Core~Service uses a type in Tool~Toast.
- The types involved
Core~Service.PseudoCommandHandler→Tool~Toast.ToastController
- Direction
- Core~Service uses Tool~Toast, so a change to Tool~Toast can break Core~Service, while a change to Core~Service can't break Tool~Toast.
- Position
- Below the diagonal: Core~Service uses a module listed above it, which is the healthy direction.
25→12 Core~Service uses Tool~ChatTab✕
- Connections
- 1 pair of types, where a type in Core~Service uses a type in Tool~ChatTab.
- The types involved
Core~Service.GraphicalUserInterfaceController→Tool~ChatTab.ChatTabPool
- Direction
- Core~Service uses Tool~ChatTab, so a change to Tool~ChatTab can break Core~Service, while a change to Core~Service can't break Tool~ChatTab.
- Position
- Below the diagonal: Core~Service uses a module listed above it, which is the healthy direction.
25→16 Core~Service uses Tool~WorkspaceSuggestionService✕
- Connections
- 1 pair of types, where a type in Core~Service uses a type in Tool~WorkspaceSuggestionService.
- The types involved
Core~Service.WidgetDataSource.swift→Tool~WorkspaceSuggestionService.FilespaceSuggestionSnapshot
- Direction
- Core~Service uses Tool~WorkspaceSuggestionService, so a change to Tool~WorkspaceSuggestionService can break Core~Service, while a change to Core~Service can't break Tool~WorkspaceSuggestionService.
- Position
- Below the diagonal: Core~Service uses a module listed above it, which is the healthy direction.
25→18 Core~Service uses Tool~Status✕
- Connections
- 1 pair of types, where a type in Core~Service uses a type in Tool~Status.
- The types involved
Core~Service.Service→Tool~Status.AuthStatus
- Direction
- Core~Service uses Tool~Status, so a change to Tool~Status can break Core~Service, while a change to Core~Service can't break Tool~Status.
- Position
- Below the diagonal: Core~Service uses a module listed above it, which is the healthy direction.
25→19 Core~Service uses Tool~XcodeInspector✕
- Connections
- 2 pairs of types, where a type in Core~Service uses a type in Tool~XcodeInspector.
- The types involved
Core~Service.PseudoCommandHandler→Tool~XcodeInspector.SourceEditorCore~Service.RealtimeSuggestionController→Tool~XcodeInspector.SourceEditor
- 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.
25→23 Core~Service uses Tool~Workspace✕
- Connections
- 4 pairs of types, where a type in Core~Service uses a type in Tool~Workspace.
- The types involved
Core~Service.PseudoCommandHandler→Tool~Workspace.FilespaceCore~Service.PseudoCommandHandler→Tool~Workspace.WorkspaceCore~Service.Service→Tool~Workspace.WorkspacePoolCore~Service.WidgetDataSource.swift→Tool~Workspace.Filespace
- Direction
- Core~Service uses Tool~Workspace, so a change to Tool~Workspace can break Core~Service, while a change to Core~Service can't break Tool~Workspace.
- Position
- Below the diagonal: Core~Service uses a module listed above it, which is the healthy direction.
25→24 Core~Service uses Core~KeyBindingManager✕
- Connections
- 1 pair of types, where a type in Core~Service uses a type in Core~KeyBindingManager.
- The types involved
Core~Service.Service→Core~KeyBindingManager.KeyBindingManager
- 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.
25→26 Core~Service uses Tool~XPCShared part of a loop✕
- Connections
- 7 pairs of types, where a type in Core~Service uses a type in Tool~XPCShared.
- The types involved
Core~Service.PseudoCommandHandler→Tool~XPCShared.EditorContentCore~Service.PseudoCommandHandler→Tool~XPCShared.UpdatedContentCore~Service.SuggestionCommandHandler→Tool~XPCShared.EditorContentCore~Service.SuggestionCommandHandler→Tool~XPCShared.UpdatedContentCore~Service.WindowBaseCommandHandler→Tool~XPCShared.EditorContentCore~Service.WindowBaseCommandHandler→Tool~XPCShared.UpdatedContentCore~Service.XPCService→Tool~XPCShared.XPCServiceProtocol
- Direction
- Core~Service uses Tool~XPCShared, so a change to Tool~XPCShared can break Core~Service, while a change to Core~Service can't break Tool~XPCShared.
- 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.
25→27 Core~Service uses repository part of a loop✕
- Connections
- 3 pairs of types, where a type in Core~Service uses a type in repository.
- The types involved
Core~Service.PseudoCommandHandler→repository.CustomCommandCore~Service.RealtimeSuggestionController→repository.TaskCore~Service.XPCService→repository.Task
- Direction
- Core~Service uses repository, so a change to repository can break Core~Service, while a change to Core~Service 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.
25→28 Core~Service uses Tool~AXExtension part of a loop✕
- Connections
- 2 pairs of types, where a type in Core~Service uses a type in Tool~AXExtension.
- The types involved
Core~Service.PseudoCommandHandler→Tool~AXExtension.AXUIElementCore~Service.RealtimeSuggestionController→Tool~AXExtension.AXUIElement
- 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
- 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.
25→29 Core~Service uses Core~SuggestionWidget part of a loop✕
- Connections
- 4 pairs of types, where a type in Core~Service uses a type in Core~SuggestionWidget.
- The types involved
Core~Service.ChatTabFactory→Core~SuggestionWidget.ChatTabBuilderCollectionCore~Service.GraphicalUserInterfaceController→Core~SuggestionWidget.SuggestionWidgetControllerCore~Service.WidgetDataSource→Core~SuggestionWidget.CodeSuggestionProviderCore~Service.WidgetDataSource→Core~SuggestionWidget.NESCodeSuggestionProvider
- 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
- 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.
25→30 Core~Service uses Core~XcodeThemeController part of a loop✕
- Connections
- 5 pairs of types, where a type in Core~Service uses a type in Core~XcodeThemeController.
- The types involved
Core~Service.NSError→Core~XcodeThemeController.ErrorCore~Service.NoAccessToAccessibilityAPIError→Core~XcodeThemeController.ErrorCore~Service.PresentInWindowSuggestionPresenter→Core~XcodeThemeController.ErrorCore~Service.Service→Core~XcodeThemeController.XcodeThemeControllerCore~Service.TelemetryLogger→Core~XcodeThemeController.Error
- 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
- 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.
25→31 Core~Service uses Tool~FileSystem part of a loop✕
- Connections
- 3 pairs of types, where a type in Core~Service uses a type in Tool~FileSystem.
- The types involved
Core~Service.PseudoCommandHandler→Tool~FileSystem.DateCore~Service.TelemetryLogger→Tool~FileSystem.StaticStringCore~Service.XPCService→Tool~FileSystem.StaticString
- Direction
- Core~Service uses Tool~FileSystem, so a change to Tool~FileSystem can break Core~Service, while a change to Core~Service 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.
25→33 Core~Service uses Core~HostApp part of a loop✕
- Connections
- 8 pairs of types, where a type in Core~Service uses a type in Core~HostApp.
- The types involved
Core~Service.GraphicalUserInterfaceController→Core~HostApp.StringCore~Service.NoAccessToAccessibilityAPIError→Core~HostApp.StringCore~Service.PresentInWindowSuggestionPresenter→Core~HostApp.StringCore~Service.Service→Core~HostApp.StringCore~Service.SuggestionCommandHandler→Core~HostApp.StringCore~Service.TelemetryLogger→Core~HostApp.StringCore~Service.WindowBaseCommandHandler→Core~HostApp.StringCore~Service.XPCService→Core~HostApp.String
- Direction
- Core~Service uses Core~HostApp, so a change to Core~HostApp can break Core~Service, while a change to Core~Service can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→38 Core~Service uses Core~ConversationTab part of a loop✕
- Connections
- 7 pairs of types, where a type in Core~Service uses a type in Core~ConversationTab.
- The types involved
Core~Service.Action→Core~ConversationTab.ActionCore~Service.PresentInWindowSuggestionPresenter→Core~ConversationTab.URLCore~Service.PseudoCommandHandler→Core~ConversationTab.URLCore~Service.Service→Core~ConversationTab.URLCore~Service.State→Core~ConversationTab.ChatHistoryCore~Service.State→Core~ConversationTab.StateCore~Service.WidgetDataSource→Core~ConversationTab.URL
- Direction
- Core~Service uses Core~ConversationTab, so a change to Core~ConversationTab can break Core~Service, while a change to Core~Service can't break Core~ConversationTab.
- Position
- 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→2 Tool~XPCShared uses Tool~Preferences✕
- Connections
- 7 pairs of types, where a type in Tool~XPCShared uses a type in Tool~Preferences.
- The types involved
Tool~XPCShared.EditorContent→Tool~Preferences.BoolTool~XPCShared.EditorContent→Tool~Preferences.IntTool~XPCShared.ExtensionServiceRequestType→Tool~Preferences.DataTool~XPCShared.XPCExtensionService→Tool~Preferences.BoolTool~XPCShared.XPCService→Tool~Preferences.BoolTool~XPCShared.XPCService.swift→Tool~Preferences.BoolTool~XPCShared.XPCServiceProtocol→Tool~Preferences.Data
- Direction
- 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.
26→6 Tool~XPCShared uses Tool~Logger✕
- Connections
- 3 pairs of types, where a type in Tool~XPCShared uses a type in Tool~Logger.
- The types involved
Tool~XPCShared.XPCCommunicationBridge→Tool~Logger.LoggerTool~XPCShared.XPCExtensionService→Tool~Logger.LoggerTool~XPCShared.XPCService→Tool~Logger.Logger
- Direction
- Tool~XPCShared uses Tool~Logger, so a change to Tool~Logger can break Tool~XPCShared, while a change to Tool~XPCShared can't break Tool~Logger.
- Position
- Below the diagonal: Tool~XPCShared uses a module listed above it, which is the healthy direction.
26→8 Tool~XPCShared uses Tool~SuggestionBasic✕
- Connections
- 4 pairs of types, where a type in Tool~XPCShared uses a type in Tool~SuggestionBasic.
- The types involved
Tool~XPCShared.EditorContent→Tool~SuggestionBasic.CursorPositionTool~XPCShared.Selection→Tool~SuggestionBasic.CursorPositionTool~XPCShared.UpdatedContent→Tool~SuggestionBasic.CursorRangeTool~XPCShared.UpdatedContent→Tool~SuggestionBasic.Modification
- 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.
26→17 Tool~XPCShared uses Tool~GitHubCopilotService✕
- Connections
- 17 pairs of types, where a type in Tool~XPCShared uses a type in Tool~GitHubCopilotService.
- The types involved
Tool~XPCShared.XPCExtensionService→Tool~GitHubCopilotService.BYOKDeleteApiKeyParamsTool~XPCShared.XPCExtensionService→Tool~GitHubCopilotService.BYOKDeleteModelParamsTool~XPCShared.XPCExtensionService→Tool~GitHubCopilotService.BYOKListApiKeysParamsTool~XPCShared.XPCExtensionService→Tool~GitHubCopilotService.BYOKListApiKeysResponseTool~XPCShared.XPCExtensionService→Tool~GitHubCopilotService.BYOKListModelsParamsTool~XPCShared.XPCExtensionService→Tool~GitHubCopilotService.BYOKListModelsResponseTool~XPCShared.XPCExtensionService→Tool~GitHubCopilotService.BYOKSaveApiKeyParamsTool~XPCShared.XPCExtensionService→Tool~GitHubCopilotService.BYOKSaveModelResponseTool~XPCShared.XPCExtensionService→Tool~GitHubCopilotService.CopilotPolicyTool~XPCShared.XPCExtensionService→Tool~GitHubCopilotService.FeatureFlagsTool~XPCShared.XPCExtensionService→Tool~GitHubCopilotService.GetMCPRegistryAllowlistResultTool~XPCShared.XPCExtensionService→Tool~GitHubCopilotService.MCPRegistryGetServerParamsTool~XPCShared.XPCExtensionService→Tool~GitHubCopilotService.MCPRegistryListServersParamsTool~XPCShared.XPCExtensionService→Tool~GitHubCopilotService.MCPRegistryServerDetailTool~XPCShared.XPCExtensionService→Tool~GitHubCopilotService.MCPRegistryServerListTool~XPCShared.XPCExtensionService→Tool~GitHubCopilotService.MCPServerToolsCollectionTool~XPCShared.XPCExtensionService→Tool~GitHubCopilotService.UpdateMCPToolsStatusServerCollection
- Direction
- Tool~XPCShared uses Tool~GitHubCopilotService, so a change to Tool~GitHubCopilotService can break Tool~XPCShared, while a change to Tool~XPCShared can't break Tool~GitHubCopilotService.
- Position
- Below the diagonal: Tool~XPCShared uses a module listed above it, which is the healthy direction.
26→18 Tool~XPCShared uses Tool~Status✕
- Connections
- 3 pairs of types, where a type in Tool~XPCShared uses a type in Tool~Status.
- The types involved
Tool~XPCShared.XPCExtensionService→Tool~Status.AuthStatusTool~XPCShared.XPCExtensionService→Tool~Status.ExtensionPermissionStatusTool~XPCShared.XPCExtensionService→Tool~Status.ObservedAXStatus
- Direction
- Tool~XPCShared uses Tool~Status, so a change to Tool~Status can break Tool~XPCShared, while a change to Tool~XPCShared can't break Tool~Status.
- Position
- Below the diagonal: Tool~XPCShared uses a module listed above it, which is the healthy direction.
26→20 Tool~XPCShared uses Tool~ChatAPIService✕
- Connections
- 1 pair of types, where a type in Tool~XPCShared uses a type in Tool~ChatAPIService.
- The types involved
Tool~XPCShared.XPCService→Tool~ChatAPIService.Kind
- Direction
- Tool~XPCShared uses Tool~ChatAPIService, so a change to Tool~ChatAPIService can break Tool~XPCShared, while a change to Tool~XPCShared can't break Tool~ChatAPIService.
- Position
- Below the diagonal: Tool~XPCShared uses a module listed above it, which is the healthy direction.
26→21 Tool~XPCShared uses Tool~ConversationServiceProvider✕
- Connections
- 5 pairs of types, where a type in Tool~XPCShared uses a type in Tool~ConversationServiceProvider.
- The types involved
Tool~XPCShared.XPCExtensionService→Tool~ConversationServiceProvider.ChatModeTool~XPCShared.XPCExtensionService→Tool~ConversationServiceProvider.ConversationModeTool~XPCShared.XPCExtensionService→Tool~ConversationServiceProvider.CopilotModelTool~XPCShared.XPCExtensionService→Tool~ConversationServiceProvider.LanguageModelToolTool~XPCShared.XPCExtensionService→Tool~ConversationServiceProvider.ToolStatusUpdate
- Direction
- Tool~XPCShared uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Tool~XPCShared, while a change to Tool~XPCShared can't break Tool~ConversationServiceProvider.
- Position
- Below the diagonal: Tool~XPCShared uses a module listed above it, which is the healthy direction.
26→25 Tool~XPCShared uses Core~Service✕
- Connections
- 1 pair of types, where a type in Tool~XPCShared uses a type in Core~Service.
- The types involved
Tool~XPCShared.XPCServiceActor→Core~Service.TheActor
- Direction
- Tool~XPCShared uses Core~Service, so a change to Core~Service can break Tool~XPCShared, while a change to Tool~XPCShared can't break Core~Service.
- Position
- Below the diagonal: Tool~XPCShared uses a module listed above it, which is the healthy direction.
26→27 Tool~XPCShared uses repository part of a loop✕
- Connections
- 3 pairs of types, where a type in Tool~XPCShared uses a type in repository.
- The types involved
Tool~XPCShared.EditorContent→repository.XCSourceEditorCommandInvocationTool~XPCShared.XPCCommunicationBridge→repository.XPCServiceTool~XPCShared.XPCExtensionService→repository.XPCService
- Direction
- 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.
26→30 Tool~XPCShared uses Core~XcodeThemeController part of a loop✕
- Connections
- 6 pairs of types, where a type in Tool~XPCShared uses a type in Core~XcodeThemeController.
- The types involved
Tool~XPCShared.AutoFinishContinuation→Core~XcodeThemeController.ErrorTool~XPCShared.NoDataError→Core~XcodeThemeController.ErrorTool~XPCShared.XPCCommunicationBridgeError→Core~XcodeThemeController.ErrorTool~XPCShared.XPCExtensionServiceError→Core~XcodeThemeController.ErrorTool~XPCShared.XPCRequestHandlerHitError→Core~XcodeThemeController.ErrorTool~XPCShared.XPCRequestNotHandledError→Core~XcodeThemeController.Error
- Direction
- Tool~XPCShared uses Core~XcodeThemeController, so a change to Core~XcodeThemeController can break Tool~XPCShared, while a change to Tool~XPCShared can't break Core~XcodeThemeController.
- 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→33 Tool~XPCShared uses Core~HostApp part of a loop✕
- Connections
- 14 pairs of types, where a type in Tool~XPCShared uses a type in Core~HostApp.
- The types involved
Tool~XPCShared.EditorContent→Core~HostApp.StringTool~XPCShared.ExtensionServiceRequestType→Core~HostApp.StringTool~XPCShared.GetExtensionSuggestionServices→Core~HostApp.StringTool~XPCShared.Models.swift→Core~HostApp.StringTool~XPCShared.OpenExtensionManager→Core~HostApp.StringTool~XPCShared.ServiceInfo→Core~HostApp.StringTool~XPCShared.UpdatedContent→Core~HostApp.StringTool~XPCShared.XPCCommunicationBridgeError→Core~HostApp.StringTool~XPCShared.XPCExtensionService→Core~HostApp.StringTool~XPCShared.XPCExtensionServiceError→Core~HostApp.StringTool~XPCShared.XPCRequestHandlerHitError→Core~HostApp.StringTool~XPCShared.XPCRequestNotHandledError→Core~HostApp.StringTool~XPCShared.XPCServiceProtocol→Core~HostApp.StringTool~XPCShared.XcodeInspectorData→Core~HostApp.String
- Direction
- Tool~XPCShared uses Core~HostApp, so a change to Core~HostApp can break Tool~XPCShared, while a change to Tool~XPCShared can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→2 repository uses Tool~Preferences✕
- Connections
- 4 pairs of types, where a type in repository uses a type in Tool~Preferences.
- The types involved
repository.ExtensionServiceLauncher→Tool~Preferences.Boolrepository.NSRunningApplication→Tool~Preferences.Boolrepository.ServiceDelegate→Tool~Preferences.Boolrepository.XCSourceEditorCommandInvocation→Tool~Preferences.Bool
- Direction
- repository uses Tool~Preferences, so a change to Tool~Preferences can break repository, while a change to repository can't break Tool~Preferences.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
27→4 repository uses Tool~ActiveApplicationMonitor✕
- Connections
- 1 pair of types, where a type in repository uses a type in Tool~ActiveApplicationMonitor.
- The types involved
repository.NSRunningApplication→Tool~ActiveApplicationMonitor.RunningApplicationInfo
- Direction
- 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.
27→8 repository uses Tool~SuggestionBasic✕
- Connections
- 1 pair of types, where a type in repository uses a type in Tool~SuggestionBasic.
- The types involved
repository.XCSourceEditorCommandInvocation→Tool~SuggestionBasic.Modification
- 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.
27→26 repository uses Tool~XPCShared✕
- Connections
- 4 pairs of types, where a type in repository uses a type in Tool~XPCShared.
- The types involved
repository.XCSourceEditorCommandInvocation→Tool~XPCShared.UpdatedContentrepository.XPCController→Tool~XPCShared.XPCCommunicationBridgerepository.XPCController→Tool~XPCShared.XPCServiceDelegaterepository.XPCService→Tool~XPCShared.CommunicationBridgeXPCServiceProtocol
- Direction
- repository uses Tool~XPCShared, so a change to Tool~XPCShared can break repository, while a change to repository can't break Tool~XPCShared.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
27→33 repository uses Core~HostApp part of a loop✕
- Connections
- 27 pairs of types, where a type in repository uses a type in Core~HostApp. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
repository.AcceptNESSuggestionCommand→Core~HostApp.Stringrepository.AcceptPromptToCodeCommand→Core~HostApp.Stringrepository.AcceptSuggestionCommand→Core~HostApp.Stringrepository.AppDelegate.swift→Core~HostApp.Stringrepository.CLSMessage→Core~HostApp.Stringrepository.CLSMessageType→Core~HostApp.Stringrepository.CloseIdleTabsCommand→Core~HostApp.Stringrepository.CommandType→Core~HostApp.Stringrepository.ContentView→Core~HostApp.Stringrepository.CustomCommand→Core~HostApp.Stringrepository.GetSuggestionsCommand→Core~HostApp.Stringrepository.NSMenuItem→Core~HostApp.Stringrepository.NextSuggestionCommand→Core~HostApp.Stringrepository.OpenChatCommand→Core~HostApp.Stringrepository.OpenSettingsCommand→Core~HostApp.Stringrepository.OpenSettingsCommand.swift→Core~HostApp.Stringrepository.PrefetchSuggestionsCommand→Core~HostApp.Stringrepository.PreviousSuggestionCommand→Core~HostApp.Stringrepository.PromptToCodeCommand→Core~HostApp.Stringrepository.RejectNESSuggestionCommand→Core~HostApp.Stringrepository.RejectSuggestionCommand→Core~HostApp.Stringrepository.ReloadLaunchAgent→Core~HostApp.Stringrepository.ReloadLaunchAgent.swift→Core~HostApp.Stringrepository.SeparatorCommand→Core~HostApp.Stringrepository.SyncTextSettingsCommand→Core~HostApp.String
- Direction
- repository uses Core~HostApp, so a change to Core~HostApp can break repository, while a change to repository can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→38 repository uses Core~ConversationTab part of a loop✕
- Connections
- 2 pairs of types, where a type in repository uses a type in Core~ConversationTab.
- The types involved
repository.ContentView→Core~ConversationTab.Viewrepository.ReloadLaunchAgent→Core~ConversationTab.URL
- Direction
- repository uses Core~ConversationTab, so a change to Core~ConversationTab can break repository, while a change to repository can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→2 Tool~AXExtension uses Tool~Preferences✕
- Connections
- 3 pairs of types, where a type in Tool~AXExtension uses a type in Tool~Preferences.
- The types involved
Tool~AXExtension.AXUIElement→Tool~Preferences.BoolTool~AXExtension.AXUIElement→Tool~Preferences.DoubleTool~AXExtension.AXUIElement→Tool~Preferences.Int
- Direction
- 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.
28→27 Tool~AXExtension uses repository✕
- Connections
- 1 pair of types, where a type in Tool~AXExtension uses a type in repository.
- The types involved
Tool~AXExtension.AXUIElement→repository.NSRunningApplication
- Direction
- Tool~AXExtension uses repository, so a change to repository can break Tool~AXExtension, while a change to Tool~AXExtension can't break repository.
- Position
- Below the diagonal: Tool~AXExtension uses a module listed above it, which is the healthy direction.
28→33 Tool~AXExtension uses Core~HostApp part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~AXExtension uses a type in Core~HostApp.
- The types involved
Tool~AXExtension.AXUIElement→Core~HostApp.String
- Direction
- Tool~AXExtension uses Core~HostApp, so a change to Core~HostApp can break Tool~AXExtension, while a change to Tool~AXExtension can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→38 Tool~AXExtension uses Core~ConversationTab part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~AXExtension uses a type in Core~ConversationTab.
- The types involved
Tool~AXExtension.AXUIElement→Core~ConversationTab.URL
- Direction
- Tool~AXExtension uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~AXExtension, while a change to Tool~AXExtension can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→1 Core~SuggestionWidget uses Core~UserDefaultsObserver✕
- Connections
- 1 pair of types, where a type in Core~SuggestionWidget uses a type in Core~UserDefaultsObserver.
- The types involved
Core~SuggestionWidget.WidgetUserDefaultsObservers→Core~UserDefaultsObserver.UserDefaultsObserver
- Direction
- Core~SuggestionWidget uses Core~UserDefaultsObserver, so a change to Core~UserDefaultsObserver can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Core~UserDefaultsObserver.
- Position
- Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
29→2 Core~SuggestionWidget uses Tool~Preferences✕
- Connections
- 74 pairs of types, where a type in Core~SuggestionWidget uses a type in Tool~Preferences. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Core~SuggestionWidget.AgentBuiltInToolsSection→Tool~Preferences.BoolCore~SuggestionWidget.AgentConfigurationWidgetView→Tool~Preferences.BoolCore~SuggestionWidget.AgentConfigurationWidgetView→Tool~Preferences.IntCore~SuggestionWidget.AgentMCPServerSection→Tool~Preferences.BoolCore~SuggestionWidget.AgentModelPickerSection→Tool~Preferences.BoolCore~SuggestionWidget.AgentToolRow→Tool~Preferences.BoolCore~SuggestionWidget.AlignToTextCursor→Tool~Preferences.BoolCore~SuggestionWidget.AlignToTextCursor→Tool~Preferences.DoubleCore~SuggestionWidget.CanBecomeKeyWindow→Tool~Preferences.BoolCore~SuggestionWidget.ChatBar→Tool~Preferences.BoolCore~SuggestionWidget.ChatHistoryButton→Tool~Preferences.BoolCore~SuggestionWidget.ChatHistoryItemView→Tool~Preferences.BoolCore~SuggestionWidget.ChatHistorySearchBarView→Tool~Preferences.BoolCore~SuggestionWidget.ChatHistoryView→Tool~Preferences.BoolCore~SuggestionWidget.ChatHistoryViewWrapper→Tool~Preferences.BoolCore~SuggestionWidget.ChatPanelWindow→Tool~Preferences.BoolCore~SuggestionWidget.ChatTabBarButton→Tool~Preferences.BoolCore~SuggestionWidget.ChatTabKind→Tool~Preferences.BoolCore~SuggestionWidget.ChatTitleBar→Tool~Preferences.BoolCore~SuggestionWidget.ChatView→Tool~Preferences.BoolCore~SuggestionWidget.ChatWindowView→Tool~Preferences.BoolCore~SuggestionWidget.ChatWorkspace→Tool~Preferences.BoolCore~SuggestionWidget.ChatWorkspace→Tool~Preferences.IntCore~SuggestionWidget.CircularWidgetState→Tool~Preferences.BoolCore~SuggestionWidget.CodeBlockSuggestionPanel→Tool~Preferences.Bool
- Direction
- 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.
29→8 Core~SuggestionWidget uses Tool~SuggestionBasic✕
- Connections
- 4 pairs of types, where a type in Core~SuggestionWidget uses a type in Tool~SuggestionBasic.
- The types involved
Core~SuggestionWidget.CursorPositionTracker→Tool~SuggestionBasic.CursorPositionCore~SuggestionWidget.NESCodeSuggestionProvider→Tool~SuggestionBasic.CursorRangeCore~SuggestionWidget.PromptToCodeInitialState→Tool~SuggestionBasic.CodeLanguageCore~SuggestionWidget.PromptToCodeInitialState→Tool~SuggestionBasic.CursorRange
- 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.
29→12 Core~SuggestionWidget uses Tool~ChatTab✕
- Connections
- 11 pairs of types, where a type in Core~SuggestionWidget uses a type in Tool~ChatTab.
- The types involved
Core~SuggestionWidget.ChatHistoryItemView→Tool~ChatTab.ChatTabPreviewInfoCore~SuggestionWidget.ChatHistoryView_Previews→Tool~ChatTab.ChatTabPoolCore~SuggestionWidget.ChatPanelWindow→Tool~ChatTab.ChatTabPoolCore~SuggestionWidget.ChatTabBarButton→Tool~ChatTab.ChatTabInfoCore~SuggestionWidget.ChatTabKind→Tool~ChatTab.ChatTabBuilderCore~SuggestionWidget.ChatWindowView_Previews→Tool~ChatTab.ChatTabPoolCore~SuggestionWidget.ChatWorkspace→Tool~ChatTab.ChatTabInfoCore~SuggestionWidget.ItemView→Tool~ChatTab.ChatTabPreviewInfoCore~SuggestionWidget.SuggestionWidgetController→Tool~ChatTab.ChatTabPoolCore~SuggestionWidget.WidgetWindows→Tool~ChatTab.ChatTabPoolCore~SuggestionWidget.WidgetWindowsController→Tool~ChatTab.ChatTabPool
- Direction
- Core~SuggestionWidget uses Tool~ChatTab, so a change to Tool~ChatTab can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~ChatTab.
- Position
- Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
29→16 Core~SuggestionWidget uses Tool~WorkspaceSuggestionService✕
- Connections
- 1 pair of types, where a type in Core~SuggestionWidget uses a type in Tool~WorkspaceSuggestionService.
- The types involved
Core~SuggestionWidget.NESCodeSuggestionProvider→Tool~WorkspaceSuggestionService.FilespaceSuggestionSnapshot
- Direction
- Core~SuggestionWidget uses Tool~WorkspaceSuggestionService, so a change to Tool~WorkspaceSuggestionService can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~WorkspaceSuggestionService.
- Position
- Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
29→17 Core~SuggestionWidget uses Tool~GitHubCopilotService✕
- Connections
- 4 pairs of types, where a type in Core~SuggestionWidget uses a type in Tool~GitHubCopilotService.
- The types involved
Core~SuggestionWidget.AgentConfigurationWidgetView→Tool~GitHubCopilotService.GitHubCopilotServiceCore~SuggestionWidget.AgentConfigurationWidgetView→Tool~GitHubCopilotService.UpdateMCPToolsStatusServerCollectionCore~SuggestionWidget.AgentMCPServerSection→Tool~GitHubCopilotService.MCPServerToolsCollectionCore~SuggestionWidget.AgentMCPServerSection→Tool~GitHubCopilotService.MCPTool
- Direction
- Core~SuggestionWidget uses Tool~GitHubCopilotService, so a change to Tool~GitHubCopilotService can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~GitHubCopilotService.
- Position
- Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
29→18 Core~SuggestionWidget uses Tool~Status✕
- Connections
- 1 pair of types, where a type in Core~SuggestionWidget uses a type in Tool~Status.
- The types involved
Core~SuggestionWidget.QuotaButton→Tool~Status.GitHubCopilotQuotaInfo
- Direction
- Core~SuggestionWidget uses Tool~Status, so a change to Tool~Status can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~Status.
- Position
- Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
29→19 Core~SuggestionWidget uses Tool~XcodeInspector✕
- Connections
- 8 pairs of types, where a type in Core~SuggestionWidget uses a type in Tool~XcodeInspector.
- The types involved
Core~SuggestionWidget.AgentConfigurationWidgetFeature.swift→Tool~XcodeInspector.SourceEditorCore~SuggestionWidget.CursorPositionTracker→Tool~XcodeInspector.SourceEditorCore~SuggestionWidget.State→Tool~XcodeInspector.SourceEditorCore~SuggestionWidget.WidgetWindowsController→Tool~XcodeInspector.AXNotificationCore~SuggestionWidget.WidgetWindowsController→Tool~XcodeInspector.AppInstanceInspectorCore~SuggestionWidget.WidgetWindowsController→Tool~XcodeInspector.SourceEditorCore~SuggestionWidget.WidgetWindowsController→Tool~XcodeInspector.XcodeAppInstanceInspectorCore~SuggestionWidget.WidgetWindowsController→Tool~XcodeInspector.XcodeInspector
- Direction
- Core~SuggestionWidget uses Tool~XcodeInspector, so a change to Tool~XcodeInspector can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~XcodeInspector.
- Position
- Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
29→21 Core~SuggestionWidget uses Tool~ConversationServiceProvider✕
- Connections
- 14 pairs of types, where a type in Core~SuggestionWidget uses a type in Tool~ConversationServiceProvider.
- The types involved
Core~SuggestionWidget.AgentBuiltInToolsSection→Tool~ConversationServiceProvider.ConversationModeCore~SuggestionWidget.AgentBuiltInToolsSection→Tool~ConversationServiceProvider.LanguageModelToolCore~SuggestionWidget.AgentConfigurationWidgetFeature.swift→Tool~ConversationServiceProvider.ConversationModeCore~SuggestionWidget.AgentConfigurationWidgetView→Tool~ConversationServiceProvider.ChatModeCore~SuggestionWidget.AgentConfigurationWidgetView→Tool~ConversationServiceProvider.ConversationModeCore~SuggestionWidget.AgentConfigurationWidgetView→Tool~ConversationServiceProvider.ToolStatusUpdateCore~SuggestionWidget.AgentMCPServerSection→Tool~ConversationServiceProvider.ConversationModeCore~SuggestionWidget.AgentToolsSection→Tool~ConversationServiceProvider.ConversationModeCore~SuggestionWidget.CodeReviewLocationStrategy→Tool~ConversationServiceProvider.ReviewCommentCore~SuggestionWidget.CommentDetailView→Tool~ConversationServiceProvider.ReviewCommentCore~SuggestionWidget.ContentView→Tool~ConversationServiceProvider.ReviewCommentCore~SuggestionWidget.DiffSegment→Tool~ConversationServiceProvider.ChangeCore~SuggestionWidget.State→Tool~ConversationServiceProvider.ConversationModeCore~SuggestionWidget.ViewState→Tool~ConversationServiceProvider.ReviewComment
- Direction
- Core~SuggestionWidget uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~ConversationServiceProvider.
- Position
- Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
29→22 Core~SuggestionWidget uses Tool~SharedUIComponents✕
- Connections
- 3 pairs of types, where a type in Core~SuggestionWidget uses a type in Tool~SharedUIComponents.
- The types involved
Core~SuggestionWidget.AgentBuiltInToolsSection→Tool~SharedUIComponents.CheckboxMixedStateCore~SuggestionWidget.AgentMCPServerSection→Tool~SharedUIComponents.CheckboxMixedStateCore~SuggestionWidget.ChatPanelWindow→Tool~SharedUIComponents.FontScaleManager
- Direction
- Core~SuggestionWidget uses Tool~SharedUIComponents, so a change to Tool~SharedUIComponents can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~SharedUIComponents.
- Position
- Below the diagonal: Core~SuggestionWidget uses a module listed above it, which is the healthy direction.
29→27 Core~SuggestionWidget uses repository✕
- Connections
- 3 pairs of types, where a type in Core~SuggestionWidget uses a type in repository.
- The types involved
Core~SuggestionWidget.CursorPositionTracker→repository.TaskCore~SuggestionWidget.NESMenuController→repository.NSMenuItemCore~SuggestionWidget.WidgetWindowsController→repository.Task
- 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.
29→28 Core~SuggestionWidget uses Tool~AXExtension✕
- Connections
- 8 pairs of types, where a type in Core~SuggestionWidget uses a type in Tool~AXExtension.
- The types involved
Core~SuggestionWidget.AgentConfigurationWidgetLocationStrategy→Tool~AXExtension.AXUIElementCore~SuggestionWidget.AlignToTextCursor→Tool~AXExtension.AXUIElementCore~SuggestionWidget.CodeReviewLocationStrategy→Tool~AXExtension.AXUIElementCore~SuggestionWidget.LocationStrategyHelper→Tool~AXExtension.AXUIElementCore~SuggestionWidget.NESPanelLocationStrategy→Tool~AXExtension.AXUIElementCore~SuggestionWidget.NearbyTextCursor→Tool~AXExtension.AXUIElementCore~SuggestionWidget.UpdateLocationStrategy→Tool~AXExtension.AXUIElementCore~SuggestionWidget.WidgetWindowsController→Tool~AXExtension.AXUIElement
- 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.
29→31 Core~SuggestionWidget uses Tool~FileSystem part of a loop✕
- Connections
- 5 pairs of types, where a type in Core~SuggestionWidget uses a type in Tool~FileSystem.
- The types involved
Core~SuggestionWidget.ChatHistoryItemView→Tool~FileSystem.DateCore~SuggestionWidget.DonutShape→Tool~FileSystem.PathCore~SuggestionWidget.PieSlice→Tool~FileSystem.PathCore~SuggestionWidget.WidgetWindowsController→Tool~FileSystem.DateCore~SuggestionWidget.WidgetWindowsController→Tool~FileSystem.StaticString
- Direction
- Core~SuggestionWidget uses Tool~FileSystem, so a change to Tool~FileSystem can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Tool~FileSystem.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→32 Core~SuggestionWidget uses Core~GitHubCopilotViewModel part of a loop✕
- Connections
- 2 pairs of types, where a type in Core~SuggestionWidget uses a type in Core~GitHubCopilotViewModel.
- The types involved
Core~SuggestionWidget.ChatLoginView→Core~GitHubCopilotViewModel.GitHubCopilotViewModelCore~SuggestionWidget.ChatNoSubscriptionView→Core~GitHubCopilotViewModel.GitHubCopilotViewModel
- Direction
- Core~SuggestionWidget uses Core~GitHubCopilotViewModel, so a change to Core~GitHubCopilotViewModel can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Core~GitHubCopilotViewModel.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→33 Core~SuggestionWidget uses Core~HostApp part of a loop✕
- Connections
- 42 pairs of types, where a type in Core~SuggestionWidget uses a type in Core~HostApp. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Core~SuggestionWidget.AgentBuiltInToolsSection→Core~HostApp.StringCore~SuggestionWidget.AgentConfigurationWidgetView→Core~HostApp.StringCore~SuggestionWidget.AgentFileAccess→Core~HostApp.StringCore~SuggestionWidget.AgentMCPServerSection→Core~HostApp.StringCore~SuggestionWidget.AgentModelPickerSection→Core~HostApp.StringCore~SuggestionWidget.AgentToolRow→Core~HostApp.StringCore~SuggestionWidget.AgentToolsSection→Core~HostApp.StringCore~SuggestionWidget.ChatHistory→Core~HostApp.StringCore~SuggestionWidget.ChatHistoryItemView→Core~HostApp.StringCore~SuggestionWidget.ChatHistorySearchBarView→Core~HostApp.StringCore~SuggestionWidget.ChatHistoryView→Core~HostApp.StringCore~SuggestionWidget.ChatPanelFeature→Core~HostApp.StringCore~SuggestionWidget.ChatTabContainer→Core~HostApp.StringCore~SuggestionWidget.ChatTabKind→Core~HostApp.StringCore~SuggestionWidget.ChatWorkspace→Core~HostApp.StringCore~SuggestionWidget.CodeReviewFeature.swift→Core~HostApp.StringCore~SuggestionWidget.CodeReviewLocationStrategy→Core~HostApp.StringCore~SuggestionWidget.CodeSuggestionProvider→Core~HostApp.StringCore~SuggestionWidget.CommandButtonStyle→Core~HostApp.ButtonStyleCore~SuggestionWidget.CommentDetailView→Core~HostApp.StringCore~SuggestionWidget.CopilotIntroItemView→Core~HostApp.StringCore~SuggestionWidget.DiffBuilder→Core~HostApp.StringCore~SuggestionWidget.DiffLine→Core~HostApp.StringCore~SuggestionWidget.DiffLineView→Core~HostApp.StringCore~SuggestionWidget.DiffSegment→Core~HostApp.String
- Direction
- Core~SuggestionWidget uses Core~HostApp, so a change to Core~HostApp can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→38 Core~SuggestionWidget uses Core~ConversationTab part of a loop✕
- Connections
- 100 pairs of types, where a type in Core~SuggestionWidget uses a type in Core~ConversationTab. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Core~SuggestionWidget.AccentStrip→Core~ConversationTab.ViewCore~SuggestionWidget.AgentBuiltInToolsSection→Core~ConversationTab.ViewCore~SuggestionWidget.AgentConfigurationWidgetView→Core~ConversationTab.URLCore~SuggestionWidget.AgentConfigurationWidgetView→Core~ConversationTab.ViewCore~SuggestionWidget.AgentFileAccess→Core~ConversationTab.URLCore~SuggestionWidget.AgentMCPServerSection→Core~ConversationTab.ViewCore~SuggestionWidget.AgentModelPickerSection→Core~ConversationTab.LLMModelCore~SuggestionWidget.AgentModelPickerSection→Core~ConversationTab.ViewCore~SuggestionWidget.AgentToolRow→Core~ConversationTab.ViewCore~SuggestionWidget.AgentToolsSection→Core~ConversationTab.ViewCore~SuggestionWidget.ChatBar→Core~ConversationTab.ViewCore~SuggestionWidget.ChatHistoryButton→Core~ConversationTab.ViewCore~SuggestionWidget.ChatHistoryItemView→Core~ConversationTab.ViewCore~SuggestionWidget.ChatHistorySearchBarView→Core~ConversationTab.ViewCore~SuggestionWidget.ChatHistoryView→Core~ConversationTab.ViewCore~SuggestionWidget.ChatHistoryViewWrapper→Core~ConversationTab.ViewCore~SuggestionWidget.ChatHistoryView_Previews→Core~ConversationTab.ViewCore~SuggestionWidget.ChatLoadingView→Core~ConversationTab.ViewCore~SuggestionWidget.ChatLoadingView_Previews→Core~ConversationTab.ViewCore~SuggestionWidget.ChatLoginView→Core~ConversationTab.ViewCore~SuggestionWidget.ChatLoginView_Previews→Core~ConversationTab.ViewCore~SuggestionWidget.ChatNoAXPermissionView→Core~ConversationTab.ViewCore~SuggestionWidget.ChatNoAXPermission_Previews→Core~ConversationTab.ViewCore~SuggestionWidget.ChatNoSubcription_Previews→Core~ConversationTab.ViewCore~SuggestionWidget.ChatNoSubscriptionView→Core~ConversationTab.View
- Direction
- Core~SuggestionWidget uses Core~ConversationTab, so a change to Core~ConversationTab can break Core~SuggestionWidget, while a change to Core~SuggestionWidget can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→2 Core~XcodeThemeController uses Tool~Preferences✕
- Connections
- 7 pairs of types, where a type in Core~XcodeThemeController uses a type in Tool~Preferences.
- The types involved
Core~XcodeThemeController.HighlightrThemeManager→Tool~Preferences.BoolCore~XcodeThemeController.ThemeColor→Tool~Preferences.DoubleCore~XcodeThemeController.ThemeColor→Tool~Preferences.StorableColorCore~XcodeThemeController.ThemeFont→Tool~Preferences.DoubleCore~XcodeThemeController.ThemeFont→Tool~Preferences.StorableFontCore~XcodeThemeController.XcodeThemeController→Tool~Preferences.BoolCore~XcodeThemeController.XcodeThemeParser→Tool~Preferences.Data
- 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.
30→27 Core~XcodeThemeController uses repository✕
- Connections
- 1 pair of types, where a type in Core~XcodeThemeController uses a type in repository.
- The types involved
Core~XcodeThemeController.XcodeThemeController→repository.Task
- 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.
30→29 Core~XcodeThemeController uses Core~SuggestionWidget✕
- Connections
- 1 pair of types, where a type in Core~XcodeThemeController uses a type in Core~SuggestionWidget.
- The types involved
Core~XcodeThemeController.HighlightrThemeManager→Core~SuggestionWidget.Theme
- 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.
30→33 Core~XcodeThemeController uses Core~HostApp part of a loop✕
- Connections
- 6 pairs of types, where a type in Core~XcodeThemeController uses a type in Core~HostApp.
- The types involved
Core~XcodeThemeController.HighlightJSThemeTemplate.swift→Core~HostApp.StringCore~XcodeThemeController.HighlightrThemeManager→Core~HostApp.StringCore~XcodeThemeController.ThemeColor→Core~HostApp.StringCore~XcodeThemeController.ThemeFont→Core~HostApp.StringCore~XcodeThemeController.XcodeTheme→Core~HostApp.StringCore~XcodeThemeController.XcodeThemeController→Core~HostApp.String
- Direction
- Core~XcodeThemeController uses Core~HostApp, so a change to Core~HostApp can break Core~XcodeThemeController, while a change to Core~XcodeThemeController can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→38 Core~XcodeThemeController uses Core~ConversationTab part of a loop✕
- Connections
- 3 pairs of types, where a type in Core~XcodeThemeController uses a type in Core~ConversationTab.
- The types involved
Core~XcodeThemeController.XcodeTheme→Core~ConversationTab.URLCore~XcodeThemeController.XcodeThemeController→Core~ConversationTab.URLCore~XcodeThemeController.XcodeThemeParser→Core~ConversationTab.URL
- Direction
- Core~XcodeThemeController uses Core~ConversationTab, so a change to Core~ConversationTab can break Core~XcodeThemeController, while a change to Core~XcodeThemeController can't break Core~ConversationTab.
- Position
- 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.
31→2 Tool~FileSystem uses Tool~Preferences✕
- Connections
- 28 pairs of types, where a type in Tool~FileSystem uses a type in Tool~Preferences. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Tool~FileSystem.AbsolutePath→Tool~Preferences.BoolTool~FileSystem.BufferedOutputByteStream→Tool~Preferences.IntTool~FileSystem.ByteString→Tool~Preferences.IntTool~FileSystem.FileLock→Tool~Preferences.BoolTool~FileSystem.FileSystem→Tool~Preferences.BoolTool~FileSystem.FileSystem→Tool~Preferences.DataTool~FileSystem.Format→Tool~Preferences.BoolTool~FileSystem.Format→Tool~Preferences.DoubleTool~FileSystem.Format→Tool~Preferences.IntTool~FileSystem.InMemoryFileSystem→Tool~Preferences.BoolTool~FileSystem.InMemoryFileSystem→Tool~Preferences.DataTool~FileSystem.JSONEscapedBoolStreamable→Tool~Preferences.BoolTool~FileSystem.JSONEscapedDoubleStreamable→Tool~Preferences.DoubleTool~FileSystem.JSONEscapedIntStreamable→Tool~Preferences.IntTool~FileSystem.LocalFileOutputByteStream→Tool~Preferences.BoolTool~FileSystem.LocalFileSystem→Tool~Preferences.BoolTool~FileSystem.LocalFileSystem→Tool~Preferences.DataTool~FileSystem.Option→Tool~Preferences.IntTool~FileSystem.Path→Tool~Preferences.BoolTool~FileSystem.Path.swift→Tool~Preferences.BoolTool~FileSystem.PathShim.swift→Tool~Preferences.BoolTool~FileSystem.RepeatingStringStreamable→Tool~Preferences.IntTool~FileSystem.ThreadSafeOutputByteStream→Tool~Preferences.IntTool~FileSystem.UNIXPath→Tool~Preferences.BoolTool~FileSystem.WindowsPath→Tool~Preferences.Bool
- Direction
- 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.
31→17 Tool~FileSystem uses Tool~GitHubCopilotService✕
- Connections
- 1 pair of types, where a type in Tool~FileSystem uses a type in Tool~GitHubCopilotService.
- The types involved
Tool~FileSystem.CodableRange→Tool~GitHubCopilotService.Range
- Direction
- Tool~FileSystem uses Tool~GitHubCopilotService, so a change to Tool~GitHubCopilotService can break Tool~FileSystem, while a change to Tool~FileSystem can't break Tool~GitHubCopilotService.
- Position
- Below the diagonal: Tool~FileSystem uses a module listed above it, which is the healthy direction.
31→20 Tool~FileSystem uses Tool~ChatAPIService✕
- Connections
- 1 pair of types, where a type in Tool~FileSystem uses a type in Tool~ChatAPIService.
- The types involved
Tool~FileSystem.FileSystemError→Tool~ChatAPIService.Kind
- Direction
- Tool~FileSystem uses Tool~ChatAPIService, so a change to Tool~ChatAPIService can break Tool~FileSystem, while a change to Tool~FileSystem can't break Tool~ChatAPIService.
- Position
- Below the diagonal: Tool~FileSystem uses a module listed above it, which is the healthy direction.
31→30 Tool~FileSystem uses Core~XcodeThemeController✕
- Connections
- 4 pairs of types, where a type in Tool~FileSystem uses a type in Core~XcodeThemeController.
- The types involved
Tool~FileSystem.FileSystemError→Core~XcodeThemeController.ErrorTool~FileSystem.PathValidationError→Core~XcodeThemeController.ErrorTool~FileSystem.ProcessLockError→Core~XcodeThemeController.ErrorTool~FileSystem.SystemError→Core~XcodeThemeController.Error
- Direction
- Tool~FileSystem uses Core~XcodeThemeController, so a change to Core~XcodeThemeController can break Tool~FileSystem, while a change to Tool~FileSystem can't break Core~XcodeThemeController.
- Position
- Below the diagonal: Tool~FileSystem uses a module listed above it, which is the healthy direction.
31→33 Tool~FileSystem uses Core~HostApp part of a loop✕
- Connections
- 22 pairs of types, where a type in Tool~FileSystem uses a type in Core~HostApp.
- The types involved
Tool~FileSystem.AbsolutePath→Core~HostApp.StringTool~FileSystem.ByteString→Core~HostApp.StringTool~FileSystem.CStringArray→Core~HostApp.StringTool~FileSystem.FileLock→Core~HostApp.StringTool~FileSystem.FileSystem→Core~HostApp.StringTool~FileSystem.FileSystemAttribute→Core~HostApp.StringTool~FileSystem.Format→Core~HostApp.StringTool~FileSystem.JSONEscapedStringListStreamable→Core~HostApp.StringTool~FileSystem.JSONEscapedStringStreamable→Core~HostApp.StringTool~FileSystem.Misc.swift→Core~HostApp.StringTool~FileSystem.Path→Core~HostApp.StringTool~FileSystem.Path.swift→Core~HostApp.StringTool~FileSystem.PathValidationError→Core~HostApp.StringTool~FileSystem.RelativePath→Core~HostApp.StringTool~FileSystem.RepeatingStringStreamable→Core~HostApp.StringTool~FileSystem.SeparatedListStreamable→Core~HostApp.StringTool~FileSystem.SystemError→Core~HostApp.StringTool~FileSystem.ThreadSafeOutputByteStream→Core~HostApp.StringTool~FileSystem.TransformedSeparatedListStreamable→Core~HostApp.StringTool~FileSystem.UNIXPath→Core~HostApp.StringTool~FileSystem.WindowsPath→Core~HostApp.StringTool~FileSystem.WritableByteStream→Core~HostApp.String
- Direction
- Tool~FileSystem uses Core~HostApp, so a change to Core~HostApp can break Tool~FileSystem, while a change to Tool~FileSystem can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→38 Tool~FileSystem uses Core~ConversationTab part of a loop✕
- Connections
- 1 pair of types, where a type in Tool~FileSystem uses a type in Core~ConversationTab.
- The types involved
Tool~FileSystem.AbsolutePath→Core~ConversationTab.URL
- Direction
- Tool~FileSystem uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~FileSystem, while a change to Tool~FileSystem can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→2 Core~GitHubCopilotViewModel uses Tool~Preferences✕
- Connections
- 1 pair of types, where a type in Core~GitHubCopilotViewModel uses a type in Tool~Preferences.
- The types involved
Core~GitHubCopilotViewModel.GitHubCopilotViewModel→Tool~Preferences.Bool
- Direction
- Core~GitHubCopilotViewModel uses Tool~Preferences, so a change to Tool~Preferences can break Core~GitHubCopilotViewModel, while a change to Core~GitHubCopilotViewModel can't break Tool~Preferences.
- Position
- Below the diagonal: Core~GitHubCopilotViewModel uses a module listed above it, which is the healthy direction.
32→17 Core~GitHubCopilotViewModel uses Tool~GitHubCopilotService✕
- Connections
- 4 pairs of types, where a type in Core~GitHubCopilotViewModel uses a type in Tool~GitHubCopilotService.
- The types involved
Core~GitHubCopilotViewModel.GitHubCopilotViewModel→Tool~GitHubCopilotService.GitHubCopilotAccountStatusCore~GitHubCopilotViewModel.GitHubCopilotViewModel→Tool~GitHubCopilotService.GitHubCopilotErrorCore~GitHubCopilotViewModel.GitHubCopilotViewModel→Tool~GitHubCopilotService.GitHubCopilotServiceCore~GitHubCopilotViewModel.SignInResponse→Tool~GitHubCopilotService.SignInInitiateStatus
- Direction
- Core~GitHubCopilotViewModel uses Tool~GitHubCopilotService, so a change to Tool~GitHubCopilotService can break Core~GitHubCopilotViewModel, while a change to Core~GitHubCopilotViewModel can't break Tool~GitHubCopilotService.
- Position
- Below the diagonal: Core~GitHubCopilotViewModel uses a module listed above it, which is the healthy direction.
32→31 Core~GitHubCopilotViewModel uses Tool~FileSystem✕
- Connections
- 1 pair of types, where a type in Core~GitHubCopilotViewModel uses a type in Tool~FileSystem.
- The types involved
Core~GitHubCopilotViewModel.GitHubCopilotViewModel→Tool~FileSystem.Date
- Direction
- Core~GitHubCopilotViewModel uses Tool~FileSystem, so a change to Tool~FileSystem can break Core~GitHubCopilotViewModel, while a change to Core~GitHubCopilotViewModel can't break Tool~FileSystem.
- Position
- Below the diagonal: Core~GitHubCopilotViewModel uses a module listed above it, which is the healthy direction.
32→33 Core~GitHubCopilotViewModel uses Core~HostApp part of a loop✕
- Connections
- 2 pairs of types, where a type in Core~GitHubCopilotViewModel uses a type in Core~HostApp.
- The types involved
Core~GitHubCopilotViewModel.GitHubCopilotViewModel→Core~HostApp.StringCore~GitHubCopilotViewModel.SignInResponse→Core~HostApp.String
- Direction
- Core~GitHubCopilotViewModel uses Core~HostApp, so a change to Core~HostApp can break Core~GitHubCopilotViewModel, while a change to Core~GitHubCopilotViewModel can't break Core~HostApp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→38 Core~GitHubCopilotViewModel uses Core~ConversationTab part of a loop✕
- Connections
- 1 pair of types, where a type in Core~GitHubCopilotViewModel uses a type in Core~ConversationTab.
- The types involved
Core~GitHubCopilotViewModel.SignInResponse→Core~ConversationTab.URL
- Direction
- Core~GitHubCopilotViewModel uses Core~ConversationTab, so a change to Core~ConversationTab can break Core~GitHubCopilotViewModel, while a change to Core~GitHubCopilotViewModel can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→2 Core~HostApp uses Tool~Preferences✕
- Connections
- 73 pairs of types, where a type in Core~HostApp uses a type in Tool~Preferences. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Core~HostApp.AgentFileSetting→Tool~Preferences.BoolCore~HostApp.AgentModeDescriptionView→Tool~Preferences.BoolCore~HostApp.ApiKeySheet→Tool~Preferences.BoolCore~HostApp.AppInfoView→Tool~Preferences.BoolCore~HostApp.AutoApproveContainerView→Tool~Preferences.BoolCore~HostApp.BYOKConfigView→Tool~Preferences.IntCore~HostApp.BYOKModelManagerObservable→Tool~Preferences.BoolCore~HostApp.BYOKProviderConfigView→Tool~Preferences.BoolCore~HostApp.BYOKServiceActor→Tool~Preferences.BoolCore~HostApp.Badge→Tool~Preferences.BoolCore~HostApp.BadgeItem→Tool~Preferences.BoolCore~HostApp.BuiltInToolsListView→Tool~Preferences.BoolCore~HostApp.CopilotInstructionSetting→Tool~Preferences.BoolCore~HostApp.CopilotPolicyManager→Tool~Preferences.BoolCore~HostApp.DependencyValues→Tool~Preferences.UserDefaultsTypeCore~HostApp.DisabledLanguageList→Tool~Preferences.BoolCore~HostApp.DisclosureSettingsRow→Tool~Preferences.BoolCore~HostApp.EditableText→Tool~Preferences.BoolCore~HostApp.EditsAutoApproveView→Tool~Preferences.BoolCore~HostApp.EnvironmentValues→Tool~Preferences.IntCore~HostApp.FeatureFlagManager→Tool~Preferences.BoolCore~HostApp.FontSizeSetting→Tool~Preferences.DoubleCore~HostApp.GeneralSettingsView→Tool~Preferences.BoolCore~HostApp.InstallationOption→Tool~Preferences.BoolCore~HostApp.LoggingSection→Tool~Preferences.Bool
- Direction
- 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.
33→4 Core~HostApp uses Tool~ActiveApplicationMonitor✕
- Connections
- 1 pair of types, where a type in Core~HostApp uses a type in Tool~ActiveApplicationMonitor.
- The types involved
Core~HostApp.DependencyValues→Tool~ActiveApplicationMonitor.ActiveApplicationMonitor
- 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.
33→7 Core~HostApp uses Tool~Persist✕
- Connections
- 1 pair of types, where a type in Core~HostApp uses a type in Tool~Persist.
- The types involved
Core~HostApp.String→Tool~Persist.Blob
- Direction
- Core~HostApp uses Tool~Persist, so a change to Tool~Persist can break Core~HostApp, while a change to Core~HostApp can't break Tool~Persist.
- Position
- Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
33→8 Core~HostApp uses Tool~SuggestionBasic✕
- Connections
- 1 pair of types, where a type in Core~HostApp uses a type in Tool~SuggestionBasic.
- The types involved
Core~HostApp.String→Tool~SuggestionBasic.Modification
- Direction
- Core~HostApp uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Core~HostApp, while a change to Core~HostApp can't break Tool~SuggestionBasic.
- Position
- Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
33→10 Core~HostApp uses Tool~Toast✕
- Connections
- 3 pairs of types, where a type in Core~HostApp uses a type in Tool~Toast.
- The types involved
Core~HostApp.DependencyValues→Tool~Toast.ToastControllerCore~HostApp.TabContainer→Tool~Toast.ToastControllerCore~HostApp.ToastHandler→Tool~Toast.ToastController
- Direction
- Core~HostApp uses Tool~Toast, so a change to Tool~Toast can break Core~HostApp, while a change to Core~HostApp can't break Tool~Toast.
- Position
- Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
33→11 Core~HostApp uses Core~PromptToCodeService✕
- Connections
- 1 pair of types, where a type in Core~HostApp uses a type in Core~PromptToCodeService.
- The types involved
Core~HostApp.DependencyValues→Core~PromptToCodeService.PromptToCodeServiceType
- Direction
- Core~HostApp uses Core~PromptToCodeService, so a change to Core~PromptToCodeService can break Core~HostApp, while a change to Core~HostApp can't break Core~PromptToCodeService.
- Position
- Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
33→12 Core~HostApp uses Tool~ChatTab✕
- Connections
- 2 pairs of types, where a type in Core~HostApp uses a type in Tool~ChatTab.
- The types involved
Core~HostApp.DependencyValues→Tool~ChatTab.ChatTabPoolCore~HostApp.EnvironmentValues→Tool~ChatTab.ChatTabPool
- Direction
- Core~HostApp uses Tool~ChatTab, so a change to Tool~ChatTab can break Core~HostApp, while a change to Core~HostApp can't break Tool~ChatTab.
- Position
- Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
33→17 Core~HostApp uses Tool~GitHubCopilotService✕
- Connections
- 41 pairs of types, where a type in Core~HostApp uses a type in Tool~GitHubCopilotService. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Core~HostApp.AppInfoView→Tool~GitHubCopilotService.GitHubCopilotAuthServiceTypeCore~HostApp.BYOKModelManagerObservable→Tool~GitHubCopilotService.BYOKApiKeyInfoCore~HostApp.BYOKModelManagerObservable→Tool~GitHubCopilotService.BYOKModelInfoCore~HostApp.BYOKModelManagerObservable→Tool~GitHubCopilotService.BYOKProviderNameCore~HostApp.BYOKProviderConfigView→Tool~GitHubCopilotService.BYOKModelInfoCore~HostApp.BYOKServiceActor→Tool~GitHubCopilotService.BYOKApiKeyInfoCore~HostApp.BYOKServiceActor→Tool~GitHubCopilotService.BYOKModelInfoCore~HostApp.BYOKServiceActor→Tool~GitHubCopilotService.BYOKProviderNameCore~HostApp.CopilotMCPToolManagerObservable→Tool~GitHubCopilotService.MCPServerToolsCollectionCore~HostApp.IdentifiableServerResponse→Tool~GitHubCopilotService.MCPRegistryServerResponseCore~HostApp.MCPRegistryService→Tool~GitHubCopilotService.ArgumentCore~HostApp.MCPRegistryService→Tool~GitHubCopilotService.MCPRegistryEntryCore~HostApp.MCPRegistryService→Tool~GitHubCopilotService.MCPRegistryServerDetailCore~HostApp.MCPRegistryService→Tool~GitHubCopilotService.PackageCore~HostApp.MCPRegistryService→Tool~GitHubCopilotService.RemoteCore~HostApp.MCPRegistryURLInputField→Tool~GitHubCopilotService.MCPRegistryEntryCore~HostApp.MCPRegistryURLSheet→Tool~GitHubCopilotService.MCPRegistryEntryCore~HostApp.MCPServerDetailSheet→Tool~GitHubCopilotService.MCPRegistryServerDetailCore~HostApp.MCPServerDetailSheet→Tool~GitHubCopilotService.MCPRegistryServerResponseCore~HostApp.MCPServerDetailSheet→Tool~GitHubCopilotService.OfficialMetaCore~HostApp.MCPServerDetailSheet→Tool~GitHubCopilotService.PackageCore~HostApp.MCPServerDetailSheet→Tool~GitHubCopilotService.RemoteCore~HostApp.MCPServerDetailSheet→Tool~GitHubCopilotService.ServerMetaCore~HostApp.MCPServerDetailSheet→Tool~GitHubCopilotService.ServerStatusCore~HostApp.MCPServerGalleryView→Tool~GitHubCopilotService.MCPRegistryServerResponse
- 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.
33→18 Core~HostApp uses Tool~Status✕
- Connections
- 3 pairs of types, where a type in Core~HostApp uses a type in Tool~Status.
- The types involved
Core~HostApp.State→Tool~Status.AuthStatusCore~HostApp.State→Tool~Status.ExtensionPermissionStatusCore~HostApp.State→Tool~Status.ObservedAXStatus
- Direction
- Core~HostApp uses Tool~Status, so a change to Tool~Status can break Core~HostApp, while a change to Core~HostApp can't break Tool~Status.
- Position
- Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
33→19 Core~HostApp uses Tool~XcodeInspector✕
- Connections
- 1 pair of types, where a type in Core~HostApp uses a type in Tool~XcodeInspector.
- The types involved
Core~HostApp.DependencyValues→Tool~XcodeInspector.XcodeInspector
- 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.
33→21 Core~HostApp uses Tool~ConversationServiceProvider✕
- Connections
- 16 pairs of types, where a type in Core~HostApp uses a type in Tool~ConversationServiceProvider.
- The types involved
Core~HostApp.AgentFileSetting→Tool~ConversationServiceProvider.PromptTypeCore~HostApp.AgentModeDescription→Tool~ConversationServiceProvider.ConversationModeCore~HostApp.AgentModeDescriptionView→Tool~ConversationServiceProvider.ConversationModeCore~HostApp.AgentModeDropdown→Tool~ConversationServiceProvider.ConversationModeCore~HostApp.BuiltInToolsListView→Tool~ConversationServiceProvider.ConversationModeCore~HostApp.BuiltInToolsListView→Tool~ConversationServiceProvider.LanguageModelToolCore~HostApp.BuiltInToolsListView→Tool~ConversationServiceProvider.ToolStatusUpdateCore~HostApp.CopilotBuiltInToolManagerObservable→Tool~ConversationServiceProvider.LanguageModelToolCore~HostApp.MCPConfigView→Tool~ConversationServiceProvider.ConversationModeCore~HostApp.MCPServerToolsSection→Tool~ConversationServiceProvider.ConversationModeCore~HostApp.MCPServerToolsSection→Tool~ConversationServiceProvider.ToolStatusCore~HostApp.MCPToolsListContainerView→Tool~ConversationServiceProvider.ConversationModeCore~HostApp.MCPToolsListView→Tool~ConversationServiceProvider.ConversationModeCore~HostApp.PromptFileSetting→Tool~ConversationServiceProvider.PromptTypeCore~HostApp.RowItem→Tool~ConversationServiceProvider.ItemTypeCore~HostApp.ToolRow→Tool~ConversationServiceProvider.ToolStatus
- Direction
- Core~HostApp uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Core~HostApp, while a change to Core~HostApp can't break Tool~ConversationServiceProvider.
- Position
- Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
33→22 Core~HostApp uses Tool~SharedUIComponents✕
- Connections
- 2 pairs of types, where a type in Core~HostApp uses a type in Tool~SharedUIComponents.
- The types involved
Core~HostApp.FontSizeSetting→Tool~SharedUIComponents.FontScaleManagerCore~HostApp.MCPServerToolsSection→Tool~SharedUIComponents.CheckboxMixedState
- 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.
33→23 Core~HostApp uses Tool~Workspace✕
- Connections
- 2 pairs of types, where a type in Core~HostApp uses a type in Tool~Workspace.
- The types involved
Core~HostApp.DependencyValues→Tool~Workspace.WorkspaceInvokerCore~HostApp.DependencyValues→Tool~Workspace.WorkspacePool
- Direction
- Core~HostApp uses Tool~Workspace, so a change to Tool~Workspace can break Core~HostApp, while a change to Core~HostApp can't break Tool~Workspace.
- Position
- Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
33→26 Core~HostApp uses Tool~XPCShared✕
- Connections
- 1 pair of types, where a type in Core~HostApp uses a type in Tool~XPCShared.
- The types involved
Core~HostApp.BYOKServiceActor→Tool~XPCShared.XPCExtensionService
- Direction
- Core~HostApp uses Tool~XPCShared, so a change to Tool~XPCShared can break Core~HostApp, while a change to Core~HostApp can't break Tool~XPCShared.
- Position
- Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
33→27 Core~HostApp uses repository✕
- Connections
- 3 pairs of types, where a type in Core~HostApp uses a type in repository.
- The types involved
Core~HostApp.BYOKServiceActor→repository.TaskCore~HostApp.MCPConfigView→repository.TaskCore~HostApp.MCPServerGalleryView→repository.Task
- Direction
- Core~HostApp uses repository, so a change to repository can break Core~HostApp, while a change to Core~HostApp can't break repository.
- Position
- Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
33→29 Core~HostApp uses Core~SuggestionWidget✕
- Connections
- 2 pairs of types, where a type in Core~HostApp uses a type in Core~SuggestionWidget.
- The types involved
Core~HostApp.DependencyValues→Core~SuggestionWidget.SuggestionWidgetControllerDependencyCore~HostApp.DependencyValues→Core~SuggestionWidget.WidgetUserDefaultsObservers
- 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.
33→30 Core~HostApp uses Core~XcodeThemeController✕
- Connections
- 2 pairs of types, where a type in Core~HostApp uses a type in Core~XcodeThemeController.
- The types involved
Core~HostApp.MCPServerGalleryViewModel→Core~XcodeThemeController.ErrorCore~HostApp.MCPServerGalleryWindow→Core~XcodeThemeController.Error
- Direction
- Core~HostApp uses Core~XcodeThemeController, so a change to Core~XcodeThemeController can break Core~HostApp, while a change to Core~HostApp can't break Core~XcodeThemeController.
- Position
- Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
33→31 Core~HostApp uses Tool~FileSystem✕
- Connections
- 7 pairs of types, where a type in Core~HostApp uses a type in Tool~FileSystem.
- The types involved
Core~HostApp.CopilotPolicyManager→Tool~FileSystem.DateCore~HostApp.FeatureFlagManager→Tool~FileSystem.DateCore~HostApp.MCPConfigView→Tool~FileSystem.DateCore~HostApp.MCPServerDetailSheet→Tool~FileSystem.DateCore~HostApp.String→Tool~FileSystem.CharacterCore~HostApp.String→Tool~FileSystem.SubstringCore~HostApp.String→Tool~FileSystem.WritableByteStream
- Direction
- Core~HostApp uses Tool~FileSystem, so a change to Tool~FileSystem can break Core~HostApp, while a change to Core~HostApp can't break Tool~FileSystem.
- Position
- Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
33→32 Core~HostApp uses Core~GitHubCopilotViewModel✕
- Connections
- 1 pair of types, where a type in Core~HostApp uses a type in Core~GitHubCopilotViewModel.
- The types involved
Core~HostApp.CopilotConnectionView→Core~GitHubCopilotViewModel.GitHubCopilotViewModel
- Direction
- Core~HostApp uses Core~GitHubCopilotViewModel, so a change to Core~GitHubCopilotViewModel can break Core~HostApp, while a change to Core~HostApp can't break Core~GitHubCopilotViewModel.
- Position
- Below the diagonal: Core~HostApp uses a module listed above it, which is the healthy direction.
33→38 Core~HostApp uses Core~ConversationTab part of a loop✕
- Connections
- 77 pairs of types, where a type in Core~HostApp uses a type in Core~ConversationTab. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Core~HostApp.AdvancedSettings→Core~ConversationTab.ViewCore~HostApp.AgentAutoCompressSetting→Core~ConversationTab.ViewCore~HostApp.AgentFileSetting→Core~ConversationTab.ViewCore~HostApp.AgentMaxToolCallLoopSetting→Core~ConversationTab.ViewCore~HostApp.AgentModeDescriptionView→Core~ConversationTab.ViewCore~HostApp.AgentModeDropdown→Core~ConversationTab.ViewCore~HostApp.AgentTrustToolAnnotationsSetting→Core~ConversationTab.ViewCore~HostApp.ApiKeySheet→Core~ConversationTab.ViewCore~HostApp.AppInfoView→Core~ConversationTab.ViewCore~HostApp.AutoApprovalDisableView→Core~ConversationTab.ViewCore~HostApp.AutoApproveContainerView→Core~ConversationTab.ViewCore~HostApp.BYOKConfigView→Core~ConversationTab.ViewCore~HostApp.BYOKProviderConfigView→Core~ConversationTab.ViewCore~HostApp.Badge→Core~ConversationTab.ViewCore~HostApp.BorderedProminentWhiteButtonStyle→Core~ConversationTab.ViewCore~HostApp.BuiltInToolsListView→Core~ConversationTab.ViewCore~HostApp.CardGroupBoxStyle→Core~ConversationTab.ColorCore~HostApp.CardGroupBoxStyle→Core~ConversationTab.ViewCore~HostApp.ChatSection→Core~ConversationTab.ViewCore~HostApp.CopilotConnectionView→Core~ConversationTab.ViewCore~HostApp.CopilotInstructionSetting→Core~ConversationTab.ViewCore~HostApp.CustomCopilotHelper.swift→Core~ConversationTab.URLCore~HostApp.DisabledLanguageList→Core~ConversationTab.ViewCore~HostApp.DisclosureSettingsRow→Core~ConversationTab.ColorCore~HostApp.DisclosureSettingsRow→Core~ConversationTab.View
- Direction
- Core~HostApp uses Core~ConversationTab, so a change to Core~ConversationTab can break Core~HostApp, while a change to Core~HostApp can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→39 Core~HostApp uses Core~ChatService part of a loop✕
- Connections
- 1 pair of types, where a type in Core~HostApp uses a type in Core~ChatService.
- The types involved
Core~HostApp.String→Core~ChatService.Array
- Direction
- Core~HostApp uses Core~ChatService, so a change to Core~ChatService can break Core~HostApp, while a change to Core~HostApp can't break Core~ChatService.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→7 Core~PersistMiddleware uses Tool~Persist✕
- Connections
- 4 pairs of types, where a type in Core~PersistMiddleware uses a type in Tool~Persist.
- The types involved
Core~PersistMiddleware.ChatMessageStore→Tool~Persist.StorageMetadataCore~PersistMiddleware.ChatTabInfoStore→Tool~Persist.ConversationFetchTypeCore~PersistMiddleware.ChatTabInfoStore→Tool~Persist.StorageMetadataCore~PersistMiddleware.ChatTabPreviewInfoStore→Tool~Persist.StorageMetadata
- Direction
- Core~PersistMiddleware uses Tool~Persist, so a change to Tool~Persist can break Core~PersistMiddleware, while a change to Core~PersistMiddleware can't break Tool~Persist.
- Position
- Below the diagonal: Core~PersistMiddleware uses a module listed above it, which is the healthy direction.
34→12 Core~PersistMiddleware uses Tool~ChatTab✕
- Connections
- 2 pairs of types, where a type in Core~PersistMiddleware uses a type in Tool~ChatTab.
- The types involved
Core~PersistMiddleware.ChatTabInfoStore→Tool~ChatTab.ChatTabInfoCore~PersistMiddleware.ChatTabPreviewInfoStore→Tool~ChatTab.ChatTabPreviewInfo
- Direction
- Core~PersistMiddleware uses Tool~ChatTab, so a change to Tool~ChatTab can break Core~PersistMiddleware, while a change to Core~PersistMiddleware can't break Tool~ChatTab.
- Position
- Below the diagonal: Core~PersistMiddleware uses a module listed above it, which is the healthy direction.
34→20 Core~PersistMiddleware uses Tool~ChatAPIService✕
- Connections
- 1 pair of types, where a type in Core~PersistMiddleware uses a type in Tool~ChatAPIService.
- The types involved
Core~PersistMiddleware.ChatMessageStore→Tool~ChatAPIService.ChatMessage
- Direction
- Core~PersistMiddleware uses Tool~ChatAPIService, so a change to Tool~ChatAPIService can break Core~PersistMiddleware, while a change to Core~PersistMiddleware can't break Tool~ChatAPIService.
- Position
- Below the diagonal: Core~PersistMiddleware uses a module listed above it, which is the healthy direction.
34→33 Core~PersistMiddleware uses Core~HostApp✕
- Connections
- 2 pairs of types, where a type in Core~PersistMiddleware uses a type in Core~HostApp.
- The types involved
Core~PersistMiddleware.ChatMessageStore→Core~HostApp.StringCore~PersistMiddleware.ChatTabInfoStore→Core~HostApp.String
- Direction
- Core~PersistMiddleware uses Core~HostApp, so a change to Core~HostApp can break Core~PersistMiddleware, while a change to Core~PersistMiddleware can't break Core~HostApp.
- Position
- Below the diagonal: Core~PersistMiddleware uses a module listed above it, which is the healthy direction.
35→27 Tool~AXNotificationStream uses repository✕
- Connections
- 1 pair of types, where a type in Tool~AXNotificationStream uses a type in repository.
- The types involved
Tool~AXNotificationStream.AXNotificationStream→repository.NSRunningApplication
- 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.
35→28 Tool~AXNotificationStream uses Tool~AXExtension✕
- Connections
- 1 pair of types, where a type in Tool~AXNotificationStream uses a type in Tool~AXExtension.
- The types involved
Tool~AXNotificationStream.AXNotificationStream→Tool~AXExtension.AXUIElement
- 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.
35→31 Tool~AXNotificationStream uses Tool~FileSystem✕
- Connections
- 1 pair of types, where a type in Tool~AXNotificationStream uses a type in Tool~FileSystem.
- The types involved
Tool~AXNotificationStream.AXNotificationStream→Tool~FileSystem.StaticString
- 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.
35→33 Tool~AXNotificationStream uses Core~HostApp✕
- Connections
- 1 pair of types, where a type in Tool~AXNotificationStream uses a type in Core~HostApp.
- The types involved
Tool~AXNotificationStream.AXNotificationStream→Core~HostApp.String
- Direction
- Tool~AXNotificationStream uses Core~HostApp, so a change to Core~HostApp can break Tool~AXNotificationStream, while a change to Tool~AXNotificationStream can't break Core~HostApp.
- Position
- Below the diagonal: Tool~AXNotificationStream uses a module listed above it, which is the healthy direction.
36→1 Tool~TelemetryService uses Core~UserDefaultsObserver✕
- Connections
- 1 pair of types, where a type in Tool~TelemetryService uses a type in Core~UserDefaultsObserver.
- The types involved
Tool~TelemetryService.GitHubPanicErrorReporter→Core~UserDefaultsObserver.UserDefaultsObserver
- Direction
- Tool~TelemetryService uses Core~UserDefaultsObserver, so a change to Core~UserDefaultsObserver can break Tool~TelemetryService, while a change to Tool~TelemetryService can't break Core~UserDefaultsObserver.
- Position
- Below the diagonal: Tool~TelemetryService uses a module listed above it, which is the healthy direction.
36→9 Tool~TelemetryService uses Tool~TelemetryServiceProvider✕
- Connections
- 5 pairs of types, where a type in Tool~TelemetryService uses a type in Tool~TelemetryServiceProvider.
- The types involved
Tool~TelemetryService.GitHubPanicErrorReporter→Tool~TelemetryServiceProvider.TelemetryExceptionRequestTool~TelemetryService.TelemetryService→Tool~TelemetryServiceProvider.ExceptionDetailTool~TelemetryService.TelemetryService→Tool~TelemetryServiceProvider.StackTraceFrameTool~TelemetryService.TelemetryService→Tool~TelemetryServiceProvider.TelemetryExceptionRequestTool~TelemetryService.TelemetryService→Tool~TelemetryServiceProvider.TelemetryServiceProvider
- Direction
- Tool~TelemetryService uses Tool~TelemetryServiceProvider, so a change to Tool~TelemetryServiceProvider can break Tool~TelemetryService, while a change to Tool~TelemetryService can't break Tool~TelemetryServiceProvider.
- Position
- Below the diagonal: Tool~TelemetryService uses a module listed above it, which is the healthy direction.
36→30 Tool~TelemetryService uses Core~XcodeThemeController✕
- Connections
- 3 pairs of types, where a type in Tool~TelemetryService uses a type in Core~XcodeThemeController.
- The types involved
Tool~TelemetryService.TelemetryService→Core~XcodeThemeController.ErrorTool~TelemetryService.TelemetryServiceError→Core~XcodeThemeController.ErrorTool~TelemetryService.WrappedTelemetryServiceType→Core~XcodeThemeController.Error
- Direction
- Tool~TelemetryService uses Core~XcodeThemeController, so a change to Core~XcodeThemeController can break Tool~TelemetryService, while a change to Tool~TelemetryService can't break Core~XcodeThemeController.
- Position
- Below the diagonal: Tool~TelemetryService uses a module listed above it, which is the healthy direction.
36→31 Tool~TelemetryService uses Tool~FileSystem✕
- Connections
- 2 pairs of types, where a type in Tool~TelemetryService uses a type in Tool~FileSystem.
- The types involved
Tool~TelemetryService.TelemetryService→Tool~FileSystem.StaticStringTool~TelemetryService.WrappedTelemetryServiceType→Tool~FileSystem.StaticString
- Direction
- Tool~TelemetryService uses Tool~FileSystem, so a change to Tool~FileSystem can break Tool~TelemetryService, while a change to Tool~TelemetryService can't break Tool~FileSystem.
- Position
- Below the diagonal: Tool~TelemetryService uses a module listed above it, which is the healthy direction.
36→33 Tool~TelemetryService uses Core~HostApp✕
- Connections
- 4 pairs of types, where a type in Tool~TelemetryService uses a type in Core~HostApp.
- The types involved
Tool~TelemetryService.GitHubPanicErrorReporter→Core~HostApp.StringTool~TelemetryService.TelemetryCleaner→Core~HostApp.StringTool~TelemetryService.TelemetryService→Core~HostApp.StringTool~TelemetryService.WrappedTelemetryServiceType→Core~HostApp.String
- Direction
- Tool~TelemetryService uses Core~HostApp, so a change to Core~HostApp can break Tool~TelemetryService, while a change to Tool~TelemetryService can't break Core~HostApp.
- Position
- Below the diagonal: Tool~TelemetryService uses a module listed above it, which is the healthy direction.
37→2 Tool~Terminal uses Tool~Preferences✕
- Connections
- 5 pairs of types, where a type in Tool~Terminal uses a type in Tool~Preferences.
- The types involved
Tool~Terminal.CommandExecutionResult→Tool~Preferences.BoolTool~Terminal.ShellProcessManager→Tool~Preferences.BoolTool~Terminal.Terminal→Tool~Preferences.BoolTool~Terminal.TerminalSession→Tool~Preferences.BoolTool~Terminal.TerminalType→Tool~Preferences.Bool
- Direction
- Tool~Terminal uses Tool~Preferences, so a change to Tool~Preferences can break Tool~Terminal, while a change to Tool~Terminal can't break Tool~Preferences.
- Position
- Below the diagonal: Tool~Terminal uses a module listed above it, which is the healthy direction.
37→30 Tool~Terminal uses Core~XcodeThemeController✕
- Connections
- 1 pair of types, where a type in Tool~Terminal uses a type in Core~XcodeThemeController.
- The types involved
Tool~Terminal.TerminationError→Core~XcodeThemeController.Error
- Direction
- Tool~Terminal uses Core~XcodeThemeController, so a change to Core~XcodeThemeController can break Tool~Terminal, while a change to Tool~Terminal can't break Core~XcodeThemeController.
- Position
- Below the diagonal: Tool~Terminal uses a module listed above it, which is the healthy direction.
37→33 Tool~Terminal uses Core~HostApp✕
- Connections
- 6 pairs of types, where a type in Tool~Terminal uses a type in Core~HostApp.
- The types involved
Tool~Terminal.CommandExecutionResult→Core~HostApp.StringTool~Terminal.ShellProcessManager→Core~HostApp.StringTool~Terminal.Terminal→Core~HostApp.StringTool~Terminal.TerminalSession→Core~HostApp.StringTool~Terminal.TerminalSessionManager→Core~HostApp.StringTool~Terminal.TerminalType→Core~HostApp.String
- Direction
- Tool~Terminal uses Core~HostApp, so a change to Core~HostApp can break Tool~Terminal, while a change to Tool~Terminal can't break Core~HostApp.
- Position
- Below the diagonal: Tool~Terminal uses a module listed above it, which is the healthy direction.
37→38 Tool~Terminal uses Core~ConversationTab part of a loop✕
- Connections
- 2 pairs of types, where a type in Tool~Terminal uses a type in Core~ConversationTab.
- The types involved
Tool~Terminal.Terminal→Core~ConversationTab.URLTool~Terminal.TerminalType→Core~ConversationTab.URL
- Direction
- Tool~Terminal uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~Terminal, while a change to Tool~Terminal can't break Core~ConversationTab.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
38→2 Core~ConversationTab uses Tool~Preferences✕
- Connections
- 120 pairs of types, where a type in Core~ConversationTab uses a type in Tool~Preferences. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Core~ConversationTab.ActionLink→Tool~Preferences.BoolCore~ConversationTab.AgentEditingState→Tool~Preferences.BoolCore~ConversationTab.AgentModeButton→Tool~Preferences.BoolCore~ConversationTab.AgentModeButton→Tool~Preferences.DoubleCore~ConversationTab.AgentModeButtonMenuItem→Tool~Preferences.BoolCore~ConversationTab.AgentModeButtonMenuItem→Tool~Preferences.DoubleCore~ConversationTab.AgentModeMenu→Tool~Preferences.BoolCore~ConversationTab.AgentModeMenu→Tool~Preferences.DoubleCore~ConversationTab.BotMessage→Tool~Preferences.BoolCore~ConversationTab.BotMessage→Tool~Preferences.DoubleCore~ConversationTab.Chat→Tool~Preferences.BoolCore~ConversationTab.ChatDropdownView→Tool~Preferences.BoolCore~ConversationTab.ChatDropdownView→Tool~Preferences.IntCore~ConversationTab.ChatModePicker→Tool~Preferences.BoolCore~ConversationTab.ChatModelPicker→Tool~Preferences.BoolCore~ConversationTab.ChatModelPicker→Tool~Preferences.DoubleCore~ConversationTab.ChatPanel→Tool~Preferences.BoolCore~ConversationTab.ChatPanelInputArea→Tool~Preferences.DoubleCore~ConversationTab.ChatPanelMessages→Tool~Preferences.BoolCore~ConversationTab.ChatPanelMessages→Tool~Preferences.DoubleCore~ConversationTab.CheckPoint→Tool~Preferences.BoolCore~ConversationTab.CodeReviewMainView→Tool~Preferences.BoolCore~ConversationTab.ContextSizeButton→Tool~Preferences.BoolCore~ConversationTab.ContextSizePopover→Tool~Preferences.DoubleCore~ConversationTab.ContextSizePopover→Tool~Preferences.Int
- Direction
- Core~ConversationTab uses Tool~Preferences, so a change to Tool~Preferences can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~Preferences.
- Position
- Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
38→8 Core~ConversationTab uses Tool~SuggestionBasic✕
- Connections
- 1 pair of types, where a type in Core~ConversationTab uses a type in Tool~SuggestionBasic.
- The types involved
Core~ConversationTab.EditorErrorIssue→Tool~SuggestionBasic.LineAnnotation
- Direction
- Core~ConversationTab uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~SuggestionBasic.
- Position
- Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
38→12 Core~ConversationTab uses Tool~ChatTab✕
- Connections
- 5 pairs of types, where a type in Core~ConversationTab uses a type in Tool~ChatTab.
- The types involved
Core~ConversationTab.Builder→Tool~ChatTab.ChatTabBuilderCore~ConversationTab.ChatPanel_Preview→Tool~ChatTab.ChatTabInfoCore~ConversationTab.ConversationTab→Tool~ChatTab.ChatTabBuilderCore~ConversationTab.ConversationTab→Tool~ChatTab.ChatTabInfoCore~ConversationTab.DiffView_Previews→Tool~ChatTab.ChatTabInfo
- Direction
- Core~ConversationTab uses Tool~ChatTab, so a change to Tool~ChatTab can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~ChatTab.
- Position
- Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
38→17 Core~ConversationTab uses Tool~GitHubCopilotService✕
- Connections
- 2 pairs of types, where a type in Core~ConversationTab uses a type in Tool~GitHubCopilotService.
- The types involved
Core~ConversationTab.ModelPickerMenuItem→Tool~GitHubCopilotService.LayoutConstantsCore~ConversationTab.WarningBanner→Tool~GitHubCopilotService.WarningAction
- Direction
- Core~ConversationTab uses Tool~GitHubCopilotService, so a change to Tool~GitHubCopilotService can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~GitHubCopilotService.
- Position
- Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
38→18 Core~ConversationTab uses Tool~Status✕
- Connections
- 1 pair of types, where a type in Core~ConversationTab uses a type in Tool~Status.
- The types involved
Core~ConversationTab.InputAreaTextEditor→Tool~Status.StatusObserver
- Direction
- Core~ConversationTab uses Tool~Status, so a change to Tool~Status can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~Status.
- Position
- Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
38→19 Core~ConversationTab uses Tool~XcodeInspector✕
- Connections
- 1 pair of types, where a type in Core~ConversationTab uses a type in Tool~XcodeInspector.
- The types involved
Core~ConversationTab.InputAreaTextEditor→Tool~XcodeInspector.SourceEditor
- Direction
- Core~ConversationTab uses Tool~XcodeInspector, so a change to Tool~XcodeInspector can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~XcodeInspector.
- Position
- Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
38→20 Core~ConversationTab uses Tool~ChatAPIService✕
- Connections
- 18 pairs of types, where a type in Core~ConversationTab uses a type in Tool~ChatAPIService.
- The types involved
Core~ConversationTab.BotMessage→Tool~ChatAPIService.ConversationReferenceCore~ConversationTab.ConversationState→Tool~ChatAPIService.RequestTypeCore~ConversationTab.DiffView→Tool~ChatAPIService.FileEditCore~ConversationTab.DiffViewWindowController→Tool~ChatAPIService.FileEditCore~ConversationTab.DiffWebView→Tool~ChatAPIService.FileEditCore~ConversationTab.DisplayedChatMessage→Tool~ChatAPIService.ConversationReferenceCore~ConversationTab.DisplayedChatMessage→Tool~ChatAPIService.FileEditCore~ConversationTab.DisplayedChatMessage→Tool~ChatAPIService.RequestTypeCore~ConversationTab.DisplayedChatMessage→Tool~ChatAPIService.TurnStatusCore~ConversationTab.FileEditView→Tool~ChatAPIService.FileEditCore~ConversationTab.FileSelectionList→Tool~ChatAPIService.StatusCore~ConversationTab.FileSelectionRow→Tool~ChatAPIService.StatusCore~ConversationTab.FileToggleList→Tool~ChatAPIService.StatusCore~ConversationTab.ReferenceButton→Tool~ChatAPIService.ConversationReferenceCore~ConversationTab.RestorableState→Tool~ChatAPIService.ChatMessageCore~ConversationTab.ReviewResultsHeader→Tool~ChatAPIService.StatusCore~ConversationTab.State→Tool~ChatAPIService.RequestTypeCore~ConversationTab.UserMessage→Tool~ChatAPIService.RequestType
- Direction
- Core~ConversationTab uses Tool~ChatAPIService, so a change to Tool~ChatAPIService can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~ChatAPIService.
- Position
- Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
38→21 Core~ConversationTab uses Tool~ConversationServiceProvider✕
- Connections
- 69 pairs of types, where a type in Core~ConversationTab uses a type in Tool~ConversationServiceProvider. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Core~ConversationTab.AgentModeButton→Tool~ConversationServiceProvider.ConversationModeCore~ConversationTab.AgentModeMenu→Tool~ConversationServiceProvider.ConversationModeCore~ConversationTab.BotMessage→Tool~ConversationServiceProvider.AgentRoundCore~ConversationTab.BotMessage→Tool~ConversationServiceProvider.CodeReviewRoundCore~ConversationTab.BotMessage→Tool~ConversationServiceProvider.ConversationFollowUpCore~ConversationTab.BotMessage→Tool~ConversationServiceProvider.ConversationProgressStepCore~ConversationTab.BotMessage→Tool~ConversationServiceProvider.CopilotShowMessageParamsCore~ConversationTab.BotMessage→Tool~ConversationServiceProvider.MessageThinkingCore~ConversationTab.BotMessage_Previews→Tool~ConversationServiceProvider.AgentRoundCore~ConversationTab.BotMessage_Previews→Tool~ConversationServiceProvider.ConversationProgressStepCore~ConversationTab.ChatContext→Tool~ConversationServiceProvider.ConversationAttachedReferenceCore~ConversationTab.ChatContext→Tool~ConversationServiceProvider.ImageReferenceCore~ConversationTab.ChatModePicker→Tool~ConversationServiceProvider.ConversationModeCore~ConversationTab.CodeReviewMainView→Tool~ConversationServiceProvider.CodeReviewRoundCore~ConversationTab.CompletedSummary→Tool~ConversationServiceProvider.CodeReviewRequestCore~ConversationTab.CompletedSummary→Tool~ConversationServiceProvider.CodeReviewResponseCore~ConversationTab.ContextSizeButton→Tool~ConversationServiceProvider.ContextSizeInfoCore~ConversationTab.ContextSizePopover→Tool~ConversationServiceProvider.ContextSizeInfoCore~ConversationTab.ContextUtils→Tool~ConversationServiceProvider.ConversationAttachedReferenceCore~ConversationTab.ContextUtils→Tool~ConversationServiceProvider.ConversationFileReferenceCore~ConversationTab.ConversationState→Tool~ConversationServiceProvider.ContextSizeInfoCore~ConversationTab.DisplayedChatMessage→Tool~ConversationServiceProvider.AgentRoundCore~ConversationTab.DisplayedChatMessage→Tool~ConversationServiceProvider.CodeReviewRoundCore~ConversationTab.DisplayedChatMessage→Tool~ConversationServiceProvider.ConversationFollowUpCore~ConversationTab.DisplayedChatMessage→Tool~ConversationServiceProvider.ConversationProgressStep
- Direction
- Core~ConversationTab uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~ConversationServiceProvider.
- Position
- Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
38→22 Core~ConversationTab uses Tool~SharedUIComponents✕
- Connections
- 5 pairs of types, where a type in Core~ConversationTab uses a type in Tool~SharedUIComponents.
- The types involved
Core~ConversationTab.FileSelectionList→Tool~SharedUIComponents.CheckboxMixedStateCore~ConversationTab.InputAreaTextEditor→Tool~SharedUIComponents.TextEditorStateCore~ConversationTab.RunInTerminalToolView→Tool~SharedUIComponents.SplitButtonMenuItemCore~ConversationTab.ToolConfirmationView→Tool~SharedUIComponents.SplitButtonMenuItemCore~ConversationTab.View→Tool~SharedUIComponents.Font
- Direction
- Core~ConversationTab uses Tool~SharedUIComponents, so a change to Tool~SharedUIComponents can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~SharedUIComponents.
- Position
- Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
38→27 Core~ConversationTab uses repository✕
- Connections
- 5 pairs of types, where a type in Core~ConversationTab uses a type in repository.
- The types involved
Core~ConversationTab.Builder→repository.CustomCommandCore~ConversationTab.ContextSizeButton→repository.TaskCore~ConversationTab.HoverableImageView→repository.TaskCore~ConversationTab.Storage→repository.TaskCore~ConversationTab.TimedDebounceFunction→repository.Task
- Direction
- Core~ConversationTab uses repository, so a change to repository can break Core~ConversationTab, while a change to Core~ConversationTab can't break repository.
- Position
- Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
38→29 Core~ConversationTab uses Core~SuggestionWidget✕
- Connections
- 7 pairs of types, where a type in Core~ConversationTab uses a type in Core~SuggestionWidget.
- The types involved
Core~ConversationTab.HoverBackgroundModifier→Core~SuggestionWidget.ContentCore~ConversationTab.HoverForegroundModifier→Core~SuggestionWidget.ContentCore~ConversationTab.HoverRadiusBackgroundModifier→Core~SuggestionWidget.ContentCore~ConversationTab.State→Core~SuggestionWidget.NavigationDirectionCore~ConversationTab.ThinScrollView→Core~SuggestionWidget.ContentCore~ConversationTab.ToolStatusDetailsView→Core~SuggestionWidget.ContentCore~ConversationTab.VerticalScrollingFixViewRepresentable→Core~SuggestionWidget.Content
- Direction
- Core~ConversationTab uses Core~SuggestionWidget, so a change to Core~SuggestionWidget can break Core~ConversationTab, while a change to Core~ConversationTab can't break Core~SuggestionWidget.
- Position
- Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
38→31 Core~ConversationTab uses Tool~FileSystem✕
- Connections
- 4 pairs of types, where a type in Core~ConversationTab uses a type in Tool~FileSystem.
- The types involved
Core~ConversationTab.DashedLine→Tool~FileSystem.PathCore~ConversationTab.ModeAndModelPicker→Tool~FileSystem.DateCore~ConversationTab.RoundedCorners→Tool~FileSystem.PathCore~ConversationTab.TimedDebounceFunction→Tool~FileSystem.Date
- Direction
- Core~ConversationTab uses Tool~FileSystem, so a change to Tool~FileSystem can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~FileSystem.
- Position
- Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
38→33 Core~ConversationTab uses Core~HostApp✕
- Connections
- 65 pairs of types, where a type in Core~ConversationTab uses a type in Core~HostApp. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Core~ConversationTab.ActionButton→Core~HostApp.StringCore~ConversationTab.ActionLink→Core~HostApp.StringCore~ConversationTab.AgentModeButton→Core~HostApp.StringCore~ConversationTab.AgentModeButtonMenuItem→Core~HostApp.StringCore~ConversationTab.AgentModeIcon→Core~HostApp.StringCore~ConversationTab.AsyncCodeBlockView→Core~HostApp.StringCore~ConversationTab.BannerStyle→Core~HostApp.StringCore~ConversationTab.BotMessage→Core~HostApp.StringCore~ConversationTab.Builder→Core~HostApp.StringCore~ConversationTab.ChatContext→Core~HostApp.StringCore~ConversationTab.ChatDropdownView→Core~HostApp.StringCore~ConversationTab.ChatModePicker→Core~HostApp.StringCore~ConversationTab.ChatModelPicker→Core~HostApp.StringCore~ConversationTab.CheckPoint→Core~HostApp.StringCore~ConversationTab.CodeReviewMainView→Core~HostApp.StringCore~ConversationTab.ContextSizePopover→Core~HostApp.StringCore~ConversationTab.ConversationTab→Core~HostApp.StringCore~ConversationTab.DiffView_Previews→Core~HostApp.StringCore~ConversationTab.DiffWebView.swift→Core~HostApp.StringCore~ConversationTab.DisplayedChatMessage→Core~HostApp.StringCore~ConversationTab.DropDownItem→Core~HostApp.StringCore~ConversationTab.EditorErrorIssue→Core~HostApp.StringCore~ConversationTab.EditorMode→Core~HostApp.StringCore~ConversationTab.ExpandableFileListView→Core~HostApp.StringCore~ConversationTab.Field→Core~HostApp.String
- Direction
- Core~ConversationTab uses Core~HostApp, so a change to Core~HostApp can break Core~ConversationTab, while a change to Core~ConversationTab can't break Core~HostApp.
- Position
- Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
38→37 Core~ConversationTab uses Tool~Terminal✕
- Connections
- 2 pairs of types, where a type in Core~ConversationTab uses a type in Tool~Terminal.
- The types involved
Core~ConversationTab.RunInTerminalToolView→Tool~Terminal.TerminalSessionCore~ConversationTab.XTermView→Tool~Terminal.TerminalSession
- Direction
- Core~ConversationTab uses Tool~Terminal, so a change to Tool~Terminal can break Core~ConversationTab, while a change to Core~ConversationTab can't break Tool~Terminal.
- Position
- Below the diagonal: Core~ConversationTab uses a module listed above it, which is the healthy direction.
38→39 Core~ConversationTab uses Core~ChatService part of a loop✕
- Connections
- 5 pairs of types, where a type in Core~ConversationTab uses a type in Core~ChatService.
- The types involved
Core~ConversationTab.Chat→Core~ChatService.ChatServiceCore~ConversationTab.ChatMenu→Core~ChatService.ChatServiceCore~ConversationTab.ConversationCodeReviewFeature→Core~ChatService.ChatServiceCore~ConversationTab.ConversationTab→Core~ChatService.ChatServiceCore~ConversationTab.State→Core~ChatService.ConversationSkill
- Direction
- Core~ConversationTab uses Core~ChatService, so a change to Core~ChatService can break Core~ConversationTab, while a change to Core~ConversationTab can't break Core~ChatService.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
39→2 Core~ChatService uses Tool~Preferences✕
- Connections
- 29 pairs of types, where a type in Core~ChatService uses a type in Tool~Preferences. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Core~ChatService.Array→Tool~Preferences.IntCore~ChatService.ChatService→Tool~Preferences.BoolCore~ChatService.ChatService→Tool~Preferences.IntCore~ChatService.ChatServiceType→Tool~Preferences.BoolCore~ChatService.ConversationSkill→Tool~Preferences.BoolCore~ChatService.CreateFileTool→Tool~Preferences.BoolCore~ChatService.CurrentEditorSkill→Tool~Preferences.BoolCore~ChatService.FetchWebPageApprovalStorage→Tool~Preferences.BoolCore~ChatService.FetchWebPageTool→Tool~Preferences.BoolCore~ChatService.GetErrorsTool→Tool~Preferences.BoolCore~ChatService.GetTerminalOutputTool→Tool~Preferences.BoolCore~ChatService.ICopilotTool→Tool~Preferences.BoolCore~ChatService.InsertEditIntoFileTool→Tool~Preferences.BoolCore~ChatService.InsertEditIntoFileTool→Tool~Preferences.IntCore~ChatService.MCPApprovalStorage→Tool~Preferences.BoolCore~ChatService.MCPApprovalStorage→Tool~Preferences.UserDefaultsTypeCore~ChatService.ProblemsInActiveDocumentSkill→Tool~Preferences.BoolCore~ChatService.ProjectContextSkill→Tool~Preferences.BoolCore~ChatService.RunInTerminalTool→Tool~Preferences.BoolCore~ChatService.SensitiveFileApprovalStorage→Tool~Preferences.BoolCore~ChatService.SensitiveFileApprovalStorage→Tool~Preferences.SensitiveFilesRulesCore~ChatService.SensitiveFileApprovalStorage→Tool~Preferences.UserDefaultsTypeCore~ChatService.ServerApprovalState→Tool~Preferences.BoolCore~ChatService.TerminalApprovalStorage→Tool~Preferences.BoolCore~ChatService.TerminalApprovalStorage→Tool~Preferences.TerminalCommandsRules
- 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.
39→5 Core~ChatService uses Tool~GitHelper✕
- Connections
- 2 pairs of types, where a type in Core~ChatService uses a type in Tool~GitHelper.
- The types involved
Core~ChatService.ChatService→Tool~GitHelper.GitDiffGroupCore~ChatService.CodeReviewProvider→Tool~GitHelper.PRChange
- Direction
- Core~ChatService uses Tool~GitHelper, so a change to Tool~GitHelper can break Core~ChatService, while a change to Core~ChatService can't break Tool~GitHelper.
- Position
- Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
39→7 Core~ChatService uses Tool~Persist✕
- Connections
- 2 pairs of types, where a type in Core~ChatService uses a type in Tool~Persist.
- The types involved
Core~ChatService.Array→Tool~Persist.ConversationItemCore~ChatService.Array→Tool~Persist.TurnItem
- Direction
- Core~ChatService uses Tool~Persist, so a change to Tool~Persist can break Core~ChatService, while a change to Core~ChatService can't break Tool~Persist.
- Position
- Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
39→8 Core~ChatService uses Tool~SuggestionBasic✕
- Connections
- 3 pairs of types, where a type in Core~ChatService uses a type in Tool~SuggestionBasic.
- The types involved
Core~ChatService.ChatInjector→Tool~SuggestionBasic.CursorRangeCore~ChatService.ChatInjector→Tool~SuggestionBasic.ModificationCore~ChatService.EditorInformation→Tool~SuggestionBasic.CodeLanguage
- Direction
- Core~ChatService uses Tool~SuggestionBasic, so a change to Tool~SuggestionBasic can break Core~ChatService, while a change to Core~ChatService can't break Tool~SuggestionBasic.
- Position
- Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
39→12 Core~ChatService uses Tool~ChatTab✕
- Connections
- 2 pairs of types, where a type in Core~ChatService uses a type in Tool~ChatTab.
- The types involved
Core~ChatService.ChatService→Tool~ChatTab.ChatTabInfoCore~ChatService.ToolContextProvider→Tool~ChatTab.ChatTabInfo
- Direction
- Core~ChatService uses Tool~ChatTab, so a change to Tool~ChatTab can break Core~ChatService, while a change to Core~ChatService can't break Tool~ChatTab.
- Position
- Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
39→17 Core~ChatService uses Tool~GitHubCopilotService✕
- Connections
- 10 pairs of types, where a type in Core~ChatService uses a type in Tool~GitHubCopilotService.
- The types involved
Core~ChatService.ChatService→Tool~GitHubCopilotService.CompressionHandlerCore~ChatService.ChatService→Tool~GitHubCopilotService.ConversationContextHandlerCore~ChatService.ChatService→Tool~GitHubCopilotService.ConversationProgressBeginCore~ChatService.ChatService→Tool~GitHubCopilotService.ConversationProgressEndCore~ChatService.ChatService→Tool~GitHubCopilotService.ConversationProgressHandlerCore~ChatService.ChatService→Tool~GitHubCopilotService.ConversationProgressReportCore~ChatService.ChatService→Tool~GitHubCopilotService.WatchedFilesHandlerCore~ChatService.ConversationSkill→Tool~GitHubCopilotService.ConversationContextParamsCore~ChatService.CurrentEditorSkill→Tool~GitHubCopilotService.ConversationContextParamsCore~ChatService.ProblemsInActiveDocumentSkill→Tool~GitHubCopilotService.ConversationContextParams
- Direction
- Core~ChatService uses Tool~GitHubCopilotService, so a change to Tool~GitHubCopilotService can break Core~ChatService, while a change to Core~ChatService can't break Tool~GitHubCopilotService.
- Position
- Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
39→19 Core~ChatService uses Tool~XcodeInspector✕
- Connections
- 2 pairs of types, where a type in Core~ChatService uses a type in Tool~XcodeInspector.
- The types involved
Core~ChatService.InsertEditIntoFileTool→Tool~XcodeInspector.AppInstanceInspectorCore~ChatService.Utils→Tool~XcodeInspector.XcodeAppInstanceInspector
- Direction
- Core~ChatService uses Tool~XcodeInspector, so a change to Tool~XcodeInspector can break Core~ChatService, while a change to Core~ChatService can't break Tool~XcodeInspector.
- Position
- Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
39→20 Core~ChatService uses Tool~ChatAPIService✕
- Connections
- 10 pairs of types, where a type in Core~ChatService uses a type in Tool~ChatAPIService.
- The types involved
Core~ChatService.Array→Tool~ChatAPIService.ConversationReferenceCore~ChatService.ChatService→Tool~ChatAPIService.ChatMessageCore~ChatService.ChatService→Tool~ChatAPIService.FileEditCore~ChatService.ChatService→Tool~ChatAPIService.RequestTypeCore~ChatService.ChatService→Tool~ChatAPIService.TurnStatusCore~ChatService.ContextAwareAutoManagedChatMemory→Tool~ChatAPIService.AutoManagedChatMemoryCore~ChatService.ContextAwareAutoManagedChatMemory→Tool~ChatAPIService.ChatMemoryCore~ChatService.ContextAwareAutoManagedChatMemory→Tool~ChatAPIService.ChatMessageCore~ChatService.ToolCallStatusUpdater→Tool~ChatAPIService.ChatMessageCore~ChatService.ToolContextProvider→Tool~ChatAPIService.FileEdit
- Direction
- Core~ChatService uses Tool~ChatAPIService, so a change to Tool~ChatAPIService can break Core~ChatService, while a change to Core~ChatService can't break Tool~ChatAPIService.
- Position
- Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
39→21 Core~ChatService uses Tool~ConversationServiceProvider✕
- Connections
- 31 pairs of types, where a type in Core~ChatService uses a type in Tool~ConversationServiceProvider. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Core~ChatService.ChatService→Tool~ConversationServiceProvider.AgentRoundCore~ChatService.ChatService→Tool~ConversationServiceProvider.ChatCompletionContentPartImageCore~ChatService.ChatService→Tool~ConversationServiceProvider.CodeReviewRoundCore~ChatService.ChatService→Tool~ConversationServiceProvider.ContextSizeInfoCore~ChatService.ChatService→Tool~ConversationServiceProvider.ConversationAttachedReferenceCore~ChatService.ChatService→Tool~ConversationServiceProvider.ConversationCreateResponseCore~ChatService.ChatService→Tool~ConversationServiceProvider.ConversationRatingCore~ChatService.ChatService→Tool~ConversationServiceProvider.ConversationRequestCore~ChatService.ChatService→Tool~ConversationServiceProvider.ConversationServiceProviderCore~ChatService.ChatService→Tool~ConversationServiceProvider.DocCore~ChatService.ChatService→Tool~ConversationServiceProvider.InvokeClientToolParamsCore~ChatService.ChatService→Tool~ConversationServiceProvider.ToolCallStatusCore~ChatService.ChatServiceType→Tool~ConversationServiceProvider.ChatCompletionContentPartImageCore~ChatService.ChatServiceType→Tool~ConversationServiceProvider.ConversationAttachedReferenceCore~ChatService.ChatServiceType→Tool~ConversationServiceProvider.ConversationRatingCore~ChatService.ChatServiceType→Tool~ConversationServiceProvider.ImageReferenceCore~ChatService.CodeReviewProvider→Tool~ConversationServiceProvider.CodeReviewRequestCore~ChatService.CodeReviewProvider→Tool~ConversationServiceProvider.CodeReviewResultCore~ChatService.CodeReviewService→Tool~ConversationServiceProvider.FileCommentCore~ChatService.CodeReviewService→Tool~ConversationServiceProvider.ReviewCommentCore~ChatService.CurrentEditorSkill→Tool~ConversationServiceProvider.ConversationFileReferenceCore~ChatService.DocumentReview→Tool~ConversationServiceProvider.ReviewCommentCore~ChatService.ICopilotTool→Tool~ConversationServiceProvider.ToolInvocationStatusCore~ChatService.SharedChatService→Tool~ConversationServiceProvider.ChatAgentCore~ChatService.SharedChatService→Tool~ConversationServiceProvider.ChatTemplate
- Direction
- Core~ChatService uses Tool~ConversationServiceProvider, so a change to Tool~ConversationServiceProvider can break Core~ChatService, while a change to Core~ChatService can't break Tool~ConversationServiceProvider.
- Position
- Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
39→27 Core~ChatService uses repository✕
- Connections
- 1 pair of types, where a type in Core~ChatService uses a type in repository.
- The types involved
Core~ChatService.ChatService→repository.CustomCommand
- Direction
- Core~ChatService uses repository, so a change to repository can break Core~ChatService, while a change to Core~ChatService can't break repository.
- Position
- Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
39→28 Core~ChatService uses Tool~AXExtension✕
- Connections
- 2 pairs of types, where a type in Core~ChatService uses a type in Tool~AXExtension.
- The types involved
Core~ChatService.ChatInjector→Tool~AXExtension.AXUIElementCore~ChatService.InsertEditIntoFileTool→Tool~AXExtension.AXUIElement
- Direction
- Core~ChatService uses Tool~AXExtension, so a change to Tool~AXExtension can break Core~ChatService, while a change to Core~ChatService can't break Tool~AXExtension.
- Position
- Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
39→29 Core~ChatService uses Core~SuggestionWidget✕
- Connections
- 1 pair of types, where a type in Core~ChatService uses a type in Core~SuggestionWidget.
- The types involved
Core~ChatService.EditorInformation→Core~SuggestionWidget.Content
- Direction
- Core~ChatService uses Core~SuggestionWidget, so a change to Core~SuggestionWidget can break Core~ChatService, while a change to Core~ChatService can't break Core~SuggestionWidget.
- Position
- Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
39→30 Core~ChatService uses Core~XcodeThemeController✕
- Connections
- 2 pairs of types, where a type in Core~ChatService uses a type in Core~XcodeThemeController.
- The types involved
Core~ChatService.ChatService→Core~XcodeThemeController.ErrorCore~ChatService.ChatServiceError→Core~XcodeThemeController.Error
- Direction
- Core~ChatService uses Core~XcodeThemeController, so a change to Core~XcodeThemeController can break Core~ChatService, while a change to Core~ChatService can't break Core~XcodeThemeController.
- Position
- Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
39→31 Core~ChatService uses Tool~FileSystem✕
- Connections
- 1 pair of types, where a type in Core~ChatService uses a type in Tool~FileSystem.
- The types involved
Core~ChatService.Array→Tool~FileSystem.WritableByteStream
- Direction
- Core~ChatService uses Tool~FileSystem, so a change to Tool~FileSystem can break Core~ChatService, while a change to Core~ChatService can't break Tool~FileSystem.
- Position
- Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
39→33 Core~ChatService uses Core~HostApp✕
- Connections
- 28 pairs of types, where a type in Core~ChatService uses a type in Core~HostApp. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Core~ChatService.ActiveThinkingCursor→Core~HostApp.StringCore~ChatService.Array→Core~HostApp.StringCore~ChatService.ChatInjector→Core~HostApp.StringCore~ChatService.ChatService→Core~HostApp.StringCore~ChatService.ChatService.swift→Core~HostApp.StringCore~ChatService.ChatServiceError→Core~HostApp.StringCore~ChatService.ChatServiceType→Core~HostApp.StringCore~ChatService.CodeReviewService→Core~HostApp.StringCore~ChatService.ConversationSkill→Core~HostApp.StringCore~ChatService.CopilotToolRegistry→Core~HostApp.StringCore~ChatService.CurrentEditorSkill→Core~HostApp.StringCore~ChatService.CustomCommandTemplateProcessor→Core~HostApp.StringCore~ChatService.DocumentReview→Core~HostApp.StringCore~ChatService.FetchWebPageApprovalStorage→Core~HostApp.StringCore~ChatService.ICopilotTool→Core~HostApp.StringCore~ChatService.InsertEditError→Core~HostApp.StringCore~ChatService.InsertEditIntoFileTool→Core~HostApp.StringCore~ChatService.MCPApprovalStorage→Core~HostApp.StringCore~ChatService.ProblemsInActiveDocumentSkill→Core~HostApp.StringCore~ChatService.ProjectContextSkill→Core~HostApp.StringCore~ChatService.SensitiveFileApprovalStorage→Core~HostApp.StringCore~ChatService.TerminalApprovalStorage→Core~HostApp.StringCore~ChatService.ToolAutoApprovalManager→Core~HostApp.StringCore~ChatService.ToolCallRequest→Core~HostApp.StringCore~ChatService.ToolCallStatusUpdater→Core~HostApp.String
- Direction
- Core~ChatService uses Core~HostApp, so a change to Core~HostApp can break Core~ChatService, while a change to Core~ChatService can't break Core~HostApp.
- Position
- Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
39→38 Core~ChatService uses Core~ConversationTab✕
- Connections
- 6 pairs of types, where a type in Core~ChatService uses a type in Core~ConversationTab.
- The types involved
Core~ChatService.ChatService→Core~ConversationTab.URLCore~ChatService.CreateFileTool→Core~ConversationTab.URLCore~ChatService.EditorInformation→Core~ConversationTab.URLCore~ChatService.InsertEditIntoFileTool→Core~ConversationTab.URLCore~ChatService.ToolContextProvider→Core~ConversationTab.URLCore~ChatService.WorkspaceInvocationCoordinator→Core~ConversationTab.URL
- Direction
- Core~ChatService uses Core~ConversationTab, so a change to Core~ConversationTab can break Core~ChatService, while a change to Core~ChatService can't break Core~ConversationTab.
- Position
- Below the diagonal: Core~ChatService uses a module listed above it, which is the healthy direction.
40→2 Tool~HostAppActivator uses Tool~Preferences✕
- Connections
- 1 pair of types, where a type in Tool~HostAppActivator uses a type in Tool~Preferences.
- The types involved
Tool~HostAppActivator.HostAppActivator.swift→Tool~Preferences.Bool
- Direction
- Tool~HostAppActivator uses Tool~Preferences, so a change to Tool~Preferences can break Tool~HostAppActivator, while a change to Tool~HostAppActivator can't break Tool~Preferences.
- Position
- Below the diagonal: Tool~HostAppActivator uses a module listed above it, which is the healthy direction.
40→27 Tool~HostAppActivator uses repository✕
- Connections
- 1 pair of types, where a type in Tool~HostAppActivator uses a type in repository.
- The types involved
Tool~HostAppActivator.HostAppActivator.swift→repository.NSRunningApplication
- Direction
- Tool~HostAppActivator uses repository, so a change to repository can break Tool~HostAppActivator, while a change to Tool~HostAppActivator can't break repository.
- Position
- Below the diagonal: Tool~HostAppActivator uses a module listed above it, which is the healthy direction.
40→30 Tool~HostAppActivator uses Core~XcodeThemeController✕
- Connections
- 1 pair of types, where a type in Tool~HostAppActivator uses a type in Core~XcodeThemeController.
- The types involved
Tool~HostAppActivator.GitHubCopilotForXcodeSettingsLaunchError→Core~XcodeThemeController.Error
- Direction
- Tool~HostAppActivator uses Core~XcodeThemeController, so a change to Core~XcodeThemeController can break Tool~HostAppActivator, while a change to Tool~HostAppActivator can't break Core~XcodeThemeController.
- Position
- Below the diagonal: Tool~HostAppActivator uses a module listed above it, which is the healthy direction.
40→33 Tool~HostAppActivator uses Core~HostApp✕
- Connections
- 2 pairs of types, where a type in Tool~HostAppActivator uses a type in Core~HostApp.
- The types involved
Tool~HostAppActivator.GitHubCopilotForXcodeSettingsLaunchError→Core~HostApp.StringTool~HostAppActivator.HostAppActivator.swift→Core~HostApp.String
- Direction
- Tool~HostAppActivator uses Core~HostApp, so a change to Core~HostApp can break Tool~HostAppActivator, while a change to Tool~HostAppActivator can't break Core~HostApp.
- Position
- Below the diagonal: Tool~HostAppActivator uses a module listed above it, which is the healthy direction.
40→38 Tool~HostAppActivator uses Core~ConversationTab✕
- Connections
- 1 pair of types, where a type in Tool~HostAppActivator uses a type in Core~ConversationTab.
- The types involved
Tool~HostAppActivator.HostAppActivator.swift→Core~ConversationTab.URL
- Direction
- Tool~HostAppActivator uses Core~ConversationTab, so a change to Core~ConversationTab can break Tool~HostAppActivator, while a change to Tool~HostAppActivator can't break Core~ConversationTab.
- Position
- Below the diagonal: Tool~HostAppActivator uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 10 | High / Critical |
Roadmap
First, address the missing architectural decision records by documenting significant design choices and establishing a dedicated folder for them. Next, resolve the floating branch dependencies to ensure stable and predictable builds. Finally, improve page structure by adding required semantic elements and implement comprehensive logging to capture diagnostic trails for user-reported bugs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.8 pts | Low | ADR Quality |
| Resolve the 9 Floating branch dependency finding(s) in Dependency Hygiene. | +3.5 pts | Low | Dependency Hygiene |
| Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with SwiftFocusedCodeFinderTests.swift. | +2.5 pts | Low | Test Quality |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +3.5 pts | Medium | Page structure |
| 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. | +3.4 pts | Medium | Architecture documentation |
| 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. | +3.4 pts | Medium | Observability |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +3.3 pts | Medium | Visual & motion safety |
| Enforce accessibility in the toolchain: add an a11y linter that can read your UI — no component framework was detected, so the JSX/Vue ESLint plugins would have nothing to lint; use an HTML-template a11y linter (html-eslint, htmlhint) or run axe/pa11y over the rendered pages, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI. | +3.1 pts | Medium | A11y enforcement |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.4 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift | 5.6 | Mixed | Cognitive Complexity: GitHubCopilotService.refreshClientTools (cognitive 25) |
| Core/Sources/ConversationTab/Chat.swift | 6.0 | Mixed | Explicit Debt: TodoComment |
| Core/Sources/ChatService/ChatService.swift | 6.0 | Mixed | Explicit Debt: TodoComment |
| Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift | 6.0 | Mixed | Explicit Debt: TodoComment |
| Tool/Sources/Workspace/FileChangeWatcher/BatchingFileChangeWatcher.swift | 6.0 | Mixed | Explicit Debt: TodoComment |
| Tool/Sources/Workspace/WorkspaceFile.swift | 6.0 | Mixed | Explicit Debt: TodoComment |
| Server/src/terminal/terminalAddon.ts | 6.0 | Mixed | Explicit Debt: TodoComment |
| Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift | 6.0 | Mixed | Explicit Debt: TodoComment |
| Tool/Tests/FocusedCodeFinderTests/SwiftFocusedCodeFinderTests.swift | 6.2 | Mixed | Test Quality: No assertions (empty test): test_selecting_a_line_in_freestanding_macro_the_scope_should_be_the_macro |
| Core/Sources/ConversationTab/Styles.swift | 6.3 | Mixed | God Classes: TooManyMethods: View |
| Core/Sources/ConversationTab/ConversationTab.swift | 6.7 | Mixed | Explicit Debt: TodoComment |
| Tool/Sources/GitHelper/CurrentChange.swift | 6.7 | Mixed | Explicit Debt: TodoComment |
| Tool/Sources/Persist/Storage/ConversationStorage/ConversationStorage.swift | 6.7 | Mixed | Explicit Debt: TodoComment |
| Tool/Sources/GitHubCopilotService/LanguageServer/CustomJSONRPCServerConnection.swift | 6.7 | Mixed | Explicit Debt: TodoComment |
| Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift | 6.7 | Mixed | Explicit Debt: TodoComment |
| Tool/Sources/SuggestionProvider/PostProcessingSuggestionServiceMiddleware.swift | 6.7 | Mixed | Explicit Debt: TodoComment |
| Core/Sources/LaunchAgentManager/LaunchAgentManager.swift | 6.7 | Mixed | Explicit Debt: TodoComment |
| Tool/Sources/Workspace/Filespace.swift | 6.7 | Mixed | Explicit Debt: TodoComment |
| Core/Sources/SuggestionWidget/WidgetWindowsController.swift | 7.0 | Near-clean | Cyclomatic Complexity: WidgetWindowsController.updateWindowOpacity (cyclomatic 33) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 76 of 76 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 76 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 383 of 452 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in Core produced no coverage export. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.swift) and this repository declares a SwiftPM test suite (2 packages), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 6 of this repository's SwiftPM dependencies could not be fetched at a pinned revision and are repositories api.deps.dev has not indexed, so their licences were not read and the verdict does not cover them: cgeventoverride, copilotforxcodekit, highlightr, keyboardshortcuts, languageclient, swiftui-flow-layout.
- D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its SwiftPM package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (6 contributor(s) across 115 commit(s) sampled, automation and bot accounts excluded). One of them holds 85% of the history; the other 5 hold 3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22'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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `CommunicationBridge/ServiceDelegate.swift`, `Core/Sources/ChatService/ChatService.swift`, `Core/Sources/ChatService/CodeReview/CodeReviewProvider.swift`, `Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalParsingHelpers.swift`, `Core/Sources/ChatService/ToolCalls/InsertEditIntoFileTool.swift`, … (+55 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository'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.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 2 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Python, Swift is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Python, Swift is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P1 CI/CD gates — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- 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.
Dimensions
D1 · Cyclomatic Complexity
46 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Chat.body at 151. A further 5 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being LanguageIdentifier.fileExtensions at 58 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Tool/Sources/SuggestionBasic/LanguageIdentifierFromFilePath.swift (LanguageIdentifier.fileExtensions at 58), Tool/Sources/GitHubCopilotService/LanguageServer/CustomJSONRPCServerConnection.swift (CustomJSONRPCServerConnection.sendRequest at 50), Tool/Sources/SharedUIComponents/Base/FileIcon.swift (FileIcon.swift.drawFileIcon at 23), Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift (GitHubCopilotError.errorDescription at 19). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with Chat.body (cyclomatic 151), ChatPanelFeature.body (cyclomatic 72). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 5.6 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
94 method(s) exceeded the cognitive complexity threshold of 15; the worst was Chat.body at 186.
What to do
- Bring the 5 bodies over 60 down to 60 or less in Cognitive Complexity — start with Chat.body (cognitive 186), ChatMessage.mergeEditAgentRounds (cognitive 158), ChatMemory.appendMessage (cognitive 130). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cognitive Complexity from 5.4 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
39 god class(es) detected.
What to do
- Resolve the 13 MethodTooLong finding(s) in God Classes — start with Chat.swift, ChatPanelFeature.swift, WidgetFeature.swift. — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 11 FileTooLong finding(s) in God Classes — start with GitHubCopilotService.swift, Chat.swift, ChatService.swift. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 8 TooManyMethods finding(s) in God Classes — start with ChatService.swift, GitHubCopilotService.swift, XPCExtensionService.swift. — One of this dimension's main actionable groups (8 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
88 duplicated block group(s) detected. A further 4 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 7 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with GitHubCopilotViewModel.swift (2), ToolStatusItemView.swift, QuotaView.swift. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 6 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with ChatMemory.swift (2), ApiKeySheet.swift, GraphicalUserInterfaceController.swift. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 6 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with ChatPanel.swift, Styles.swift, ToolStatusItemView.swift. — One of this dimension's main actionable groups (6 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
62 production modules (npm+SwiftPM+Xcode), 0 dependency cycle(s), 7 unstable depended-on module(s). Read from the build's own module declarations; a workspace's implicit (product-name) dependency is not visible there; 18 module(s) off the main sequence, with abstractness counted on 58 of the 62 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 18 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (18 warning-level).
- Resolve the 1 Unstable project ChatService finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Unstable project ConversationTab finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
15 of 133 classes have LCOM4 above 3.
What to do
- Resolve the 15 Low cohesion finding(s) in Cohesion (LCOM4) — start with ChatService.swift (2), Styles.swift, GitHubCopilotService.swift. — One of this dimension's main actionable groups (15 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
219 test methods: 200 unit, 0 integration, 19 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 13 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 219 tests (1 harness-style project(s) excluded from the assertion penalty).
What to do
- Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with SwiftFocusedCodeFinderTests.swift. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 10 No direct assertions finding(s) in Test Quality — start with TabToAcceptSuggestionTests.swift (10). — One of this dimension's main actionable groups (10 recommendation-level).
- Resolve the 2 No assertions finding(s) in Test Quality — start with BreakLinePerformanceTests.swift, SourceEditorCachePerformanceTests.swift. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D12 · Dependency Hygiene
24 outdated direct SwiftPM dependencies, 9 pinning defect(s). 34 of 61 direct dependencies had their releases listed (0 naming no readable repository, 27 pinned to a branch or a revision rather than a version). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question.
What to do
- Resolve the 9 Floating branch dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (9 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 32 SwiftPM package(s) use a banned license. SwiftPM has no package registry, so each package's licence is the one its repository declares: 18 of them read from the licence file the repository carries at the revision REDACTED pins, and 14 — unpinned, or whose licence file could not be read or named — from api.deps.dev, which reports the licence the repository declares today. Graded: every package a committed REDACTED pins, direct and transitive, and every declared dependency none pins. 23 of them are declared by a manifest that commits no REDACTED (a library, whose resolution is its consumer's), so their own dependencies are resolved by whoever builds it and are not in this verdict. 1 of them declare no licence that matches a known SPDX licence; that is missing data, not a violation, and none of them is charged. ★ 6 package(s) could not be read at a pinned revision and are not known to the index, and were NOT graded — this verdict does not cover them: `cgeventoverride`, `copilotforxcodekit`, `highlightr`, `keyboardshortcuts`, `languageclient`, `swiftui-flow-layout`. ★ COVERAGE OF THIS VERDICT: it grades this repository's SwiftPM package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
29 deducted task-comment markers across 73217 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 29 TodoComment finding(s) in Explicit Debt — start with ChatService.swift (3), Package.swift (2), terminalAddon.ts (2). — One of this dimension's main actionable groups (29 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 5 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
2 of 4 build units (SwiftPM, Xcode, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
D30 · Dependency Vulnerabilities
10 finding(s): 0 critical, 5 high, 3 medium, 2 low.
What to do
- Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 278 of the 502 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — Server/src/diffView/diffView.html:2, Server/src/terminal/terminal.html:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — Server/src/diffView/diffView.html:2
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — Server/src/terminal/terminal.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety
- `.action-button.secondary` sets color: #DFDEDF on background-color: #6E6D70 — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — Server/src/diffView/css/style.css:94
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (an a11y linter that can read your UI — no component framework was detected, so the JSX/Vue ESLint plugins would have nothing to lint; use an HTML-template a11y linter (html-eslint, htmlhint) or run axe/pa11y over the rendered pages) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 2 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the toolchain: add an a11y linter that can read your UI — no component framework was detected, so the JSX/Vue ESLint plugins would have nothing to lint; use an HTML-template a11y linter (html-eslint, htmlhint) or run axe/pa11y over the rendered pages, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
AX9 · CQS / query purity
DM4 · Rich vs anemic domain model
DM5 · Encapsulated state
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 3 of 3 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
- Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
M4 · Documentation accuracy
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`xcodebuild test` for the toolchain this pipeline already uses) and gate merges on it.
P10 · Library API & versioning
P2 · Observability
- 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.
P3 · Security & performance tooling
What to do
- Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF2 · Allocation hygiene
What to do
- Raise allocation-aware density on the hot paths — currently 8 use(s) across 82,821 production line(s) (~0.1/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
- Swift: on hot paths, reserveCapacity before appending, use ContiguousArray for class-element arrays, work in place with withUnsafeBufferPointer/withUnsafeTemporaryAllocation, and make large values ~Copyable with borrowing/consuming parameters.
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- Server/src/diffView/js/ui-controller.ts:84 · Server/src/diffView/js/ui-controller.ts:108 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — Server/src/diffView/js/ui-controller.ts:84
- Server/src/diffView/js/api.ts:82 · Server/src/diffView/js/monaco-diff-editor.ts:243 — the two spans are one implementation copied and then locally edited — 106 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — Server/src/diffView/js/api.ts:82
- Server/src/terminal/terminalAddon.ts:93 · Server/src/terminal/terminalAddon.ts:132 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — Server/src/terminal/terminalAddon.ts:93
- Server/src/diffView/js/monaco-diff-editor.ts:61 · Server/src/diffView/js/monaco-diff-editor.ts:243 — the two spans are one implementation copied and then locally edited — 56 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — Server/src/diffView/js/monaco-diff-editor.ts:61
- Server/src/terminal/terminalAddon.ts:132 · Server/src/terminal/terminalAddon.ts:142 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — Server/src/terminal/terminalAddon.ts:132
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- handleSingleLine has cyclomatic complexity 12 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Server/src/terminal/terminalAddon.ts:125
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
- test ✗ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add a test runner (vitest / jest / playwright) and eslint as package.json scripts and run them in CI.
R7 · Dead Code
R8 · Dependency Hygiene
- Declared in Server/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×5) — Tool/Sources/XcodeInspector/SourceEditor.swift:92, Tool/Sources/XcodeInspector/Apps/XcodeAppInstanceInspector.swift:416, Tool/Sources/SharedUIComponents/SyntaxHighlighting.swift:152, …
- `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×8) — Tool/Sources/XPCShared/XPCService.swift:150, Tool/Sources/FileSystem/FileSystem.swift:871, Tool/Sources/FileSystem/FileSystem.swift:884, …
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 81% | Strong | Solid. |
| Architecture | 89% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 55% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 46% | Adequate — gated by D12, R6, P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 92% | Exemplary | Solid. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Accessibility | 45% | Adequate — gated by AC3, AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 77% | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 16 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- 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 — 56 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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.
- D21 Naming Consistency — Naming consistency is measured on C# only; Swift, TypeScript not measured.
- 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+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .py, .swift, .ts, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.swift), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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) — 60 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release).
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — Swift suite
- DM1 Aggregate boundaries — not scored for Swift: the sidecar flattens array/collection types (a child COLLECTION = legitimate membership vs a single embedded aggregate is indistinguishable), and aggregate-vs-value-object classification cannot be told apart in source (every struct-holding-struct reads alike) — reported as guidance rather than measured
- DM2 Strongly-typed ids — no in-repo typed-id idiom — primitive-obsession recorded as advisory DM8, DM2 not gated
- DM3 Integration-event coupling — not scored for Swift: a cross-SwiftPM-target domain leak cannot be told apart in source from a legitimate shared-kernel/contracts module, and most repositories ship a single module — reported as guidance rather than measured
- DM6 Domain ↔ infrastructure boundary — this Swift package maps no type to a persistence framework and declares no domain-model type carrying a method of its own, so DM6's domain↔infrastructure boundary read has no population to be taken over
- DM7 Repository granularity — not scored for Swift: 'a repository per CHILD entity' needs the aggregate-root structure, which is not source-resolvable — reported as guidance rather than measured
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python, Swift source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `swift test --enable-code-coverage` (SwiftPM) or `xcodebuild test -scheme <YourScheme> -enableCodeCoverage YES` (an .xcodeproj/.xcworkspace suite), then `xcrun llvm-cov export -format=lcov`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — the JS/TS workspace (6 production file(s)) has no JavaScript/TypeScript test, but it is 1.31% of this repository's production source and the other 98.69% carries 5,332 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 9 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <html> without a lang Server/src/diffView/diffView.html:2
- <html> without a lang Server/src/terminal/terminal.html:2
- Document without a <title> Server/src/terminal/terminal.html:2
- No assertions (empty test): test_selecting_a_line_in_freestanding_macro_the_scope_should_be_the_macro Tool/Tests/FocusedCodeFinderTests/SwiftFocusedCodeFinderTests.swift:345
Serious — 381 finding(s)
- TodoComment Tool/Package.swift:73
- TodoComment Tool/Package.swift:85
- TodoComment Tool/Tests/FocusedCodeFinderTests/SwiftFocusedCodeFinderTests.swift:346
- TodoComment Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:126
- TodoComment Tool/Sources/Workspace/Filespace.swift:139
- TodoComment Tool/Sources/Workspace/WorkspaceFile.swift:287
- TodoComment Tool/Sources/Workspace/FileChangeWatcher/BatchingFileChangeWatcher.swift:24
- TodoComment Tool/Sources/SuggestionProvider/PostProcessingSuggestionServiceMiddleware.swift:34
- TodoComment Tool/Sources/Persist/Storage/ConversationStorage/ConversationStorage.swift:228
- TodoComment Core/Sources/PersistMiddleware/Extensions/ChatMessage+Storage.swift:128
- TodoComment Tool/Sources/GitHubCopilotService/LanguageServer/CustomJSONRPCServerConnection.swift:41
- TodoComment Tool/Sources/GitHelper/CurrentChange.swift:65
- TodoComment Tool/Sources/Cache/AvatarCache.swift:27
- TodoComment Tool/Sources/AXExtension/AXUIElement.swift:264
- TodoComment Server/src/terminal/terminalAddon.ts:259
- TodoComment Server/src/terminal/terminalAddon.ts:263
- TodoComment Core/Sources/SuggestionWidget/CodeReviewPanelView.swift:425
- TodoComment Core/Sources/SuggestionWidget/FeatureReducers/NESSuggestionPanelFeature.swift:24
- TodoComment Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:221
- TodoComment Core/Sources/LaunchAgentManager/LaunchAgentManager.swift:117
- TodoComment Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift:485
- TodoComment Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerGalleryViewModel.swift:124
- TodoComment Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerGalleryViewModel.swift:139
- TodoComment Core/Sources/ConversationTab/Chat.swift:1339
- TodoComment Core/Sources/ConversationTab/ConversationTab.swift:29
- Off the main sequence: ActiveApplicationMonitor
- Off the main sequence: AsyncPassthroughSubject
- Off the main sequence: Cache
- Off the main sequence: CustomAsyncAlgorithms
- Off the main sequence: DebounceFunction
- Off the main sequence: FileChangeChecker
- Off the main sequence: NotificationCenterCoordinator
- Off the main sequence: UserDefaultsObserver
- Off the main sequence: SuggestionBasic
- Off the main sequence: Logger
- Off the main sequence: AppActivator
- Off the main sequence: ChatTab
- Off the main sequence: Status
- Off the main sequence: SystemUtils
- Off the main sequence: Preferences
- Off the main sequence: ConversationServiceProvider
- Off the main sequence: LaunchAgentManager
- Off the main sequence: Toast
- Low cohesion: View (LCOM4 30) Core/Sources/ConversationTab/Styles.swift:36
- Low cohesion: GitHubCopilotService (LCOM4 14) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:442
- Low cohesion: String (LCOM4 12) Core/Sources/HostApp/ToolsConfigView.swift:267
- Low cohesion: AppDelegate (LCOM4 10) CommunicationBridge/main.swift:5
- Low cohesion: AppDelegate (LCOM4 10) ExtensionService/AppDelegate.swift:33
- Low cohesion: Array (LCOM4 7) Core/Sources/ChatService/ChatService.swift:1422
- Low cohesion: Filespace (LCOM4 7) Tool/Sources/Workspace/Filespace.swift:64
- Low cohesion: AXUIElement (LCOM4 6) Tool/Sources/AXExtension/AXUIElement+Xcode.swift:5
- Low cohesion: BuiltinExtensionSuggestionServiceProvider (LCOM4 5) Tool/Sources/BuiltinExtension/BuiltinExtensionSuggestionServiceProvider.swift:8
- Low cohesion: ChatService (LCOM4 4) Core/Sources/ChatService/ChatService.swift:63
- Low cohesion: Coordinator (LCOM4 4) Core/Sources/ConversationTab/DiffViews/DiffWebView.swift:97
- Low cohesion: ChatPanelWindow (LCOM4 4) Core/Sources/SuggestionWidget/ChatPanelWindow.swift:9
- Low cohesion: AutoManagedChatMemory (LCOM4 4) Tool/Sources/ChatAPIService/Memory/AutoManagedChatMemory.swift:17
- Low cohesion: StatusObserver (LCOM4 4) Tool/Sources/Status/StatusObserver.swift:4
- Low cohesion: AccountItemView (LCOM4 4) Tool/Sources/StatusBarItemView/AccountItemView.swift:4
- MethodTooLong: Chat.body Core/Sources/ConversationTab/Chat.swift:689
- MethodTooLong: ChatPanelFeature.body Core/Sources/SuggestionWidget/FeatureReducers/ChatPanelFeature.swift:210
- MethodTooLong: WidgetFeature.body Core/Sources/SuggestionWidget/FeatureReducers/WidgetFeature.swift:145
- MethodTooLong: XcodeThemeParser.parseXCColorTheme Core/Sources/XcodeThemeController/XcodeThemeParser.swift:116
- MethodTooLong: LanguageIdentifier.fileExtensions Tool/Sources/SuggestionBasic/LanguageIdentifierFromFilePath.swift:51
- MethodTooLong: PanelFeature.body Core/Sources/SuggestionWidget/FeatureReducers/PanelFeature.swift:80
- MethodTooLong: GUI.body Core/Sources/Service/GUI/GraphicalUserInterfaceController.swift:65
- MethodTooLong: FixErrorPanelFeature.body Core/Sources/SuggestionWidget/FeatureReducers/FixErrorPanelFeature.swift:87
- MethodTooLong: ModelPickerDetailPanel.show Core/Sources/ConversationTab/ModeAndModelPicker/ModelPicker/ModelPickerDetailPanel.swift:398
- MethodTooLong: InputAreaTextEditor.body Core/Sources/ConversationTab/Views/ChatPanelInputArea/InputAreaTextEditor.swift:90
- MethodTooLong: AppDelegate.buildStatusBarMenu ExtensionService/AppDelegate+Menu.swift:24
- MethodTooLong: HorizontalMovable.framesForWindows Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:197
- MethodTooLong: CustomJSONRPCServerConnection.sendRequest Tool/Sources/GitHubCopilotService/LanguageServer/CustomJSONRPCServerConnection.swift:88
- FileTooLong: LanguageServer/GitHubCopilotService.swift Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift
- FileTooLong: ConversationTab/Chat.swift Core/Sources/ConversationTab/Chat.swift
- FileTooLong: ChatService/ChatService.swift Core/Sources/ChatService/ChatService.swift
- FileTooLong: SuggestionWidget/WidgetWindowsController.swift Core/Sources/SuggestionWidget/WidgetWindowsController.swift
- FileTooLong: SuggestionWidget/AgentConfigurationWidgetView.swift Core/Sources/SuggestionWidget/AgentConfigurationWidgetView.swift
- FileTooLong: ConversationServiceProvider/LSPTypes.swift Tool/Sources/ConversationServiceProvider/LSPTypes.swift
- FileTooLong: XPCShared/XPCExtensionService.swift Tool/Sources/XPCShared/XPCExtensionService.swift
- FileTooLong: GitHubCopilotRequestTypes/MCPRegistry.swift Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift
- FileTooLong: ConversationTab/ChatPanel.swift Core/Sources/ConversationTab/ChatPanel.swift
- FileTooLong: Service/XPCService.swift Core/Sources/Service/XPCService.swift
- FileTooLong: StatusBarItemView/QuotaView.swift Tool/Sources/StatusBarItemView/QuotaView.swift
- Floating branch dependency: keyboardshortcuts
- Floating branch dependency: cgeventoverride
- Floating branch dependency: highlightr
- Floating branch dependency: highlightr
- Floating branch dependency: copilotforxcodekit
- Floating branch dependency: cgeventoverride
- Floating branch dependency: copilotforxcodekit
- Floating branch dependency: highlightr
- Floating branch dependency: keyboardshortcuts
- TooManyMethods: ChatService Core/Sources/ChatService/ChatService.swift:63
- TooManyMethods: GitHubCopilotService Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:442
- TooManyMethods: XPCExtensionService Tool/Sources/XPCShared/XPCExtensionService.swift:34
- TooManyMethods: XPCService Core/Sources/Service/XPCService.swift:15
- TooManyMethods: WidgetWindowsController Core/Sources/SuggestionWidget/WidgetWindowsController.swift:12
- TooManyMethods: QuotaView Tool/Sources/StatusBarItemView/QuotaView.swift:6
- TooManyMethods: View Core/Sources/ConversationTab/Styles.swift:36
- TooManyMethods: ToolAutoApprovalManager Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalManager.swift:3
- Swallowed exception (caught, then discarded) Tool/Sources/XPCShared/XPCService.swift:150
- Swallowed exception (caught, then discarded) Tool/Sources/FileSystem/FileSystem.swift:871
- Swallowed exception (caught, then discarded) Tool/Sources/FileSystem/FileSystem.swift:884
- Swallowed exception (caught, then discarded) Tool/Sources/FileSystem/FileSystem.swift:897
- Swallowed exception (caught, then discarded) Tool/Sources/FileSystem/FileSystem.swift:910
- Swallowed exception (caught, then discarded) Tool/Sources/Cache/AvatarCache.swift:35
- Swallowed exception (caught, then discarded) Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift:399
- Swallowed exception (caught, then discarded) Core/Sources/HostApp/ToolsSettings/MCPRegistry/ServerInstallationOptionView.swift:168
- ClassTooLong: Chat Core/Sources/ConversationTab/Chat.swift:179
- ClassTooLong: GitHubCopilotService Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:442
- ClassTooLong: ChatService Core/Sources/ChatService/ChatService.swift:63
- ClassTooLong: AgentConfigurationWidgetView Core/Sources/SuggestionWidget/AgentConfigurationWidgetView.swift:25
- ClassTooLong: XPCService Core/Sources/Service/XPCService.swift:15
- ClassTooLong: InputAreaTextEditor Core/Sources/ConversationTab/Views/ChatPanelInputArea/InputAreaTextEditor.swift:18
- ClassTooLong: ModelPickerDetailPanel Core/Sources/ConversationTab/ModeAndModelPicker/ModelPicker/ModelPickerDetailPanel.swift:30
- Duplicated block (6 lines × 2) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:344
- Duplicated block (6 lines × 2) Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift:296
- Duplicated block (6 lines × 2) Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift:304
- Duplicated block (6 lines × 2) Tool/Sources/StatusBarItemView/QuotaView.swift:599
- Duplicated block (6 lines × 2) Tool/Sources/XPCShared/XPCExtensionService.swift:430
- Duplicated block (6 lines × 2) Core/Sources/ChatService/ChatService.swift:897
- Duplicated block (6 lines × 2) Core/Sources/ConversationTab/ModeAndModelPicker/ModelPicker/ModelPickerDetailPanel.swift:279
- Duplicated block (9 lines × 2) Core/Sources/HostApp/BYOKSettings/ApiKeySheet.swift:67
- Duplicated block (9 lines × 2) Core/Sources/Service/GUI/GraphicalUserInterfaceController.swift:459
- Duplicated block (9 lines × 2) Core/Sources/Service/SuggestionCommandHandler/WindowBaseCommandHandler.swift:178
- Duplicated block (9 lines × 2) Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:53
- Duplicated block (9 lines × 2) Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:184
- Duplicated block (9 lines × 2) Tool/Sources/StatusBarItemView/QuotaView.swift:335
- Duplicated block (8 lines × 2) Core/Sources/ConversationTab/ChatPanel.swift:627
- Duplicated block (8 lines × 2) Core/Sources/ConversationTab/Styles.swift:7
- Duplicated block (8 lines × 2) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:92
- Duplicated block (8 lines × 2) Tool/Sources/ConversationServiceProvider/LSPTypes+AgentRound.swift:104
- Duplicated block (8 lines × 2) Core/Sources/ChatService/ToolCalls/AutoApproval/MCPApprovalStorage.swift:79
- Duplicated block (8 lines × 2) Core/Sources/UserDefaultsObserver/UserDefaultsObserver.swift:27
- Duplicated block (5 lines × 2) Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPRegistryInstallation.swift:395
- Duplicated block (5 lines × 2) Core/Sources/LaunchAgentManager/LaunchAgentManager.swift:20
- Duplicated block (5 lines × 2) Tool/Sources/SharedUIComponents/QuotaPopoverView.swift:150
- Duplicated block (5 lines × 2) Tool/Sources/Workspace/WorkspaceDirectoryIndex.swift:61
- Duplicated block (5 lines × 2) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:155
- Duplicated block (5 lines × 2) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:488
- Duplicated block (13 lines × 2) Core/Sources/HostApp/ToolsSettings/BuiltInToolsListView.swift:58
- Duplicated block (13 lines × 2) Core/Sources/SuggestionWidget/ChatWindow/ChatNoAXPermissionView.swift:8
- Duplicated block (13 lines × 2) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/Telemetry.swift:11
- Duplicated block (13 lines × 2) Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:170
- Duplicated block (13 lines × 2) Core/Sources/HostApp/SidebarTabView.swift:37
- Duplicated block (12 lines × 2) Core/Sources/ConversationTab/TerminalViews/RunInTerminalToolView.swift:57
- Duplicated block (12 lines × 2) Core/Sources/ConversationTab/Views/BotMessage.swift:290
- Duplicated block (12 lines × 2) Core/Sources/SuggestionWidget/Providers/CodeSuggestionProvider.swift:38
- Duplicated block (12 lines × 2) Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:376
- Duplicated block (12 lines × 2) Core/Sources/UserDefaultsObserver/UserDefaultsObserver.swift:8
- Duplicated block (10 lines × 2) Core/Sources/ConversationTab/ModeAndModelPicker/ModePicker/AgentModeButton.swift:46
- Duplicated block (10 lines × 2) Core/Sources/HostApp/ToolsSettings/BuiltInToolsListView.swift:178
- Duplicated block (10 lines × 2) Core/Sources/Service/Service.swift:172
- Duplicated block (10 lines × 2) Core/Sources/Service/XPCService.swift:349
- Duplicated block (10 lines × 2) Tool/Sources/SuggestionProvider/PostProcessingSuggestionServiceMiddleware.swift:8
- Swallowed exception (empty catch) Tool/Sources/XcodeInspector/SourceEditor.swift:92
- Swallowed exception (empty catch) Tool/Sources/XcodeInspector/Apps/XcodeAppInstanceInspector.swift:416
- Swallowed exception (empty catch) Tool/Sources/SharedUIComponents/SyntaxHighlighting.swift:152
- Swallowed exception (empty catch) Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift:484
- Swallowed exception (empty catch) Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift:124
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (16 lines × 2) Core/Sources/HostApp/ToolsSettings/AutoApprove/AutoApprovalDisableView.swift:9
- Duplicated block (16 lines × 2) Core/Sources/SuggestionService/SuggestionService.swift:51
- Duplicated block (16 lines × 2) Tool/Sources/SuggestionProvider/SuggestionServiceMiddleware.swift:42
- Duplicated block (12–13 lines × 2) Core/Sources/ConversationTab/DiffViews/DiffWebView.swift:77
- Duplicated block (12–13 lines × 2) Core/Sources/HostApp/BYOKSettings/ApiKeySheet.swift:23
- Duplicated block (12–13 lines × 2) Core/Sources/SuggestionWidget/WidgetView.swift:77
- Duplicated block (11 lines × 2) Core/Sources/ConversationTab/Chat.swift:840
- Duplicated block (11 lines × 2) Core/Sources/ConversationTab/Views/ChatPanelInputArea/InputAreaTextEditor.swift:456
- Duplicated block (11 lines × 2) Tool/Sources/SharedUIComponents/DownvoteButton.swift:17
- No assertions: test_breakLines Tool/Tests/SuggestionBasicTests/BreakLinePerformanceTests.swift:6
- No assertions: test_source_editor_cache_get_content_comparison Tool/Tests/XcodeInspectorTests/SourceEditorCachePerformanceTests.swift:7
- Duplicated block (23 lines × 2) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:359
- Duplicated block (23 lines × 2) Tool/Sources/WorkspaceSuggestionService/Workspace+SuggestionService.swift:47
- Duplicated block (21 lines × 2) Tool/Sources/SuggestionProvider/SuggestionServiceMiddleware.swift:82
- Duplicated block (21 lines × 2) Tool/Sources/TelemetryService/TelemetryService.swift:76
- Duplicated block (19 lines × 2) Core/Sources/HostApp/AdvancedSettings/ChatSection.swift:430
- Duplicated block (19 lines × 2) Tool/Sources/GitHubCopilotService/Services/GitHubCopilotSuggestionService.swift:80
- Duplicated block (18 lines × 2) Core/Sources/HostApp/AdvancedSettings/ChatSection.swift:451
- Duplicated block (18 lines × 2) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:338
- Duplicated block (14 lines × 2) Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:62
- Duplicated block (14 lines × 2) Tool/Sources/Terminal/Terminal.swift:54
- Duplicated block (10–11 lines × 2) Core/Sources/KeyBindingManager/KeyBindingManager.swift:6
- Duplicated block (10–11 lines × 2) Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:39
- Duplicated block (8–9 lines × 2) Core/Sources/SuggestionWidget/ChatWindow/ChatHistoryView.swift:259
- Duplicated block (8–9 lines × 2) Tool/Sources/XPCShared/XPCExtensionService.swift:308
- Duplicated block (7 lines × 2) Tool/Sources/ConversationServiceProvider/LSPTypes+AgentRound.swift:118
- Duplicated block (7 lines × 2) Core/Sources/ChatService/ToolCalls/AutoApproval/MCPApprovalStorage.swift:90
- Page without a main landmark Server/src/diffView/diffView.html:2
- Low contrast colour pair in CSS (3.8:1) Server/src/diffView/css/style.css:94
- Accessibility enforcement below the top rung
- Chat.body (cyclomatic 151) Core/Sources/ConversationTab/Chat.swift:689
- ChatPanelFeature.body (cyclomatic 72) Core/Sources/SuggestionWidget/FeatureReducers/ChatPanelFeature.swift:210
- WidgetFeature.body (cyclomatic 52) Core/Sources/SuggestionWidget/FeatureReducers/WidgetFeature.swift:145
- PanelFeature.body (cyclomatic 42) Core/Sources/SuggestionWidget/FeatureReducers/PanelFeature.swift:80
- GUI.body (cyclomatic 38) Core/Sources/Service/GUI/GraphicalUserInterfaceController.swift:65
- ChatMessage.mergeEditAgentRounds (cyclomatic 38) Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:167
- CodeReviewPanelFeature.body (cyclomatic 34) Core/Sources/SuggestionWidget/FeatureReducers/CodeReviewFeature.swift:107
- WidgetWindowsController.updateWindowOpacity (cyclomatic 33) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:453
- FixErrorPanelFeature.body (cyclomatic 31) Core/Sources/SuggestionWidget/FeatureReducers/FixErrorPanelFeature.swift:87
- ChatService.handleProgressReport (cyclomatic 28) Core/Sources/ChatService/ChatService.swift:789
- ChatMemory.appendMessage (cyclomatic 27) Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:12
- HTMLToMarkdownConverter.convertSpecificElement (cyclomatic 27) Tool/Sources/WebContentExtractor/HTMLToMarkdownConverter.swift:103
- ToolAutoApprovalManager.splitTerminalCommandLineIntoSubCommands (cyclomatic 26) Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalParsingHelpers.swift:115
- ServerNotificationHandlerImpl.handleNotification (cyclomatic 25) Tool/Sources/GitHubCopilotService/LanguageServer/ServerNotificationHandler.swift:25
- ChatService.resetOngoingRequest (cyclomatic 24) Core/Sources/ChatService/ChatService.swift:1123
- NSError.from (cyclomatic 24) Core/Sources/Service/Helpers.swift:6
- PromptToCode.body (cyclomatic 23) Core/Sources/SuggestionWidget/FeatureReducers/PromptToCode.swift:150
- XcodeInspector.restart (cyclomatic 23) Tool/Sources/XcodeInspector/XcodeInspector.swift:123
- ToolStatusItemView.parsedFileListResult (cyclomatic 22) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:361
- WidgetWindowsController.generateWidgetLocation (cyclomatic 22) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:310
- HighlightrThemeManager.theme (cyclomatic 21) Core/Sources/XcodeThemeController/HighlightrThemeManager.swift:15
- ChatService.handleProgressEnd (cyclomatic 20) Core/Sources/ChatService/ChatService.swift:1019
- InputAreaTextEditor.body (cyclomatic 20) Core/Sources/ConversationTab/Views/ChatPanelInputArea/InputAreaTextEditor.swift:90
- SuggestionInjector.acceptSuggestion (cyclomatic 20) Core/Sources/SuggestionInjector/SuggestionInjector.swift:18
- WidgetWindowsController.updateAttachedChatWindowLocation (cyclomatic 20) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:555
- ToolAutoApprovalManager.extractTerminalCommandName (cyclomatic 19) Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalParsingHelpers.swift:239
- ModelPickerDetailPanel.show (cyclomatic 19) Core/Sources/ConversationTab/ModeAndModelPicker/ModelPicker/ModelPickerDetailPanel.swift:398
- PseudoCommandHandler.acceptSuggestion (cyclomatic 19) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:401
- GitHubCopilotRequest.swift.editorConfiguration (cyclomatic 19) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:55
- BatchingFileChangeWatcher.processEvent (cyclomatic 19) Tool/Sources/Workspace/FileChangeWatcher/BatchingFileChangeWatcher.swift:257
- WorkspaceXcodeWindowInspector.deriveWorkspaceFromDocumentURL (cyclomatic 19) Tool/Sources/XcodeInspector/XcodeWindowInspector.swift:126
- ChatService.send (cyclomatic 18) Core/Sources/ChatService/ChatService.swift:358
- SuggestionInjector.recoverSuffixIfNeeded (cyclomatic 18) Core/Sources/SuggestionInjector/SuggestionInjector.swift:133
- PromptToCodeGroup.body (cyclomatic 18) Core/Sources/SuggestionWidget/FeatureReducers/PromptToCodeGroup.swift:94
- XcodeThemeController.syncXcodeThemeIfNeeded (cyclomatic 18) Core/Sources/XcodeThemeController/XcodeThemeController.swift:91
- AXNotificationStream.init (cyclomatic 18) Tool/Sources/AXNotificationStream/AXNotificationStream.swift:47
- AppDelegate.menuWillOpen (cyclomatic 18) ExtensionService/AppDelegate+Menu.swift:179
- ToolAutoApprovalManager.approve (cyclomatic 17) Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalManager.swift:26
- CopilotLocalProcessServer.handleNotification (cyclomatic 17) Tool/Sources/GitHubCopilotService/LanguageServer/CopilotLocalProcessServer.swift:181
- CodeHighlighting.convertToCodeLines (cyclomatic 17) Tool/Sources/SharedUIComponents/SyntaxHighlighting.swift:76
- ToolStatusItemView.body (cyclomatic 16) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:452
- RealtimeSuggestionController.handleFocusElementChange (cyclomatic 16) Core/Sources/Service/RealtimeSuggestionController.swift:46
- AgentMCPServerSection.body (cyclomatic 16) Core/Sources/SuggestionWidget/AgentConfigurationWidgetView.swift:671
- WidgetWindowsController._updateCodeReviewWindowLocation (cyclomatic 16) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:839
- QuotaView.createUpsellView (cyclomatic 16) Tool/Sources/StatusBarItemView/QuotaView.swift:406
- QuotaView.buildFooterConstraints (cyclomatic 16) Tool/Sources/StatusBarItemView/QuotaView.swift:580
- Chat.body (cognitive 186) Core/Sources/ConversationTab/Chat.swift:689
- ChatMessage.mergeEditAgentRounds (cognitive 158) Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:167
- ChatMemory.appendMessage (cognitive 130) Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:12
- ChatPanelFeature.body (cognitive 77) Core/Sources/SuggestionWidget/FeatureReducers/ChatPanelFeature.swift:210
- WidgetFeature.body (cognitive 62) Core/Sources/SuggestionWidget/FeatureReducers/WidgetFeature.swift:145
- WidgetWindowsController.updateWindowOpacity (cognitive 57) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:453
- ToolAutoApprovalManager.splitTerminalCommandLineIntoSubCommands (cognitive 52) Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalParsingHelpers.swift:115
- GUI.body (cognitive 47) Core/Sources/Service/GUI/GraphicalUserInterfaceController.swift:65
- AppDelegate.menuWillOpen (cognitive 45) ExtensionService/AppDelegate+Menu.swift:179
- ChatService.resetOngoingRequest (cognitive 44) Core/Sources/ChatService/ChatService.swift:1123
- ToolStatusItemView.parsedFileListResult (cognitive 43) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:361
- XcodeInspector.restart (cognitive 42) Tool/Sources/XcodeInspector/XcodeInspector.swift:123
- PseudoCommandHandler.acceptSuggestion (cognitive 41) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:401
- WidgetWindowsController.generateWidgetLocation (cognitive 39) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:310
- ServerNotificationHandlerImpl.handleNotification (cognitive 38) Tool/Sources/GitHubCopilotService/LanguageServer/ServerNotificationHandler.swift:25
- ChatService.handleProgressEnd (cognitive 37) Core/Sources/ChatService/ChatService.swift:1019
- CodeReviewPanelFeature.body (cognitive 36) Core/Sources/SuggestionWidget/FeatureReducers/CodeReviewFeature.swift:107
- BatchingFileChangeWatcher.processEvent (cognitive 36) Tool/Sources/Workspace/FileChangeWatcher/BatchingFileChangeWatcher.swift:257
- NSMutableArray.apply (cognitive 34) Tool/Sources/SuggestionBasic/Modification.swift:61
- CodeHighlighting.convertToCodeLines (cognitive 32) Tool/Sources/SharedUIComponents/SyntaxHighlighting.swift:76
- WorkspaceXcodeWindowInspector.deriveWorkspaceFromDocumentURL (cognitive 31) Tool/Sources/XcodeInspector/XcodeWindowInspector.swift:126
- QuotaView.createUpsellView (cognitive 30) Tool/Sources/StatusBarItemView/QuotaView.swift:406
- ChatService.handleProgressReport (cognitive 29) Core/Sources/ChatService/ChatService.swift:789
- WidgetWindowsController.updateAttachedChatWindowLocation (cognitive 29) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:555
- FixErrorPanelFeature.body (cognitive 29) Core/Sources/SuggestionWidget/FeatureReducers/FixErrorPanelFeature.swift:87
- QuotaPopoverView.quotaContent (cognitive 29) Tool/Sources/SharedUIComponents/QuotaPopoverView.swift:55
- XcodeAppInstanceInspector.observeAXNotifications (cognitive 29) Tool/Sources/XcodeInspector/Apps/XcodeAppInstanceInspector.swift:200
- MCPAutoApproveView.body (cognitive 27) Core/Sources/HostApp/ToolsSettings/AutoApprove/MCPAutoApproveView.swift:15
- PanelFeature.body (cognitive 27) Core/Sources/SuggestionWidget/FeatureReducers/PanelFeature.swift:80
- AppInstanceInspector.triggerMenuItem (cognitive 26) Tool/Sources/XcodeInspector/XcodeInspector+TriggerCommand.swift:57
- ModelPickerDetailPanel.show (cognitive 25) Core/Sources/ConversationTab/ModeAndModelPicker/ModelPicker/ModelPickerDetailPanel.swift:398
- TabToAcceptSuggestion.handleEvent (cognitive 25) Core/Sources/KeyBindingManager/TabToAcceptSuggestion.swift:136
- RealtimeSuggestionController.handleFocusElementChange (cognitive 25) Core/Sources/Service/RealtimeSuggestionController.swift:46
- SuggestionInjector.acceptSuggestion (cognitive 25) Core/Sources/SuggestionInjector/SuggestionInjector.swift:18
- GitHubCopilotService.refreshClientTools (cognitive 25) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:1350
- ChatService.send (cognitive 24) Core/Sources/ChatService/ChatService.swift:358
- XPCService.updateToolsStatus (cognitive 24) Core/Sources/Service/XPCService.swift:480
- QuotaPopoverView.buildQuotaItems (cognitive 24) Tool/Sources/SharedUIComponents/QuotaPopoverView.swift:227
- XPCService.updateMCPServerToolsStatus (cognitive 23) Core/Sources/Service/XPCService.swift:335
- ToolStatusItemView.fileOperationProgressView (cognitive 22) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:181
- AgentMCPServerSection.body (cognitive 22) Core/Sources/SuggestionWidget/AgentConfigurationWidgetView.swift:671
- GitHubCopilotService.updateServiceAuthStatus (cognitive 22) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:1075
- ExtensionServiceLauncher.launch (cognitive 22) CommunicationBridge/ServiceDelegate.swift:134
- String.apply (cognitive 21) Tool/Sources/SuggestionBasic/Modification.swift:10
- XcodeThemeController.syncXcodeThemeIfNeeded (cognitive 21) Core/Sources/XcodeThemeController/XcodeThemeController.swift:91
- GitHunk.parseDiff (cognitive 21) Tool/Sources/GitHelper/GitHunk.swift:29
- WorkspaceFile.processWorkspaceNodes (cognitive 21) Tool/Sources/Workspace/WorkspaceFile.swift:89
- InputAreaTextEditor.body (cognitive 20) Core/Sources/ConversationTab/Views/ChatPanelInputArea/InputAreaTextEditor.swift:90
- PseudoCommandHandler.acceptPromptToCode (cognitive 20) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:339
- HighlightrThemeManager.theme (cognitive 20) Core/Sources/XcodeThemeController/HighlightrThemeManager.swift:15
- GitDiff.parseDiff (cognitive 20) Tool/Sources/GitHelper/GitDiff.swift:43
- QuotaView.buildFooterConstraints (cognitive 20) Tool/Sources/StatusBarItemView/QuotaView.swift:580
- WorkspaceFile.getFilesInActiveWorkspace (cognitive 20) Tool/Sources/Workspace/WorkspaceFile.swift:227
- ToolAutoApprovalManager.extractTerminalCommandName (cognitive 19) Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalParsingHelpers.swift:239
- ConversationTab.handlePasteEvent (cognitive 19) Core/Sources/ConversationTab/ConversationTab.swift:248
- FunctionMessage.body (cognitive 19) Core/Sources/ConversationTab/Views/FunctionMessage.swift:107
- NSError.from (cognitive 19) Core/Sources/Service/Helpers.swift:6
- HorizontalMovable.framesForWindows (cognitive 19) Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:197
- GitHubCopilotRequest.swift.editorConfiguration (cognitive 19) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:55
- WorkspaceXcodeWindowInspector.extractProjectURL (cognitive 19) Tool/Sources/XcodeInspector/XcodeWindowInspector.swift:183
- ChatPanel.onFileDrop (cognitive 18) Core/Sources/ConversationTab/ChatPanel.swift:92
- ModelPickerMenu.rebuildMenuItems (cognitive 18) Core/Sources/ConversationTab/ModeAndModelPicker/ModelPicker/ModelPickerMenu.swift:224
- MCPConfigView.body (cognitive 18) Core/Sources/HostApp/ToolsConfigView.swift:33
- ModelRowView.body (cognitive 18) Core/Sources/HostApp/BYOKSettings/ModelRowView.swift:23
- SuggestionInjector.recoverSuffixIfNeeded (cognitive 18) Core/Sources/SuggestionInjector/SuggestionInjector.swift:133
- AgentConfigurationWidgetLocationStrategy.getAgentConfigurationWidgetLocation (cognitive 18) Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:558
- PromptToCode.body (cognitive 18) Core/Sources/SuggestionWidget/FeatureReducers/PromptToCode.swift:150
- AXNotificationStream.init (cognitive 18) Tool/Sources/AXNotificationStream/AXNotificationStream.swift:47
- GitHubCopilotService.init (cognitive 18) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotService.swift:464
- AppDelegate.updateStatusBarItem (cognitive 18) ExtensionService/AppDelegate.swift:415
- TerminalAddon.handleSingleLine (cognitive 18) Server/src/terminal/terminalAddon.ts:125
- ToolCallStatusUpdater.findAndUpdateToolCall (cognitive 17) Core/Sources/ChatService/ToolCalls/ToolCallStatusUpdater.swift:26
- ToolAutoApprovalManager.approve (cognitive 17) Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalManager.swift:26
- ModelPickerDetailPanel.layoutAndShow (cognitive 17) Core/Sources/ConversationTab/ModeAndModelPicker/ModelPicker/ModelPickerDetailPanel.swift:567
- General.body (cognitive 17) Core/Sources/HostApp/General.swift:42
- ScheduledCleaner.cleanUp (cognitive 17) Core/Sources/Service/ScheduledCleaner.swift:33
- WidgetWindowsController._updateCodeReviewWindowLocation (cognitive 17) Core/Sources/SuggestionWidget/WidgetWindowsController.swift:839
- CodeBlockSuggestionPanel.body (cognitive 17) Core/Sources/SuggestionWidget/SuggestionPanelContent/CodeBlockSuggestionPanel.swift:42
- DiffBuilder.diff (cognitive 17) Core/Sources/SuggestionWidget/NES/NESDiffView/NESDiffBuilder.swift:62
- CurrentChangeService.getPRChanges (cognitive 17) Tool/Sources/GitHelper/CurrentChange.swift:14
- ConversationStorage.operate (cognitive 17) Tool/Sources/Persist/Storage/ConversationStorage/ConversationStorage.swift:78
- Terminal.streamCommand (cognitive 17) Tool/Sources/Terminal/Terminal.swift:44
- SourceEditor.observeAXNotifications (cognitive 17) Tool/Sources/XcodeInspector/SourceEditor.swift:105
- XcodeInspector.setActiveXcode (cognitive 17) Tool/Sources/XcodeInspector/XcodeInspector.swift:270
- ChatService.requestThinkingTitle (cognitive 16) Core/Sources/ChatService/ChatService.swift:920
- InputAreaTextEditor.subscribeToActiveDocumentChangeEvent (cognitive 16) Core/Sources/ConversationTab/Views/ChatPanelInputArea/InputAreaTextEditor.swift:600
- ExpandableFileListView.fileRow (cognitive 16) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ExpandableFileListView.swift:118
- ToolStatusItemView.body (cognitive 16) Core/Sources/ConversationTab/Views/ConversationAgentProgressView/ToolStatusItemView.swift:452
- GitHubCopilotViewModel.waitForSignIn (cognitive 16) Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift:148
- BuiltInToolsListView.reloadModesAndUpdateStates (cognitive 16) Core/Sources/HostApp/ToolsSettings/BuiltInToolsListView.swift:178
- MCPServerToolsSection.reloadModesAndUpdateStates (cognitive 16) Core/Sources/HostApp/ToolsSettings/MCPServerToolsSection.swift:419
- PseudoCommandHandler.generateRealtimeSuggestions (cognitive 16) Core/Sources/Service/SuggestionCommandHandler/PseudoCommandHandler.swift:54
- CopilotLanguageModelToolManager.updateToolsStatus (cognitive 16) Tool/Sources/GitHubCopilotService/LanguageServer/CopilotLanguageModelToolManager.swift:15
- QuotaView.addSubviewsToHierarchy (cognitive 16) Tool/Sources/StatusBarItemView/QuotaView.swift:73
- Members sharing a duplicated core (22 members, 50+ identical tokens) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:367
- Members sharing a duplicated core (10 members, 50+ identical tokens) Core/Sources/ConversationTab/Chat.swift:46
- Members sharing a duplicated core (5 members, 50+ identical tokens) Tool/Sources/HostAppActivator/HostAppActivator.swift:42
- Members sharing a duplicated core (4 members, 50+ identical tokens) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:269
- Duplicated block (36 lines × 2) Core/Sources/HostApp/ToolsSettings/AutoApprove/EditsAutoApproveView.swift:97
- Duplicated block (28–32 lines × 2) Core/Sources/HostApp/ToolsSettings/AutoApprove/EditsAutoApproveView.swift:25
- Duplicated block (30 lines × 2) Tool/Sources/AppActivator/AppActivator.swift:77
- Duplicated block (27 lines × 2) Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift:366
- Duplicated block (20–22 lines × 3) Core/Sources/SuggestionWidget/SuggestionPanelContent/PromptToCodePanel.swift:485
- Duplicated block (20–21 lines × 2) Core/Sources/SuggestionWidget/WidgetPositionStrategy.swift:248
- Duplicated block (20 lines × 2) Core/Sources/HostApp/AdvancedSettings/DisabledLanguageList.swift:29
- Duplicated block (17–18 lines × 2) Core/Sources/HostApp/AdvancedSettings/GlobalInstructionsView.swift:65
- Duplicated block (17 lines × 2) Core/Sources/SuggestionWidget/ChatWindow/ChatLoginView.swift:16
- Duplicated block (10–14 lines × 3) Core/Sources/HostApp/ToolsSettings/AutoApprove/EditsAutoApproveView.swift:24
- Duplicated block (12–13 lines × 4) Core/Sources/HostApp/ToolsSettings/MCPManualInstallView.swift:20
- Duplicated block (12 lines × 10) Core/Sources/ConversationTab/Chat.swift:68
- Duplicated block (11–12 lines × 2) Core/Sources/ChatService/ChatService.swift:335
- Duplicated block (9–11 lines × 2) Tool/Sources/BuiltinExtension/BuiltinExtensionConversationServiceProvider.swift:61
- Duplicated block (9–10 lines × 2) Tool/Sources/SharedUIComponents/Base/FileIcon.swift:42
- Duplicated block (7–8 lines × 3) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequestTypes/MCPRegistry.swift:116
- Duplicated block (7 lines × 5) Tool/Sources/HostAppActivator/HostAppActivator.swift:44
- Duplicated block (6–7 lines × 2) Tool/Sources/ChatAPIService/Memory/ChatMemory.swift:36
- Duplicated block (3–5 lines × 4) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:271
- Duplicated block (5 lines × 3) Tool/Sources/Persist/AppState.swift:63
- Duplicated block (10 lines × 7) EditorExtension/GetSuggestionsCommand.swift:9
- Duplicated block (7 lines × 3) ExtensionService/AppDelegate+Menu.swift:365
- Duplicated block (5 lines × 22) Tool/Sources/GitHubCopilotService/LanguageServer/GitHubCopilotRequest.swift:367
- Unstable project ChatService
- Unstable project ConversationTab
- Unstable project KeyBindingManager
- Unstable project SuggestionService
- Unstable project SuggestionWidget
- Unstable project TelemetryService
- Unstable project XcodeThemeController
- No structured logging
- Duplicated block (20 lines × 2 locations) Server/src/diffView/js/ui-controller.ts:84
- Duplicated block with local edits (17 matched lines × 2 locations) Server/src/diffView/js/api.ts:82
- Duplicated block (9 lines × 2 locations) Server/src/terminal/terminalAddon.ts:93
- Duplicated block with local edits (8 matched lines × 2 locations) Server/src/diffView/js/monaco-diff-editor.ts:61
- Duplicated block (7 lines × 2 locations) Server/src/terminal/terminalAddon.ts:132
- Complex function handleSingleLine (cyclomatic 12, cognitive 18) Server/src/terminal/terminalAddon.ts:125
- No test or lint script
- Unused dependency '@github/copilot-language-server'
- Unused dependency '@github/copilot-language-server-darwin-arm64'
- Unused dependency '@github/copilot-language-server-darwin-x64'
Minor — 38 finding(s)
- Silent fallback default in catch Core/Sources/ChatService/ChatService.swift:1359
- Silent fallback default in catch Core/Sources/HostApp/ToolsSettings/MCPRegistry/MCPServerDetailSheet.swift:399
- Silent fallback default in catch Core/Sources/HostApp/ToolsSettings/MCPRegistry/ServerInstallationOptionView.swift:168
- Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:18
- Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:22
- Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:30
- Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:34
- Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:38
- Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:47
- Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:52
- Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:56
- Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:119
- Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:127
- Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:143
- Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:151
- Silent fallback default in catch Tool/Sources/AXExtension/AXUIElement.swift:159
- No direct assertions: test_should_accept Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:10
- No direct assertions: test_should_not_accept_without_suggestion Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:29
- No direct assertions: test_should_not_accept_without_filespace Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:48
- No direct assertions: test_should_not_accept_without_editor_focused Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:66
- No direct assertions: test_should_not_accept_without_active_xcode Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:85
- No direct assertions: test_should_not_accept_without_active_document Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:104
- No direct assertions: test_should_not_accept_with_shift Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:123
- No direct assertions: test_should_not_accept_with_command Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:142
- No direct assertions: test_should_not_accept_with_control Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:161
- No direct assertions: test_should_not_accept_with_help Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:180
- Duplicated predicate Server/src/diffView/js/api.ts:109
- Duplicated predicate Core/Sources/ConversationTab/TerminalViews/RunInTerminalToolView.swift:164
- Duplicated predicate Core/Sources/GitHubCopilotViewModel/GitHubCopilotViewModel.swift:381
- Duplicated predicate Core/Sources/HostApp/GeneralSettings/CopilotConnectionView.swift:41
- REDACTED
- REDACTED
- Test project verifies nothing: KeyBindingManagerTests Core/Tests/KeyBindingManagerTests/TabToAcceptSuggestionTests.swift:10
- No ADRs found
- Projects may be oversized for their cohesion
- No ADRs
- No architecture diagram/doc
- No src/ separation
Minor — 24 finding(s)
- Outdated: combine-schedulers
- Outdated: jsonrpc
- Outdated: languageserverprotocol
- Outdated: networkimage
- Outdated: queue
- Outdated: sparkle
- Outdated: sqlite.swift
- Outdated: swift-argument-parser
- Outdated: swift-async-algorithms
- Outdated: swift-case-paths
- Outdated: swift-clocks
- Outdated: swift-collections
- Outdated: swift-composable-architecture
- Outdated: swift-concurrency-extras
- Outdated: swift-custom-dump
- Outdated: swift-dependencies
- Outdated: swift-identified-collections
- Outdated: swift-markdown-ui
- Outdated: swift-parsing
- Outdated: swift-perception
- Outdated: swiftsoup
- Outdated: swiftui-navigation
- Outdated: tree-sitter
- Outdated: xctest-dynamic-overlay
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ef7713a169fb48fba168689130442705/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ef7713a169fb48fba168689130442705/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 10 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 60 file(s) — `CommunicationBridge/ServiceDelegate.swift`, `Core/Sources/ChatService/ChatService.swift`, `Core/Sources/ChatService/CodeReview/CodeReviewProvider.swift`, `Core/Sources/ChatService/ToolCalls/AutoApproval/ToolAutoApprovalParsingHelpers.swift`, `Core/Sources/ChatService/ToolCalls/InsertEditIntoFileTool.swift`, … (+55 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |