Executive summary
MarkEdit-app/MarkEdit falls short of our standard for production because we found no automated security scanning of the code, its secrets or its dependencies. It scores 65 out of 100 and is rated Adequate, and three of its six critical findings are security problems in the build pipeline and in its code.
Production Readiness, at 54, is the weakest lens and counts most in the score. The best first step for the work it takes is improving the documentation, worth about 5 points. Adding automated security scanning would lift Production Readiness itself, worth about 7 points. Raising Production Readiness to 70 would lift the score to about 72.
Two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One weakness in the code could be used by an attacker. Pinning each tool to an exact version and fixing the weaknesses the scanner points to would close both risks. The loop of files that import each other needs breaking.
The product code is 36,490 lines, about €57,000 to rebuild.
If Production Readiness rose from 54 to 70, the lowest score rated Strong, the score would rise from 65 to about 72.
New since the last survey: 22 findings
- Cyclomatic Complexity · commands.insertNewlineContinueMarkupCommand.<returned closure> (cyclomatic 44) CoreEditor/src/@vendor/lang-markdown/commands.ts
- Cognitive Complexity · commands.insertNewlineContinueMarkupCommand.<returned closure> (cognitive 51) CoreEditor/src/@vendor/lang-markdown/commands.ts
- Cognitive Complexity · AppDelegate.quickSearch (cognitive 19) MarkEditMac/Sources/Main/Application/AppDelegate+QuickSearch.swift
- Cognitive Complexity · EditorDocument.presentedItemDidChange (cognitive 17) MarkEditMac/Sources/Editor/Models/EditorDocument.swift
- God Classes · FileTooLong: QuickSearchUI/QuickSearchController.swift MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchController.swift
- Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) MarkEditMac/Modules/Sources/ExtensionCore/ExtensionRegistry.swift
- Code Duplication · Edited copy of a member (15 corresponding lines) MarkEditKit/Sources/Bridge/Native/Modules/EditorModuleAPI.swift
- Code Duplication · Edited copy of a member (8 corresponding lines) MarkEditMac/Sources/Main/AppWritingTools.swift
- Code Duplication · Edited copy of a member (11 corresponding lines) MarkEditMac/Sources/Extension/Core/ExtensionInstaller.swift
- Code Duplication · Edited copy of a member (10 corresponding lines) MarkEditMac/Sources/Editor/Controllers/EditorViewController+Menu.swift
- Code Duplication · Edited copy of a member (6 corresponding lines) MarkEditMac/Modules/Sources/AppKitExtensions/UI/NSColor+Extension.swift
- Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) MarkEditKit/Sources/Bridge/Native/Modules/EditorModuleSecretStorage.swift
- Cohesion (LCOM4) · Low cohesion: NSMenuItem (LCOM4 7) MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchMenuActions.swift
- Cohesion (LCOM4) · Low cohesion: NSApplication (LCOM4 4) MarkEditMac/Sources/Extras/NSApplication+Extras.swift
- Test Quality · Skipped test: testInvalidArgumentsDoNotInvokeNativeMethods MarkEditKit/Tests/NativeBridgeParametersTests.swift
- Test Quality · No assertions: testDelayedAppKitInternalFunctions MarkEditMac/Modules/Tests/RuntimeTests.swift
- Test Reliability · Flaky test: CoreEditor/test/task.test.ts::Task marker decoration decorates mixed task lists with the correct state per line
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Code Duplication · Duplicated block (6 lines × 2 locations) CoreEditor/src/styling/nodes/indent.ts
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 28, cognitive 49) CoreEditor/src/modules/input/index.ts
Fixed since the last survey: 16 findings
- Cyclomatic Complexity · commands.insertNewlineContinueMarkupCommand (cyclomatic 44) CoreEditor/src/@vendor/lang-markdown/commands.ts
- Cyclomatic Complexity · QuickSearchController.present (cyclomatic 16) MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchController.swift
- Cognitive Complexity · commands.insertNewlineContinueMarkupCommand (cognitive 51) CoreEditor/src/@vendor/lang-markdown/commands.ts
- Cognitive Complexity · QuickSearchController.present (cognitive 16) MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchController.swift
- Code Duplication · Duplicated block (20 lines × 2) MarkEditMac/Modules/Sources/FontPicker/FontPickerConfiguration.swift
- Code Duplication · Duplicated block (5 lines × 2) MarkEditMac/Modules/Sources/DiffKit/Diff.swift
- Coupling · Off the main sequence: UpdaterCore
- Cohesion (LCOM4) · Low cohesion: NSMenuItem (LCOM4 7) MarkEditMac/Sources/Editor/Views/EditorWebView.swift
- Churn × Complexity Hotspots · Hotspot: CoreEditor/src/@vendor/lang-markdown/commands.ts CoreEditor/src/@vendor/lang-markdown/commands.ts
- Churn × Complexity Hotspots · Hotspot: CoreEditor/src/modules/commands/formatContent.ts CoreEditor/src/modules/commands/formatContent.ts
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Change Coupling · Boundary-crossing change coupling: WebKit+Extension.swift ↔ WKWebViewConfiguration+Extension.swift MarkEditCore/Sources/Extensions/WebKit+Extension.swift
- Code Duplication · Duplicated block with local edits (17 matched lines × 2 locations) CoreEditor/src/bridge/web/config.ts
- Code Duplication · Duplicated block with local edits (8 matched lines × 2 locations) CoreEditor/src/bridge/web/core.ts
- Code Duplication · Duplicated block with local edits (6 matched lines × 2 locations) CoreEditor/src/bridge/web/search.ts
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 28, cognitive 51) CoreEditor/src/modules/input/index.ts
Rebuild cost: about €57,000 · Estimate
| Cost to rebuild | €19,000 to €95,000, for 315 to 1,000 hours of work, about 0.4 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 65. 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: 36,490 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 CoreEditor.src.@types.WebFontFace | 2 CoreEditor.src.api | 3 CoreEditor.src.core | 4 CoreEditor.src.modules.search.options | 5 CoreEditor.src.modules.selection.types | 6 CoreEditor.src.styling.types | 7 CoreEditor.src.styling.views | 8 CoreEditor.src.config | 9 CoreEditor.src.modules.search | 10 CoreEditor.src.modules.selection | 11 MarkEditKit~Extensions | 12 MarkEditMac~Modules~FontPicker | 13 MarkEditMac~Modules~QuickSearchCore | 14 UpdateInstaller~UpdaterCore | 15 CoreEditor.src | 16 CoreEditor.src.styling | 17 repository | 18 MarkEditMac~Modules~ExtensionCore | 19 MarkEditMac~Modules~TextBundle | 20 MarkEditMac~Scripting | 21 MarkEditMac~Modules~TextCompletion | 22 MarkEditMac~Modules~AppKitExtensions | 23 MarkEditMac~Main | 24 MarkEditMac~Modules~SharedUI | 25 MarkEditMac~Modules~Statistics | 26 MarkEditMac~Extras | 27 MarkEditMac~Modules~FileVersion | 28 MarkEditMac~Panels | 29 MarkEditMac~Extension | 30 MarkEditMac~Editor | 31 MarkEditMac~Modules~QuickSearchUI | 32 MarkEditKit~Bridge | 33 MarkEditKit | 34 MarkEditCore~Extensions | 35 MarkEditCore | 36 MarkEditMac~Modules~DiffKit | 37 MarkEditMac~Modules~SettingsUI | 38 MarkEditMac~Settings | 39 MarkEditMac~Shortcuts | 40 MarkEditMac~Updater |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 CoreEditor.src.@types.WebFontFace | ||||||||||||||||||||||||||||||||||||||||
| 2 CoreEditor.src.api | ||||||||||||||||||||||||||||||||||||||||
| 3 CoreEditor.src.core | ||||||||||||||||||||||||||||||||||||||||
| 4 CoreEditor.src.modules.search.options | ||||||||||||||||||||||||||||||||||||||||
| 5 CoreEditor.src.modules.selection.types | ||||||||||||||||||||||||||||||||||||||||
| 6 CoreEditor.src.styling.types | ||||||||||||||||||||||||||||||||||||||||
| 7 CoreEditor.src.styling.views | ||||||||||||||||||||||||||||||||||||||||
| 8 CoreEditor.src.config | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 CoreEditor.src.modules.search | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 CoreEditor.src.modules.selection | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 MarkEditKit~Extensions | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 MarkEditMac~Modules~FontPicker | 4 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 13 MarkEditMac~Modules~QuickSearchCore | 15 | |||||||||||||||||||||||||||||||||||||||
| 14 UpdateInstaller~UpdaterCore | 8 | |||||||||||||||||||||||||||||||||||||||
| 15 CoreEditor.src | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 CoreEditor.src.styling | 1 | 5 | 2 | |||||||||||||||||||||||||||||||||||||
| 17 repository | 2 | 6 | 1 | 1 | 2 | 11 | ||||||||||||||||||||||||||||||||||
| 18 MarkEditMac~Modules~ExtensionCore | 1 | 3 | 16 | |||||||||||||||||||||||||||||||||||||
| 19 MarkEditMac~Modules~TextBundle | 1 | 1 | 6 | |||||||||||||||||||||||||||||||||||||
| 20 MarkEditMac~Scripting | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 MarkEditMac~Modules~TextCompletion | 1 | 2 | 3 | 2 | 4 | |||||||||||||||||||||||||||||||||||
| 22 MarkEditMac~Modules~AppKitExtensions | 2 | 2 | 1 | 1 | 2 | 2 | 1 | 17 | ||||||||||||||||||||||||||||||||
| 23 MarkEditMac~Main | 2 | 1 | 1 | 1 | 2 | 6 | 5 | 1 | 2 | 3 | 2 | 6 | 44 | 9 | ||||||||||||||||||||||||||
| 24 MarkEditMac~Modules~SharedUI | 10 | 6 | 12 | 4 | 14 | |||||||||||||||||||||||||||||||||||
| 25 MarkEditMac~Modules~Statistics | 2 | 1 | 2 | 1 | 9 | |||||||||||||||||||||||||||||||||||
| 26 MarkEditMac~Extras | 1 | 2 | 2 | 2 | 2 | 1 | 4 | |||||||||||||||||||||||||||||||||
| 27 MarkEditMac~Modules~FileVersion | 2 | 4 | 2 | 3 | ||||||||||||||||||||||||||||||||||||
| 28 MarkEditMac~Panels | 4 | 4 | 2 | 3 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 29 MarkEditMac~Extension | 3 | 3 | 9 | 7 | 1 | 2 | 1 | 3 | 15 | |||||||||||||||||||||||||||||||
| 30 MarkEditMac~Editor | 2 | 1 | 1 | 2 | 1 | 19 | 6 | 5 | 1 | 4 | 1 | 3 | 2 | 6 | 20 | 4 | 16 | 5 | ||||||||||||||||||||||
| 31 MarkEditMac~Modules~QuickSearchUI | 1 | 9 | 1 | 4 | 1 | 15 | 2 | 4 | 1 | 13 | ||||||||||||||||||||||||||||||
| 32 MarkEditKit~Bridge | 2 | 2 | 1 | 1 | 12 | 78 | 12 | |||||||||||||||||||||||||||||||||
| 33 MarkEditKit | 1 | 3 | 1 | 6 | 1 | |||||||||||||||||||||||||||||||||||
| 34 MarkEditCore~Extensions | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 35 MarkEditCore | 1 | 2 | 22 | |||||||||||||||||||||||||||||||||||||
| 36 MarkEditMac~Modules~DiffKit | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 37 MarkEditMac~Modules~SettingsUI | 4 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 MarkEditMac~Settings | 6 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 MarkEditMac~Shortcuts | 1 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 40 MarkEditMac~Updater | 1 | 2 | 6 |
8→1 CoreEditor.src.config uses CoreEditor.src.@types.WebFontFace✕
- Connections
- 1 pair of types, where a type in CoreEditor.src.config uses a type in CoreEditor.src.@types.WebFontFace.
- The types involved
CoreEditor.src.config.Config→CoreEditor.src.@types.WebFontFace.WebFontFace
- Direction
- CoreEditor.src.config uses CoreEditor.src.@types.WebFontFace, so a change to CoreEditor.src.@types.WebFontFace can break CoreEditor.src.config, while a change to CoreEditor.src.config can't break CoreEditor.src.@types.WebFontFace.
- Position
- Below the diagonal: CoreEditor.src.config uses a module listed above it, which is the healthy direction.
9→4 CoreEditor.src.modules.search uses CoreEditor.src.modules.search.options✕
- Connections
- 1 pair of types, where a type in CoreEditor.src.modules.search uses a type in CoreEditor.src.modules.search.options.
- The types involved
CoreEditor.src.modules.search.previewSearch→CoreEditor.src.modules.search.options.SearchOptions
- Direction
- CoreEditor.src.modules.search uses CoreEditor.src.modules.search.options, so a change to CoreEditor.src.modules.search.options can break CoreEditor.src.modules.search, while a change to CoreEditor.src.modules.search can't break CoreEditor.src.modules.search.options.
- Position
- Below the diagonal: CoreEditor.src.modules.search uses a module listed above it, which is the healthy direction.
9→5 CoreEditor.src.modules.search uses CoreEditor.src.modules.selection.types✕
- Connections
- 1 pair of types, where a type in CoreEditor.src.modules.search uses a type in CoreEditor.src.modules.selection.types.
- The types involved
CoreEditor.src.modules.search.rangesFromQuery→CoreEditor.src.modules.selection.types.SelectionRange
- Direction
- CoreEditor.src.modules.search uses CoreEditor.src.modules.selection.types, so a change to CoreEditor.src.modules.selection.types can break CoreEditor.src.modules.search, while a change to CoreEditor.src.modules.search can't break CoreEditor.src.modules.selection.types.
- Position
- Below the diagonal: CoreEditor.src.modules.search uses a module listed above it, which is the healthy direction.
10→5 CoreEditor.src.modules.selection uses CoreEditor.src.modules.selection.types✕
- Connections
- 1 pair of types, where a type in CoreEditor.src.modules.selection uses a type in CoreEditor.src.modules.selection.types.
- The types involved
CoreEditor.src.modules.selection.reverseRange→CoreEditor.src.modules.selection.types.SelectionRange
- Direction
- CoreEditor.src.modules.selection uses CoreEditor.src.modules.selection.types, so a change to CoreEditor.src.modules.selection.types can break CoreEditor.src.modules.selection, while a change to CoreEditor.src.modules.selection can't break CoreEditor.src.modules.selection.types.
- Position
- Below the diagonal: CoreEditor.src.modules.selection uses a module listed above it, which is the healthy direction.
11→34 MarkEditKit~Extensions uses MarkEditCore~Extensions part of a loop✕
- Connections
- 1 pair of types, where a type in MarkEditKit~Extensions uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditKit~Extensions.NSFileVersion→MarkEditCore~Extensions.URL
- Direction
- MarkEditKit~Extensions uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditKit~Extensions, while a change to MarkEditKit~Extensions can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so 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→22 MarkEditMac~Modules~FontPicker uses MarkEditMac~Modules~AppKitExtensions part of a loop✕
- Connections
- 4 pairs of types, where a type in MarkEditMac~Modules~FontPicker uses a type in MarkEditMac~Modules~AppKitExtensions.
- The types involved
MarkEditMac~Modules~FontPicker.FontPicker→MarkEditMac~Modules~AppKitExtensions.NSFontMarkEditMac~Modules~FontPicker.FontStyle→MarkEditMac~Modules~AppKitExtensions.NSFontMarkEditMac~Modules~FontPicker.IdentifiableView→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Modules~FontPicker.IdentifiableWrapper→MarkEditMac~Modules~AppKitExtensions.NSView
- Direction
- MarkEditMac~Modules~FontPicker uses MarkEditMac~Modules~AppKitExtensions, so a change to MarkEditMac~Modules~AppKitExtensions can break MarkEditMac~Modules~FontPicker, while a change to MarkEditMac~Modules~FontPicker can't break MarkEditMac~Modules~AppKitExtensions.
- Position
- Above the diagonal, so 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→32 MarkEditMac~Modules~FontPicker uses MarkEditKit~Bridge part of a loop✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Modules~FontPicker uses a type in MarkEditKit~Bridge.
- The types involved
MarkEditMac~Modules~FontPicker.IdentifiableWrapper→MarkEditKit~Bridge.Context
- Direction
- MarkEditMac~Modules~FontPicker uses MarkEditKit~Bridge, so a change to MarkEditKit~Bridge can break MarkEditMac~Modules~FontPicker, while a change to MarkEditMac~Modules~FontPicker can't break MarkEditKit~Bridge.
- Position
- Above the diagonal, so 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→34 MarkEditMac~Modules~FontPicker uses MarkEditCore~Extensions part of a loop✕
- Connections
- 4 pairs of types, where a type in MarkEditMac~Modules~FontPicker uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditMac~Modules~FontPicker.FontPicker→MarkEditCore~Extensions.StringMarkEditMac~Modules~FontPicker.FontPickerConfiguration→MarkEditCore~Extensions.StringMarkEditMac~Modules~FontPicker.FontStyle→MarkEditCore~Extensions.StringMarkEditMac~Modules~FontPicker.View→MarkEditCore~Extensions.String
- Direction
- MarkEditMac~Modules~FontPicker uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Modules~FontPicker, while a change to MarkEditMac~Modules~FontPicker can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→35 MarkEditMac~Modules~FontPicker uses MarkEditCore part of a loop✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Modules~FontPicker uses a type in MarkEditCore.
- The types involved
MarkEditMac~Modules~FontPicker.FontStyle→MarkEditCore.WebFontFace
- Direction
- MarkEditMac~Modules~FontPicker uses MarkEditCore, so a change to MarkEditCore can break MarkEditMac~Modules~FontPicker, while a change to MarkEditMac~Modules~FontPicker can't break MarkEditCore.
- Position
- Above the diagonal, so 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→34 MarkEditMac~Modules~QuickSearchCore uses MarkEditCore~Extensions part of a loop✕
- Connections
- 15 pairs of types, where a type in MarkEditMac~Modules~QuickSearchCore uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditMac~Modules~QuickSearchCore.Action→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchCore.Batch→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchCore.Batch→MarkEditCore~Extensions.URLMarkEditMac~Modules~QuickSearchCore.ContentSearchResult→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchCore.FileSearchResult→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchCore.FileSearchResult→MarkEditCore~Extensions.URLMarkEditMac~Modules~QuickSearchCore.FuzzyMatcher→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchCore.HeadingSearchResult→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchCore.MenuActionSearchResult→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchCore.QuickSearchDocumentSnapshot→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchCore.QuickSearchHeading→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchCore.QuickSearchLocations→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchCore.QuickSearchLocations→MarkEditCore~Extensions.URLMarkEditMac~Modules~QuickSearchCore.QuickSearchResult→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchCore.QuickSearchResult→MarkEditCore~Extensions.URL
- Direction
- MarkEditMac~Modules~QuickSearchCore uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Modules~QuickSearchCore, while a change to MarkEditMac~Modules~QuickSearchCore can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so 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→34 UpdateInstaller~UpdaterCore uses MarkEditCore~Extensions part of a loop✕
- Connections
- 8 pairs of types, where a type in UpdateInstaller~UpdaterCore uses a type in MarkEditCore~Extensions.
- The types involved
UpdateInstaller~UpdaterCore.BundleVerifier→MarkEditCore~Extensions.StringUpdateInstaller~UpdaterCore.Failure→MarkEditCore~Extensions.StringUpdateInstaller~UpdaterCore.HostBundle→MarkEditCore~Extensions.StringUpdateInstaller~UpdaterCore.HostBundle→MarkEditCore~Extensions.URLUpdateInstaller~UpdaterCore.InstallerArguments→MarkEditCore~Extensions.StringUpdateInstaller~UpdaterCore.StagingLocation→MarkEditCore~Extensions.StringUpdateInstaller~UpdaterCore.StagingLocation→MarkEditCore~Extensions.URLUpdateInstaller~UpdaterCore.[String: Any]→MarkEditCore~Extensions.String
- Direction
- UpdateInstaller~UpdaterCore uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break UpdateInstaller~UpdaterCore, while a change to UpdateInstaller~UpdaterCore can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so 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→3 CoreEditor.src uses CoreEditor.src.core✕
- Connections
- 2 pairs of types, where a type in CoreEditor.src uses a type in CoreEditor.src.core.
- The types involved
CoreEditor.src.core→CoreEditor.src.core.ReadableContentPairCoreEditor.src.core→CoreEditor.src.core.ReplaceGranularity
- Direction
- CoreEditor.src uses CoreEditor.src.core, so a change to CoreEditor.src.core can break CoreEditor.src, while a change to CoreEditor.src can't break CoreEditor.src.core.
- Position
- Below the diagonal: CoreEditor.src uses a module listed above it, which is the healthy direction.
15→8 CoreEditor.src uses CoreEditor.src.config✕
- Connections
- 1 pair of types, where a type in CoreEditor.src uses a type in CoreEditor.src.config.
- The types involved
CoreEditor.src.index→CoreEditor.src.config.Config
- Direction
- CoreEditor.src uses CoreEditor.src.config, so a change to CoreEditor.src.config can break CoreEditor.src, while a change to CoreEditor.src can't break CoreEditor.src.config.
- Position
- Below the diagonal: CoreEditor.src uses a module listed above it, which is the healthy direction.
16→1 CoreEditor.src.styling uses CoreEditor.src.@types.WebFontFace✕
- Connections
- 1 pair of types, where a type in CoreEditor.src.styling uses a type in CoreEditor.src.@types.WebFontFace.
- The types involved
CoreEditor.src.styling.config→CoreEditor.src.@types.WebFontFace.WebFontFace
- Direction
- CoreEditor.src.styling uses CoreEditor.src.@types.WebFontFace, so a change to CoreEditor.src.@types.WebFontFace can break CoreEditor.src.styling, while a change to CoreEditor.src.styling can't break CoreEditor.src.@types.WebFontFace.
- Position
- Below the diagonal: CoreEditor.src.styling uses a module listed above it, which is the healthy direction.
16→6 CoreEditor.src.styling uses CoreEditor.src.styling.types✕
- Connections
- 5 pairs of types, where a type in CoreEditor.src.styling uses a type in CoreEditor.src.styling.types.
- The types involved
CoreEditor.src.styling.builder→CoreEditor.src.styling.types.ColorSchemeCoreEditor.src.styling.builder→CoreEditor.src.styling.types.EditorColorsCoreEditor.src.styling.config→CoreEditor.src.styling.types.EditorColorsCoreEditor.src.styling.config→CoreEditor.src.styling.types.EditorThemeCoreEditor.src.styling.index→CoreEditor.src.styling.types.EditorTheme
- Direction
- CoreEditor.src.styling uses CoreEditor.src.styling.types, so a change to CoreEditor.src.styling.types can break CoreEditor.src.styling, while a change to CoreEditor.src.styling can't break CoreEditor.src.styling.types.
- Position
- Below the diagonal: CoreEditor.src.styling uses a module listed above it, which is the healthy direction.
16→8 CoreEditor.src.styling uses CoreEditor.src.config✕
- Connections
- 2 pairs of types, where a type in CoreEditor.src.styling uses a type in CoreEditor.src.config.
- The types involved
CoreEditor.src.styling.config→CoreEditor.src.config.ConfigCoreEditor.src.styling.config→CoreEditor.src.config.InvisiblesBehavior
- Direction
- CoreEditor.src.styling uses CoreEditor.src.config, so a change to CoreEditor.src.config can break CoreEditor.src.styling, while a change to CoreEditor.src.styling can't break CoreEditor.src.config.
- Position
- Below the diagonal: CoreEditor.src.styling uses a module listed above it, which is the healthy direction.
17→11 repository uses MarkEditKit~Extensions✕
- Connections
- 2 pairs of types, where a type in repository uses a type in MarkEditKit~Extensions.
- The types involved
repository.ServiceDelegate→MarkEditKit~Extensions.NSObjectrepository.UpdateService→MarkEditKit~Extensions.NSObject
- Direction
- repository uses MarkEditKit~Extensions, so a change to MarkEditKit~Extensions can break repository, while a change to repository can't break MarkEditKit~Extensions.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
17→22 repository uses MarkEditMac~Modules~AppKitExtensions part of a loop✕
- Connections
- 6 pairs of types, where a type in repository uses a type in MarkEditMac~Modules~AppKitExtensions.
- The types involved
repository.QuickLookOpenGestureRecognizer→MarkEditMac~Modules~AppKitExtensions.NSEventrepository.QuickLookViewController→MarkEditMac~Modules~AppKitExtensions.NSEventrepository.QuickLookViewController→MarkEditMac~Modules~AppKitExtensions.NSViewrepository.QuickLookViewController→MarkEditMac~Modules~AppKitExtensions.NSViewControllerrepository.QuickLookViewController→MarkEditMac~Modules~AppKitExtensions.NSWindowrepository.QuickLookWebView→MarkEditMac~Modules~AppKitExtensions.NSEvent
- Direction
- repository uses MarkEditMac~Modules~AppKitExtensions, so a change to MarkEditMac~Modules~AppKitExtensions can break repository, while a change to repository can't break MarkEditMac~Modules~AppKitExtensions.
- Position
- Above the diagonal, so 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→26 repository uses MarkEditMac~Extras part of a loop✕
- Connections
- 1 pair of types, where a type in repository uses a type in MarkEditMac~Extras.
- The types involved
repository.QuickLookWebView→MarkEditMac~Extras.NSMenu
- Direction
- repository uses MarkEditMac~Extras, so a change to MarkEditMac~Extras can break repository, while a change to repository can't break MarkEditMac~Extras.
- Position
- Above the diagonal, so 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→29 repository uses MarkEditMac~Extension part of a loop✕
- Connections
- 1 pair of types, where a type in repository uses a type in MarkEditMac~Extension.
- The types involved
repository.QuickLookViewController→MarkEditMac~Extension.Name
- Direction
- repository uses MarkEditMac~Extension, so a change to MarkEditMac~Extension can break repository, while a change to repository can't break MarkEditMac~Extension.
- Position
- Above the diagonal, so 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→31 repository uses MarkEditMac~Modules~QuickSearchUI part of a loop✕
- Connections
- 2 pairs of types, where a type in repository uses a type in MarkEditMac~Modules~QuickSearchUI.
- The types involved
repository.QuickLookWebView→MarkEditMac~Modules~QuickSearchUI.CGRectrepository.QuickLookWebView→MarkEditMac~Modules~QuickSearchUI.NSMenuItem
- Direction
- repository uses MarkEditMac~Modules~QuickSearchUI, so a change to MarkEditMac~Modules~QuickSearchUI can break repository, while a change to repository can't break MarkEditMac~Modules~QuickSearchUI.
- Position
- Above the diagonal, so 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→34 repository uses MarkEditCore~Extensions part of a loop✕
- Connections
- 11 pairs of types, where a type in repository uses a type in MarkEditCore~Extensions.
- The types involved
repository.QuickLookViewController→MarkEditCore~Extensions.Stringrepository.QuickLookViewController→MarkEditCore~Extensions.URLrepository.QuickLookViewController→MarkEditCore~Extensions.WKWebViewrepository.QuickLookWebView→MarkEditCore~Extensions.WKWebViewrepository.QuickLookWindowSize→MarkEditCore~Extensions.Stringrepository.ServiceDelegate→MarkEditCore~Extensions.Stringrepository.UpdateInstalling→MarkEditCore~Extensions.Stringrepository.UpdateRunner→MarkEditCore~Extensions.Stringrepository.UpdateService→MarkEditCore~Extensions.Stringrepository.UpdateService→MarkEditCore~Extensions.URLrepository.WKWebViewConfiguration→MarkEditCore~Extensions.String
- Direction
- repository uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break repository, while a change to repository can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→17 MarkEditMac~Modules~ExtensionCore uses repository✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Modules~ExtensionCore uses a type in repository.
- The types involved
MarkEditMac~Modules~ExtensionCore.Failure→repository.Error
- Direction
- MarkEditMac~Modules~ExtensionCore uses repository, so a change to repository can break MarkEditMac~Modules~ExtensionCore, while a change to MarkEditMac~Modules~ExtensionCore can't break repository.
- Position
- Below the diagonal: MarkEditMac~Modules~ExtensionCore uses a module listed above it, which is the healthy direction.
18→33 MarkEditMac~Modules~ExtensionCore uses MarkEditKit part of a loop✕
- Connections
- 3 pairs of types, where a type in MarkEditMac~Modules~ExtensionCore uses a type in MarkEditKit.
- The types involved
MarkEditMac~Modules~ExtensionCore.ExtensionConfig→MarkEditKit.DataMarkEditMac~Modules~ExtensionCore.ExtensionDownloader→MarkEditKit.DataMarkEditMac~Modules~ExtensionCore.ExtensionRegistry→MarkEditKit.Data
- Direction
- MarkEditMac~Modules~ExtensionCore uses MarkEditKit, so a change to MarkEditKit can break MarkEditMac~Modules~ExtensionCore, while a change to MarkEditMac~Modules~ExtensionCore can't break MarkEditKit.
- Position
- Above the diagonal, so 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→34 MarkEditMac~Modules~ExtensionCore uses MarkEditCore~Extensions part of a loop✕
- Connections
- 16 pairs of types, where a type in MarkEditMac~Modules~ExtensionCore uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditMac~Modules~ExtensionCore.Category→MarkEditCore~Extensions.StringMarkEditMac~Modules~ExtensionCore.CodingKeys→MarkEditCore~Extensions.StringMarkEditMac~Modules~ExtensionCore.ColorScheme→MarkEditCore~Extensions.StringMarkEditMac~Modules~ExtensionCore.Definition→MarkEditCore~Extensions.StringMarkEditMac~Modules~ExtensionCore.ExtensionConfig→MarkEditCore~Extensions.StringMarkEditMac~Modules~ExtensionCore.ExtensionConfig→MarkEditCore~Extensions.URLMarkEditMac~Modules~ExtensionCore.ExtensionDownloader→MarkEditCore~Extensions.StringMarkEditMac~Modules~ExtensionCore.ExtensionDownloader→MarkEditCore~Extensions.URLMarkEditMac~Modules~ExtensionCore.ExtensionEntry→MarkEditCore~Extensions.StringMarkEditMac~Modules~ExtensionCore.ExtensionEnvironment→MarkEditCore~Extensions.URLMarkEditMac~Modules~ExtensionCore.ExtensionRelease→MarkEditCore~Extensions.StringMarkEditMac~Modules~ExtensionCore.ExtensionRelease→MarkEditCore~Extensions.URLMarkEditMac~Modules~ExtensionCore.ExtensionUpdate→MarkEditCore~Extensions.StringMarkEditMac~Modules~ExtensionCore.Installed→MarkEditCore~Extensions.StringMarkEditMac~Modules~ExtensionCore.Installed→MarkEditCore~Extensions.URLMarkEditMac~Modules~ExtensionCore.UpdateBehavior→MarkEditCore~Extensions.String
- Direction
- MarkEditMac~Modules~ExtensionCore uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Modules~ExtensionCore, while a change to MarkEditMac~Modules~ExtensionCore can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so 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→17 MarkEditMac~Modules~TextBundle uses repository✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Modules~TextBundle uses a type in repository.
- The types involved
MarkEditMac~Modules~TextBundle.TextBundleError→repository.Error
- Direction
- MarkEditMac~Modules~TextBundle uses repository, so a change to repository can break MarkEditMac~Modules~TextBundle, while a change to MarkEditMac~Modules~TextBundle can't break repository.
- Position
- Below the diagonal: MarkEditMac~Modules~TextBundle uses a module listed above it, which is the healthy direction.
19→33 MarkEditMac~Modules~TextBundle uses MarkEditKit part of a loop✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Modules~TextBundle uses a type in MarkEditKit.
- The types involved
MarkEditMac~Modules~TextBundle.TextBundleWrapper→MarkEditKit.Data
- Direction
- MarkEditMac~Modules~TextBundle uses MarkEditKit, so a change to MarkEditKit can break MarkEditMac~Modules~TextBundle, while a change to MarkEditMac~Modules~TextBundle can't break MarkEditKit.
- Position
- Above the diagonal, so 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→34 MarkEditMac~Modules~TextBundle uses MarkEditCore~Extensions part of a loop✕
- Connections
- 6 pairs of types, where a type in MarkEditMac~Modules~TextBundle uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditMac~Modules~TextBundle.FileNames→MarkEditCore~Extensions.StringMarkEditMac~Modules~TextBundle.FileWrapper→MarkEditCore~Extensions.StringMarkEditMac~Modules~TextBundle.TextBundleAssets→MarkEditCore~Extensions.StringMarkEditMac~Modules~TextBundle.TextBundleAssets→MarkEditCore~Extensions.URLMarkEditMac~Modules~TextBundle.TextBundleWrapper→MarkEditCore~Extensions.StringMarkEditMac~Modules~TextBundle.TextBundleWrapper→MarkEditCore~Extensions.URL
- Direction
- MarkEditMac~Modules~TextBundle uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Modules~TextBundle, while a change to MarkEditMac~Modules~TextBundle can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so 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→14 MarkEditMac~Scripting uses UpdateInstaller~UpdaterCore✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Scripting uses a type in UpdateInstaller~UpdaterCore.
- The types involved
MarkEditMac~Scripting.NSAppleEventDescriptor→UpdateInstaller~UpdaterCore.[String: Any]
- Direction
- MarkEditMac~Scripting uses UpdateInstaller~UpdaterCore, so a change to UpdateInstaller~UpdaterCore can break MarkEditMac~Scripting, while a change to MarkEditMac~Scripting can't break UpdateInstaller~UpdaterCore.
- Position
- Below the diagonal: MarkEditMac~Scripting uses a module listed above it, which is the healthy direction.
20→17 MarkEditMac~Scripting uses repository✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Scripting uses a type in repository.
- The types involved
MarkEditMac~Scripting.ScriptingError→repository.Error
- Direction
- MarkEditMac~Scripting uses repository, so a change to repository can break MarkEditMac~Scripting, while a change to MarkEditMac~Scripting can't break repository.
- Position
- Below the diagonal: MarkEditMac~Scripting uses a module listed above it, which is the healthy direction.
20→22 MarkEditMac~Scripting uses MarkEditMac~Modules~AppKitExtensions part of a loop✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Scripting uses a type in MarkEditMac~Modules~AppKitExtensions.
- The types involved
MarkEditMac~Scripting.NSColor→MarkEditMac~Modules~AppKitExtensions.NSAppearance
- Direction
- MarkEditMac~Scripting uses MarkEditMac~Modules~AppKitExtensions, so a change to MarkEditMac~Modules~AppKitExtensions can break MarkEditMac~Scripting, while a change to MarkEditMac~Scripting can't break MarkEditMac~Modules~AppKitExtensions.
- Position
- Above the diagonal, so 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→34 MarkEditMac~Scripting uses MarkEditCore~Extensions part of a loop✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Scripting uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditMac~Scripting.ScriptingError→MarkEditCore~Extensions.String
- Direction
- MarkEditMac~Scripting uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Scripting, while a change to MarkEditMac~Scripting can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so 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→12 MarkEditMac~Modules~TextCompletion uses MarkEditMac~Modules~FontPicker✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Modules~TextCompletion uses a type in MarkEditMac~Modules~FontPicker.
- The types involved
MarkEditMac~Modules~TextCompletion.TextCompletionView→MarkEditMac~Modules~FontPicker.View
- Direction
- MarkEditMac~Modules~TextCompletion uses MarkEditMac~Modules~FontPicker, so a change to MarkEditMac~Modules~FontPicker can break MarkEditMac~Modules~TextCompletion, while a change to MarkEditMac~Modules~TextCompletion can't break MarkEditMac~Modules~FontPicker.
- Position
- Below the diagonal: MarkEditMac~Modules~TextCompletion uses a module listed above it, which is the healthy direction.
21→20 MarkEditMac~Modules~TextCompletion uses MarkEditMac~Scripting✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Modules~TextCompletion uses a type in MarkEditMac~Scripting.
- The types involved
MarkEditMac~Modules~TextCompletion.TextCompletionContext→MarkEditMac~Scripting.NSColorMarkEditMac~Modules~TextCompletion.TextCompletionPanel→MarkEditMac~Scripting.NSColor
- Direction
- MarkEditMac~Modules~TextCompletion uses MarkEditMac~Scripting, so a change to MarkEditMac~Scripting can break MarkEditMac~Modules~TextCompletion, while a change to MarkEditMac~Modules~TextCompletion can't break MarkEditMac~Scripting.
- Position
- Below the diagonal: MarkEditMac~Modules~TextCompletion uses a module listed above it, which is the healthy direction.
21→22 MarkEditMac~Modules~TextCompletion uses MarkEditMac~Modules~AppKitExtensions part of a loop✕
- Connections
- 3 pairs of types, where a type in MarkEditMac~Modules~TextCompletion uses a type in MarkEditMac~Modules~AppKitExtensions.
- The types involved
MarkEditMac~Modules~TextCompletion.ContentView→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Modules~TextCompletion.TextCompletionContext→MarkEditMac~Modules~AppKitExtensions.NSAppearanceMarkEditMac~Modules~TextCompletion.TextCompletionContext→MarkEditMac~Modules~AppKitExtensions.NSWindow
- Direction
- MarkEditMac~Modules~TextCompletion uses MarkEditMac~Modules~AppKitExtensions, so a change to MarkEditMac~Modules~AppKitExtensions can break MarkEditMac~Modules~TextCompletion, while a change to MarkEditMac~Modules~TextCompletion can't break MarkEditMac~Modules~AppKitExtensions.
- Position
- Above the diagonal, so 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→31 MarkEditMac~Modules~TextCompletion uses MarkEditMac~Modules~QuickSearchUI part of a loop✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Modules~TextCompletion uses a type in MarkEditMac~Modules~QuickSearchUI.
- The types involved
MarkEditMac~Modules~TextCompletion.ContentView→MarkEditMac~Modules~QuickSearchUI.CGRectMarkEditMac~Modules~TextCompletion.TextCompletionContext→MarkEditMac~Modules~QuickSearchUI.CGRect
- Direction
- MarkEditMac~Modules~TextCompletion uses MarkEditMac~Modules~QuickSearchUI, so a change to MarkEditMac~Modules~QuickSearchUI can break MarkEditMac~Modules~TextCompletion, while a change to MarkEditMac~Modules~TextCompletion can't break MarkEditMac~Modules~QuickSearchUI.
- Position
- Above the diagonal, so 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→34 MarkEditMac~Modules~TextCompletion uses MarkEditCore~Extensions part of a loop✕
- Connections
- 4 pairs of types, where a type in MarkEditMac~Modules~TextCompletion uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditMac~Modules~TextCompletion.TextCompletionContext→MarkEditCore~Extensions.StringMarkEditMac~Modules~TextCompletion.TextCompletionLocalizable→MarkEditCore~Extensions.StringMarkEditMac~Modules~TextCompletion.TextCompletionPanel→MarkEditCore~Extensions.StringMarkEditMac~Modules~TextCompletion.TextCompletionState→MarkEditCore~Extensions.String
- Direction
- MarkEditMac~Modules~TextCompletion uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Modules~TextCompletion, while a change to MarkEditMac~Modules~TextCompletion can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so 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→11 MarkEditMac~Modules~AppKitExtensions uses MarkEditKit~Extensions✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Modules~AppKitExtensions uses a type in MarkEditKit~Extensions.
- The types involved
MarkEditMac~Modules~AppKitExtensions.Handler→MarkEditKit~Extensions.NSObjectMarkEditMac~Modules~AppKitExtensions.NSDocument→MarkEditKit~Extensions.NSFileVersion
- Direction
- MarkEditMac~Modules~AppKitExtensions uses MarkEditKit~Extensions, so a change to MarkEditKit~Extensions can break MarkEditMac~Modules~AppKitExtensions, while a change to MarkEditMac~Modules~AppKitExtensions can't break MarkEditKit~Extensions.
- Position
- Below the diagonal: MarkEditMac~Modules~AppKitExtensions uses a module listed above it, which is the healthy direction.
22→20 MarkEditMac~Modules~AppKitExtensions uses MarkEditMac~Scripting✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Modules~AppKitExtensions uses a type in MarkEditMac~Scripting.
- The types involved
MarkEditMac~Modules~AppKitExtensions.NSImage→MarkEditMac~Scripting.NSColorMarkEditMac~Modules~AppKitExtensions.NSView→MarkEditMac~Scripting.NSColor
- Direction
- MarkEditMac~Modules~AppKitExtensions uses MarkEditMac~Scripting, so a change to MarkEditMac~Scripting can break MarkEditMac~Modules~AppKitExtensions, while a change to MarkEditMac~Modules~AppKitExtensions can't break MarkEditMac~Scripting.
- Position
- Below the diagonal: MarkEditMac~Modules~AppKitExtensions uses a module listed above it, which is the healthy direction.
22→21 MarkEditMac~Modules~AppKitExtensions uses MarkEditMac~Modules~TextCompletion✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Modules~AppKitExtensions uses a type in MarkEditMac~Modules~TextCompletion.
- The types involved
MarkEditMac~Modules~AppKitExtensions.NSWindow→MarkEditMac~Modules~TextCompletion.NSScreen
- Direction
- MarkEditMac~Modules~AppKitExtensions uses MarkEditMac~Modules~TextCompletion, so a change to MarkEditMac~Modules~TextCompletion can break MarkEditMac~Modules~AppKitExtensions, while a change to MarkEditMac~Modules~AppKitExtensions can't break MarkEditMac~Modules~TextCompletion.
- Position
- Below the diagonal: MarkEditMac~Modules~AppKitExtensions uses a module listed above it, which is the healthy direction.
22→23 MarkEditMac~Modules~AppKitExtensions uses MarkEditMac~Main part of a loop✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Modules~AppKitExtensions uses a type in MarkEditMac~Main.
- The types involved
MarkEditMac~Modules~AppKitExtensions.NSWindow→MarkEditMac~Main.NSUserInterfaceItemIdentifier
- Direction
- MarkEditMac~Modules~AppKitExtensions uses MarkEditMac~Main, so a change to MarkEditMac~Main can break MarkEditMac~Modules~AppKitExtensions, while a change to MarkEditMac~Modules~AppKitExtensions can't break MarkEditMac~Main.
- Position
- Above the diagonal, so 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→29 MarkEditMac~Modules~AppKitExtensions uses MarkEditMac~Extension part of a loop✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Modules~AppKitExtensions uses a type in MarkEditMac~Extension.
- The types involved
MarkEditMac~Modules~AppKitExtensions.NSAppearance→MarkEditMac~Extension.NameMarkEditMac~Modules~AppKitExtensions.NSWindow→MarkEditMac~Extension.Identifier
- Direction
- MarkEditMac~Modules~AppKitExtensions uses MarkEditMac~Extension, so a change to MarkEditMac~Extension can break MarkEditMac~Modules~AppKitExtensions, while a change to MarkEditMac~Modules~AppKitExtensions can't break MarkEditMac~Extension.
- Position
- Above the diagonal, so 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 MarkEditMac~Modules~AppKitExtensions uses MarkEditMac~Modules~QuickSearchUI part of a loop✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Modules~AppKitExtensions uses a type in MarkEditMac~Modules~QuickSearchUI.
- The types involved
MarkEditMac~Modules~AppKitExtensions.NSBezierPath→MarkEditMac~Modules~QuickSearchUI.CGRectMarkEditMac~Modules~AppKitExtensions.NSWindow→MarkEditMac~Modules~QuickSearchUI.CGRect
- Direction
- MarkEditMac~Modules~AppKitExtensions uses MarkEditMac~Modules~QuickSearchUI, so a change to MarkEditMac~Modules~QuickSearchUI can break MarkEditMac~Modules~AppKitExtensions, while a change to MarkEditMac~Modules~AppKitExtensions can't break MarkEditMac~Modules~QuickSearchUI.
- Position
- Above the diagonal, so 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 MarkEditMac~Modules~AppKitExtensions uses MarkEditKit part of a loop✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Modules~AppKitExtensions uses a type in MarkEditKit.
- The types involved
MarkEditMac~Modules~AppKitExtensions.NSDocument→MarkEditKit.Data
- Direction
- MarkEditMac~Modules~AppKitExtensions uses MarkEditKit, so a change to MarkEditKit can break MarkEditMac~Modules~AppKitExtensions, while a change to MarkEditMac~Modules~AppKitExtensions can't break MarkEditKit.
- Position
- Above the diagonal, so 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→34 MarkEditMac~Modules~AppKitExtensions uses MarkEditCore~Extensions part of a loop✕
- Connections
- 17 pairs of types, where a type in MarkEditMac~Modules~AppKitExtensions uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditMac~Modules~AppKitExtensions.Bundle→MarkEditCore~Extensions.StringMarkEditMac~Modules~AppKitExtensions.Bundle→MarkEditCore~Extensions.URLMarkEditMac~Modules~AppKitExtensions.CALayer→MarkEditCore~Extensions.StringMarkEditMac~Modules~AppKitExtensions.ClosureActionable→MarkEditCore~Extensions.StringMarkEditMac~Modules~AppKitExtensions.ModifierFlags→MarkEditCore~Extensions.StringMarkEditMac~Modules~AppKitExtensions.NSAlert→MarkEditCore~Extensions.StringMarkEditMac~Modules~AppKitExtensions.NSButton→MarkEditCore~Extensions.StringMarkEditMac~Modules~AppKitExtensions.NSDataDetector→MarkEditCore~Extensions.StringMarkEditMac~Modules~AppKitExtensions.NSDocument→MarkEditCore~Extensions.URLMarkEditMac~Modules~AppKitExtensions.NSFont→MarkEditCore~Extensions.StringMarkEditMac~Modules~AppKitExtensions.NSImage→MarkEditCore~Extensions.StringMarkEditMac~Modules~AppKitExtensions.NSPasteboard→MarkEditCore~Extensions.StringMarkEditMac~Modules~AppKitExtensions.NSPasteboard→MarkEditCore~Extensions.URLMarkEditMac~Modules~AppKitExtensions.NSSearchField→MarkEditCore~Extensions.StringMarkEditMac~Modules~AppKitExtensions.NSWorkspace→MarkEditCore~Extensions.StringMarkEditMac~Modules~AppKitExtensions.NSWorkspace→MarkEditCore~Extensions.URLMarkEditMac~Modules~AppKitExtensions.ProcessInfo→MarkEditCore~Extensions.String
- Direction
- MarkEditMac~Modules~AppKitExtensions uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Modules~AppKitExtensions, while a change to MarkEditMac~Modules~AppKitExtensions can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→11 MarkEditMac~Main uses MarkEditKit~Extensions✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Main uses a type in MarkEditKit~Extensions.
- The types involved
MarkEditMac~Main.AppDelegate→MarkEditKit~Extensions.NSObjectMarkEditMac~Main.AppWritingTools→MarkEditKit~Extensions.NSObject
- Direction
- MarkEditMac~Main uses MarkEditKit~Extensions, so a change to MarkEditKit~Extensions can break MarkEditMac~Main, while a change to MarkEditMac~Main can't break MarkEditKit~Extensions.
- Position
- Below the diagonal: MarkEditMac~Main uses a module listed above it, which is the healthy direction.
23→12 MarkEditMac~Main uses MarkEditMac~Modules~FontPicker✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Main uses a type in MarkEditMac~Modules~FontPicker.
- The types involved
MarkEditMac~Main.Editor→MarkEditMac~Modules~FontPicker.FontStyle
- Direction
- MarkEditMac~Main uses MarkEditMac~Modules~FontPicker, so a change to MarkEditMac~Modules~FontPicker can break MarkEditMac~Main, while a change to MarkEditMac~Main can't break MarkEditMac~Modules~FontPicker.
- Position
- Below the diagonal: MarkEditMac~Main uses a module listed above it, which is the healthy direction.
23→14 MarkEditMac~Main uses UpdateInstaller~UpdaterCore✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Main uses a type in UpdateInstaller~UpdaterCore.
- The types involved
MarkEditMac~Main.AppRuntimeConfig→UpdateInstaller~UpdaterCore.[String: Any]
- Direction
- MarkEditMac~Main uses UpdateInstaller~UpdaterCore, so a change to UpdateInstaller~UpdaterCore can break MarkEditMac~Main, while a change to MarkEditMac~Main can't break UpdateInstaller~UpdaterCore.
- Position
- Below the diagonal: MarkEditMac~Main uses a module listed above it, which is the healthy direction.
23→17 MarkEditMac~Main uses repository✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Main uses a type in repository.
- The types involved
MarkEditMac~Main.Bookmark→repository.Error
- Direction
- MarkEditMac~Main uses repository, so a change to repository can break MarkEditMac~Main, while a change to MarkEditMac~Main can't break repository.
- Position
- Below the diagonal: MarkEditMac~Main uses a module listed above it, which is the healthy direction.
23→20 MarkEditMac~Main uses MarkEditMac~Scripting✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Main uses a type in MarkEditMac~Scripting.
- The types involved
MarkEditMac~Main.AppDelegate→MarkEditMac~Scripting.NSColorMarkEditMac~Main.AppTheme→MarkEditMac~Scripting.NSColor
- Direction
- MarkEditMac~Main uses MarkEditMac~Scripting, so a change to MarkEditMac~Scripting can break MarkEditMac~Main, while a change to MarkEditMac~Main can't break MarkEditMac~Scripting.
- Position
- Below the diagonal: MarkEditMac~Main uses a module listed above it, which is the healthy direction.
23→22 MarkEditMac~Main uses MarkEditMac~Modules~AppKitExtensions✕
- Connections
- 6 pairs of types, where a type in MarkEditMac~Main uses a type in MarkEditMac~Modules~AppKitExtensions.
- The types involved
MarkEditMac~Main.AppDelegate→MarkEditMac~Modules~AppKitExtensions.NSWindowMarkEditMac~Main.AppDocumentController→MarkEditMac~Modules~AppKitExtensions.NSWindowMarkEditMac~Main.AppTheme→MarkEditMac~Modules~AppKitExtensions.NSAppearanceMarkEditMac~Main.AppTheme→MarkEditMac~Modules~AppKitExtensions.NSImageMarkEditMac~Main.AppWritingTools→MarkEditMac~Modules~AppKitExtensions.NSImageMarkEditMac~Main.Appearance→MarkEditMac~Modules~AppKitExtensions.NSAppearance
- Direction
- MarkEditMac~Main uses MarkEditMac~Modules~AppKitExtensions, so a change to MarkEditMac~Modules~AppKitExtensions can break MarkEditMac~Main, while a change to MarkEditMac~Main can't break MarkEditMac~Modules~AppKitExtensions.
- Position
- Below the diagonal: MarkEditMac~Main uses a module listed above it, which is the healthy direction.
23→26 MarkEditMac~Main uses MarkEditMac~Extras part of a loop✕
- Connections
- 5 pairs of types, where a type in MarkEditMac~Main uses a type in MarkEditMac~Extras.
- The types involved
MarkEditMac~Main.AppDelegate→MarkEditMac~Extras.NSApplicationMarkEditMac~Main.AppDelegate→MarkEditMac~Extras.NSMenuMarkEditMac~Main.AppDocumentController→MarkEditMac~Extras.NSDocumentControllerMarkEditMac~Main.AppWritingTools→MarkEditMac~Extras.NSMenuMarkEditMac~Main.Application→MarkEditMac~Extras.NSApplication
- Direction
- MarkEditMac~Main uses MarkEditMac~Extras, so a change to MarkEditMac~Extras can break MarkEditMac~Main, while a change to MarkEditMac~Main can't break MarkEditMac~Extras.
- Position
- Above the diagonal, so 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→29 MarkEditMac~Main uses MarkEditMac~Extension part of a loop✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Main uses a type in MarkEditMac~Extension.
- The types involved
MarkEditMac~Main.CustomToolbarItem→MarkEditMac~Extension.Identifier
- Direction
- MarkEditMac~Main uses MarkEditMac~Extension, so a change to MarkEditMac~Extension can break MarkEditMac~Main, while a change to MarkEditMac~Main can't break MarkEditMac~Extension.
- Position
- Above the diagonal, so 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 MarkEditMac~Main uses MarkEditMac~Editor part of a loop✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Main uses a type in MarkEditMac~Editor.
- The types involved
MarkEditMac~Main.AppDelegate→MarkEditMac~Editor.EditorDocumentMarkEditMac~Main.AppDelegate→MarkEditMac~Editor.EditorViewController
- Direction
- MarkEditMac~Main uses MarkEditMac~Editor, so a change to MarkEditMac~Editor can break MarkEditMac~Main, while a change to MarkEditMac~Main can't break MarkEditMac~Editor.
- Position
- Above the diagonal, so 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 MarkEditMac~Main uses MarkEditMac~Modules~QuickSearchUI part of a loop✕
- Connections
- 3 pairs of types, where a type in MarkEditMac~Main uses a type in MarkEditMac~Modules~QuickSearchUI.
- The types involved
MarkEditMac~Main.AppDelegate→MarkEditMac~Modules~QuickSearchUI.NSMenuItemMarkEditMac~Main.AppDelegate→MarkEditMac~Modules~QuickSearchUI.QuickSearchControllerMarkEditMac~Main.AppDelegate→MarkEditMac~Modules~QuickSearchUI.QuickSearchDocument
- Direction
- MarkEditMac~Main uses MarkEditMac~Modules~QuickSearchUI, so a change to MarkEditMac~Modules~QuickSearchUI can break MarkEditMac~Main, while a change to MarkEditMac~Main can't break MarkEditMac~Modules~QuickSearchUI.
- Position
- Above the diagonal, so 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→32 MarkEditMac~Main uses MarkEditKit~Bridge part of a loop✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Main uses a type in MarkEditKit~Bridge.
- The types involved
MarkEditMac~Main.Editor→MarkEditKit~Bridge.TabKeyBehaviorMarkEditMac~Main.General→MarkEditKit~Bridge.LineEndings
- Direction
- MarkEditMac~Main uses MarkEditKit~Bridge, so a change to MarkEditKit~Bridge can break MarkEditMac~Main, while a change to MarkEditMac~Main can't break MarkEditKit~Bridge.
- Position
- Above the diagonal, so 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 MarkEditMac~Main uses MarkEditKit part of a loop✕
- Connections
- 6 pairs of types, where a type in MarkEditMac~Main uses a type in MarkEditKit.
- The types involved
MarkEditMac~Main.AppDocumentController→MarkEditKit.EditorTextEncodingMarkEditMac~Main.AppRuntimeConfig→MarkEditKit.DataMarkEditMac~Main.Bookmark→MarkEditKit.DataMarkEditMac~Main.BookmarkStore→MarkEditKit.DataMarkEditMac~Main.General→MarkEditKit.DataMarkEditMac~Main.General→MarkEditKit.EditorTextEncoding
- Direction
- MarkEditMac~Main uses MarkEditKit, so a change to MarkEditKit can break MarkEditMac~Main, while a change to MarkEditMac~Main can't break MarkEditKit.
- Position
- Above the diagonal, so 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→34 MarkEditMac~Main uses MarkEditCore~Extensions part of a loop✕
- Connections
- 44 pairs of types, where a type in MarkEditMac~Main uses a type in MarkEditCore~Extensions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
MarkEditMac~Main.AppCustomization→MarkEditCore~Extensions.StringMarkEditMac~Main.AppCustomization→MarkEditCore~Extensions.URLMarkEditMac~Main.AppDelegate→MarkEditCore~Extensions.StringMarkEditMac~Main.AppDelegate→MarkEditCore~Extensions.URLMarkEditMac~Main.AppDocumentController→MarkEditCore~Extensions.StringMarkEditMac~Main.AppDocumentController→MarkEditCore~Extensions.URLMarkEditMac~Main.AppHotKeys→MarkEditCore~Extensions.StringMarkEditMac~Main.AppPreferences→MarkEditCore~Extensions.StringMarkEditMac~Main.AppRelauncher→MarkEditCore~Extensions.URLMarkEditMac~Main.AppRuntimeConfig→MarkEditCore~Extensions.StringMarkEditMac~Main.AppTheme→MarkEditCore~Extensions.StringMarkEditMac~Main.AppWritingTools→MarkEditCore~Extensions.StringMarkEditMac~Main.Appearance→MarkEditCore~Extensions.StringMarkEditMac~Main.ApplicationEnvironment→MarkEditCore~Extensions.StringMarkEditMac~Main.ApplicationEnvironment→MarkEditCore~Extensions.URLMarkEditMac~Main.ApplicationEnvironment→MarkEditCore~Extensions.UserDefaultsMarkEditMac~Main.Bookmark→MarkEditCore~Extensions.URLMarkEditMac~Main.BookmarkStore→MarkEditCore~Extensions.URLMarkEditMac~Main.Bookmarks→MarkEditCore~Extensions.StringMarkEditMac~Main.CodingKeys→MarkEditCore~Extensions.StringMarkEditMac~Main.CustomToolbarItem→MarkEditCore~Extensions.StringMarkEditMac~Main.Definition→MarkEditCore~Extensions.StringMarkEditMac~Main.Document→MarkEditCore~Extensions.StringMarkEditMac~Main.Editor→MarkEditCore~Extensions.StringMarkEditMac~Main.FileType→MarkEditCore~Extensions.String
- Direction
- MarkEditMac~Main uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Main, while a change to MarkEditMac~Main can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→35 MarkEditMac~Main uses MarkEditCore part of a loop✕
- Connections
- 9 pairs of types, where a type in MarkEditMac~Main uses a type in MarkEditCore.
- The types involved
MarkEditMac~Main.AppPreferences→MarkEditCore.EditorConfigMarkEditMac~Main.AppRuntimeConfig→MarkEditCore.EditorIndentBehaviorMarkEditMac~Main.Appearance→MarkEditCore.CompactCodableEnumMarkEditMac~Main.Definition→MarkEditCore.EditorIndentBehaviorMarkEditMac~Main.Editor→MarkEditCore.EditorInvisiblesBehaviorMarkEditMac~Main.IndentUnit→MarkEditCore.CompactCodableEnumMarkEditMac~Main.LineHeight→MarkEditCore.CompactCodableEnumMarkEditMac~Main.NewWindowBehavior→MarkEditCore.CompactCodableEnumMarkEditMac~Main.ToolbarMode→MarkEditCore.CompactCodableEnum
- Direction
- MarkEditMac~Main uses MarkEditCore, so a change to MarkEditCore can break MarkEditMac~Main, while a change to MarkEditMac~Main can't break MarkEditCore.
- Position
- Above the diagonal, so 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→12 MarkEditMac~Modules~SharedUI uses MarkEditMac~Modules~FontPicker✕
- Connections
- 10 pairs of types, where a type in MarkEditMac~Modules~SharedUI uses a type in MarkEditMac~Modules~FontPicker.
- The types involved
MarkEditMac~Modules~SharedUI.ActionableInfoBar→MarkEditMac~Modules~FontPicker.ViewMarkEditMac~Modules~SharedUI.ColorPatternSwatch→MarkEditMac~Modules~FontPicker.ViewMarkEditMac~Modules~SharedUI.HighlightedText→MarkEditMac~Modules~FontPicker.ViewMarkEditMac~Modules~SharedUI.LabeledProgressView→MarkEditMac~Modules~FontPicker.ViewMarkEditMac~Modules~SharedUI.Measurer→MarkEditMac~Modules~FontPicker.ViewMarkEditMac~Modules~SharedUI.PillButton→MarkEditMac~Modules~FontPicker.ViewMarkEditMac~Modules~SharedUI.RingProgressView→MarkEditMac~Modules~FontPicker.ViewMarkEditMac~Modules~SharedUI.SpinningRing→MarkEditMac~Modules~FontPicker.ViewMarkEditMac~Modules~SharedUI.TableCellWrapper→MarkEditMac~Modules~FontPicker.ViewMarkEditMac~Modules~SharedUI.ThemePreview→MarkEditMac~Modules~FontPicker.View
- Direction
- MarkEditMac~Modules~SharedUI uses MarkEditMac~Modules~FontPicker, so a change to MarkEditMac~Modules~FontPicker can break MarkEditMac~Modules~SharedUI, while a change to MarkEditMac~Modules~SharedUI can't break MarkEditMac~Modules~FontPicker.
- Position
- Below the diagonal: MarkEditMac~Modules~SharedUI uses a module listed above it, which is the healthy direction.
24→20 MarkEditMac~Modules~SharedUI uses MarkEditMac~Scripting✕
- Connections
- 6 pairs of types, where a type in MarkEditMac~Modules~SharedUI uses a type in MarkEditMac~Scripting.
- The types involved
MarkEditMac~Modules~SharedUI.BackgroundTheming→MarkEditMac~Scripting.NSColorMarkEditMac~Modules~SharedUI.BezelView→MarkEditMac~Scripting.NSColorMarkEditMac~Modules~SharedUI.DividerView→MarkEditMac~Scripting.NSColorMarkEditMac~Modules~SharedUI.LabeledSearchField→MarkEditMac~Scripting.NSColorMarkEditMac~Modules~SharedUI.MaterialView→MarkEditMac~Scripting.NSColorMarkEditMac~Modules~SharedUI.RoundedButtonGroup→MarkEditMac~Scripting.NSColor
- Direction
- MarkEditMac~Modules~SharedUI uses MarkEditMac~Scripting, so a change to MarkEditMac~Scripting can break MarkEditMac~Modules~SharedUI, while a change to MarkEditMac~Modules~SharedUI can't break MarkEditMac~Scripting.
- Position
- Below the diagonal: MarkEditMac~Modules~SharedUI uses a module listed above it, which is the healthy direction.
24→22 MarkEditMac~Modules~SharedUI uses MarkEditMac~Modules~AppKitExtensions✕
- Connections
- 12 pairs of types, where a type in MarkEditMac~Modules~SharedUI uses a type in MarkEditMac~Modules~AppKitExtensions.
- The types involved
MarkEditMac~Modules~SharedUI.BackgroundTheming→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Modules~SharedUI.BezelView→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Modules~SharedUI.CustomIconView→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Modules~SharedUI.DividerView→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Modules~SharedUI.LabelView→MarkEditMac~Modules~AppKitExtensions.NSTextFieldMarkEditMac~Modules~SharedUI.LabeledSearchField→MarkEditMac~Modules~AppKitExtensions.NSSearchFieldMarkEditMac~Modules~SharedUI.LabeledSearchField→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Modules~SharedUI.MaterialView→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Modules~SharedUI.NonBezelButton→MarkEditMac~Modules~AppKitExtensions.NSButtonMarkEditMac~Modules~SharedUI.RoundedButtonGroup→MarkEditMac~Modules~AppKitExtensions.NSButtonMarkEditMac~Modules~SharedUI.RoundedButtonGroup→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Modules~SharedUI.TitleOnlyButton→MarkEditMac~Modules~AppKitExtensions.NSFont
- Direction
- MarkEditMac~Modules~SharedUI uses MarkEditMac~Modules~AppKitExtensions, so a change to MarkEditMac~Modules~AppKitExtensions can break MarkEditMac~Modules~SharedUI, while a change to MarkEditMac~Modules~SharedUI can't break MarkEditMac~Modules~AppKitExtensions.
- Position
- Below the diagonal: MarkEditMac~Modules~SharedUI uses a module listed above it, which is the healthy direction.
24→31 MarkEditMac~Modules~SharedUI uses MarkEditMac~Modules~QuickSearchUI part of a loop✕
- Connections
- 4 pairs of types, where a type in MarkEditMac~Modules~SharedUI uses a type in MarkEditMac~Modules~QuickSearchUI.
- The types involved
MarkEditMac~Modules~SharedUI.BezelView→MarkEditMac~Modules~QuickSearchUI.CGRectMarkEditMac~Modules~SharedUI.LabelView→MarkEditMac~Modules~QuickSearchUI.CGRectMarkEditMac~Modules~SharedUI.LabeledSearchField→MarkEditMac~Modules~QuickSearchUI.CGRectMarkEditMac~Modules~SharedUI.NonBezelButton→MarkEditMac~Modules~QuickSearchUI.CGRect
- Direction
- MarkEditMac~Modules~SharedUI uses MarkEditMac~Modules~QuickSearchUI, so a change to MarkEditMac~Modules~QuickSearchUI can break MarkEditMac~Modules~SharedUI, while a change to MarkEditMac~Modules~SharedUI can't break MarkEditMac~Modules~QuickSearchUI.
- Position
- Above the diagonal, so 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→34 MarkEditMac~Modules~SharedUI uses MarkEditCore~Extensions part of a loop✕
- Connections
- 14 pairs of types, where a type in MarkEditMac~Modules~SharedUI uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditMac~Modules~SharedUI.ActionableInfoBar→MarkEditCore~Extensions.StringMarkEditMac~Modules~SharedUI.AttributedString→MarkEditCore~Extensions.StringMarkEditMac~Modules~SharedUI.Color→MarkEditCore~Extensions.StringMarkEditMac~Modules~SharedUI.ColorPatternSwatch→MarkEditCore~Extensions.StringMarkEditMac~Modules~SharedUI.Constants→MarkEditCore~Extensions.StringMarkEditMac~Modules~SharedUI.HighlightedText→MarkEditCore~Extensions.StringMarkEditMac~Modules~SharedUI.IconOnlyButton→MarkEditCore~Extensions.StringMarkEditMac~Modules~SharedUI.LabeledProgressView→MarkEditCore~Extensions.StringMarkEditMac~Modules~SharedUI.LabeledSearchField→MarkEditCore~Extensions.StringMarkEditMac~Modules~SharedUI.PillButton→MarkEditCore~Extensions.StringMarkEditMac~Modules~SharedUI.RoundedNavigateButtons→MarkEditCore~Extensions.StringMarkEditMac~Modules~SharedUI.Text→MarkEditCore~Extensions.StringMarkEditMac~Modules~SharedUI.ThemePreview→MarkEditCore~Extensions.StringMarkEditMac~Modules~SharedUI.TitleOnlyButton→MarkEditCore~Extensions.String
- Direction
- MarkEditMac~Modules~SharedUI uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Modules~SharedUI, while a change to MarkEditMac~Modules~SharedUI can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so 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→12 MarkEditMac~Modules~Statistics uses MarkEditMac~Modules~FontPicker✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Modules~Statistics uses a type in MarkEditMac~Modules~FontPicker.
- The types involved
MarkEditMac~Modules~Statistics.StatisticsCell→MarkEditMac~Modules~FontPicker.ViewMarkEditMac~Modules~Statistics.StatisticsView→MarkEditMac~Modules~FontPicker.View
- Direction
- MarkEditMac~Modules~Statistics uses MarkEditMac~Modules~FontPicker, so a change to MarkEditMac~Modules~FontPicker can break MarkEditMac~Modules~Statistics, while a change to MarkEditMac~Modules~Statistics can't break MarkEditMac~Modules~FontPicker.
- Position
- Below the diagonal: MarkEditMac~Modules~Statistics uses a module listed above it, which is the healthy direction.
25→20 MarkEditMac~Modules~Statistics uses MarkEditMac~Scripting✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Modules~Statistics uses a type in MarkEditMac~Scripting.
- The types involved
MarkEditMac~Modules~Statistics.StatisticsController→MarkEditMac~Scripting.NSColor
- Direction
- MarkEditMac~Modules~Statistics uses MarkEditMac~Scripting, so a change to MarkEditMac~Scripting can break MarkEditMac~Modules~Statistics, while a change to MarkEditMac~Modules~Statistics can't break MarkEditMac~Scripting.
- Position
- Below the diagonal: MarkEditMac~Modules~Statistics uses a module listed above it, which is the healthy direction.
25→22 MarkEditMac~Modules~Statistics uses MarkEditMac~Modules~AppKitExtensions✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Modules~Statistics uses a type in MarkEditMac~Modules~AppKitExtensions.
- The types involved
MarkEditMac~Modules~Statistics.StatisticsController→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Modules~Statistics.StatisticsController→MarkEditMac~Modules~AppKitExtensions.NSViewController
- Direction
- MarkEditMac~Modules~Statistics uses MarkEditMac~Modules~AppKitExtensions, so a change to MarkEditMac~Modules~AppKitExtensions can break MarkEditMac~Modules~Statistics, while a change to MarkEditMac~Modules~Statistics can't break MarkEditMac~Modules~AppKitExtensions.
- Position
- Below the diagonal: MarkEditMac~Modules~Statistics uses a module listed above it, which is the healthy direction.
25→32 MarkEditMac~Modules~Statistics uses MarkEditKit~Bridge part of a loop✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Modules~Statistics uses a type in MarkEditKit~Bridge.
- The types involved
MarkEditMac~Modules~Statistics.StatisticsController→MarkEditKit~Bridge.ReadableContentPair
- Direction
- MarkEditMac~Modules~Statistics uses MarkEditKit~Bridge, so a change to MarkEditKit~Bridge can break MarkEditMac~Modules~Statistics, while a change to MarkEditMac~Modules~Statistics can't break MarkEditKit~Bridge.
- Position
- Above the diagonal, so 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→34 MarkEditMac~Modules~Statistics uses MarkEditCore~Extensions part of a loop✕
- Connections
- 9 pairs of types, where a type in MarkEditMac~Modules~Statistics uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditMac~Modules~Statistics.FileSize→MarkEditCore~Extensions.StringMarkEditMac~Modules~Statistics.FileSize→MarkEditCore~Extensions.URLMarkEditMac~Modules~Statistics.ReadTime→MarkEditCore~Extensions.StringMarkEditMac~Modules~Statistics.StatisticsCell→MarkEditCore~Extensions.StringMarkEditMac~Modules~Statistics.StatisticsController→MarkEditCore~Extensions.URLMarkEditMac~Modules~Statistics.StatisticsLocalizable→MarkEditCore~Extensions.StringMarkEditMac~Modules~Statistics.StatisticsRule→MarkEditCore~Extensions.StringMarkEditMac~Modules~Statistics.StatisticsView→MarkEditCore~Extensions.URLMarkEditMac~Modules~Statistics.Tokenizer→MarkEditCore~Extensions.String
- Direction
- MarkEditMac~Modules~Statistics uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Modules~Statistics, while a change to MarkEditMac~Modules~Statistics can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so 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→11 MarkEditMac~Extras uses MarkEditKit~Extensions✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Extras uses a type in MarkEditKit~Extensions.
- The types involved
MarkEditMac~Extras.Terminator→MarkEditKit~Extensions.NSObject
- Direction
- MarkEditMac~Extras uses MarkEditKit~Extensions, so a change to MarkEditKit~Extensions can break MarkEditMac~Extras, while a change to MarkEditMac~Extras can't break MarkEditKit~Extensions.
- Position
- Below the diagonal: MarkEditMac~Extras uses a module listed above it, which is the healthy direction.
26→22 MarkEditMac~Extras uses MarkEditMac~Modules~AppKitExtensions✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Extras uses a type in MarkEditMac~Modules~AppKitExtensions.
- The types involved
MarkEditMac~Extras.NSSpellChecker→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Extras.Terminator→MarkEditMac~Modules~AppKitExtensions.NSDocument
- Direction
- MarkEditMac~Extras uses MarkEditMac~Modules~AppKitExtensions, so a change to MarkEditMac~Modules~AppKitExtensions can break MarkEditMac~Extras, while a change to MarkEditMac~Extras can't break MarkEditMac~Modules~AppKitExtensions.
- Position
- Below the diagonal: MarkEditMac~Extras uses a module listed above it, which is the healthy direction.
26→23 MarkEditMac~Extras uses MarkEditMac~Main✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Extras uses a type in MarkEditMac~Main.
- The types involved
MarkEditMac~Extras.NSApplication→MarkEditMac~Main.AppDelegateMarkEditMac~Extras.NSApplication→MarkEditMac~Main.NSOpenPanel
- Direction
- MarkEditMac~Extras uses MarkEditMac~Main, so a change to MarkEditMac~Main can break MarkEditMac~Extras, while a change to MarkEditMac~Extras can't break MarkEditMac~Main.
- Position
- Below the diagonal: MarkEditMac~Extras uses a module listed above it, which is the healthy direction.
26→30 MarkEditMac~Extras uses MarkEditMac~Editor part of a loop✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Extras uses a type in MarkEditMac~Editor.
- The types involved
MarkEditMac~Extras.NSApplication→MarkEditMac~Editor.EditorViewControllerMarkEditMac~Extras.NSDocumentController→MarkEditMac~Editor.EditorDocument
- Direction
- MarkEditMac~Extras uses MarkEditMac~Editor, so a change to MarkEditMac~Editor can break MarkEditMac~Extras, while a change to MarkEditMac~Extras can't break MarkEditMac~Editor.
- Position
- Above the diagonal, so 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→31 MarkEditMac~Extras uses MarkEditMac~Modules~QuickSearchUI part of a loop✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Extras uses a type in MarkEditMac~Modules~QuickSearchUI.
- The types involved
MarkEditMac~Extras.NSMenu→MarkEditMac~Modules~QuickSearchUI.NSMenuItemMarkEditMac~Extras.NSSpellChecker→MarkEditMac~Modules~QuickSearchUI.CGRect
- Direction
- MarkEditMac~Extras uses MarkEditMac~Modules~QuickSearchUI, so a change to MarkEditMac~Modules~QuickSearchUI can break MarkEditMac~Extras, while a change to MarkEditMac~Extras can't break MarkEditMac~Modules~QuickSearchUI.
- Position
- Above the diagonal, so 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→32 MarkEditMac~Extras uses MarkEditKit~Bridge part of a loop✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Extras uses a type in MarkEditKit~Bridge.
- The types involved
MarkEditMac~Extras.NSSpellChecker→MarkEditKit~Bridge.WebBridgeCompletion
- Direction
- MarkEditMac~Extras uses MarkEditKit~Bridge, so a change to MarkEditKit~Bridge can break MarkEditMac~Extras, while a change to MarkEditMac~Extras can't break MarkEditKit~Bridge.
- Position
- Above the diagonal, so 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→34 MarkEditMac~Extras uses MarkEditCore~Extensions part of a loop✕
- Connections
- 4 pairs of types, where a type in MarkEditMac~Extras uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditMac~Extras.NSDocumentController→MarkEditCore~Extensions.StringMarkEditMac~Extras.NSMenu→MarkEditCore~Extensions.StringMarkEditMac~Extras.NSSpellChecker→MarkEditCore~Extensions.StringMarkEditMac~Extras.NSSpellChecker→MarkEditCore~Extensions.WKWebView
- Direction
- MarkEditMac~Extras uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Extras, while a change to MarkEditMac~Extras can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so 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→11 MarkEditMac~Modules~FileVersion uses MarkEditKit~Extensions✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Modules~FileVersion uses a type in MarkEditKit~Extensions.
- The types involved
MarkEditMac~Modules~FileVersion.FileVersionPicker→MarkEditKit~Extensions.NSFileVersionMarkEditMac~Modules~FileVersion.FileVersionPickerDelegate→MarkEditKit~Extensions.NSFileVersion
- Direction
- MarkEditMac~Modules~FileVersion uses MarkEditKit~Extensions, so a change to MarkEditKit~Extensions can break MarkEditMac~Modules~FileVersion, while a change to MarkEditMac~Modules~FileVersion can't break MarkEditKit~Extensions.
- Position
- Below the diagonal: MarkEditMac~Modules~FileVersion uses a module listed above it, which is the healthy direction.
27→22 MarkEditMac~Modules~FileVersion uses MarkEditMac~Modules~AppKitExtensions✕
- Connections
- 4 pairs of types, where a type in MarkEditMac~Modules~FileVersion uses a type in MarkEditMac~Modules~AppKitExtensions.
- The types involved
MarkEditMac~Modules~FileVersion.FileVersionPicker→MarkEditMac~Modules~AppKitExtensions.NSButtonMarkEditMac~Modules~FileVersion.FileVersionPicker→MarkEditMac~Modules~AppKitExtensions.NSScrollViewMarkEditMac~Modules~FileVersion.FileVersionPicker→MarkEditMac~Modules~AppKitExtensions.NSTextFieldMarkEditMac~Modules~FileVersion.FileVersionPicker→MarkEditMac~Modules~AppKitExtensions.NSViewController
- Direction
- MarkEditMac~Modules~FileVersion uses MarkEditMac~Modules~AppKitExtensions, so a change to MarkEditMac~Modules~AppKitExtensions can break MarkEditMac~Modules~FileVersion, while a change to MarkEditMac~Modules~FileVersion can't break MarkEditMac~Modules~AppKitExtensions.
- Position
- Below the diagonal: MarkEditMac~Modules~FileVersion uses a module listed above it, which is the healthy direction.
27→24 MarkEditMac~Modules~FileVersion uses MarkEditMac~Modules~SharedUI✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Modules~FileVersion uses a type in MarkEditMac~Modules~SharedUI.
- The types involved
MarkEditMac~Modules~FileVersion.FileVersionPicker→MarkEditMac~Modules~SharedUI.DividerViewMarkEditMac~Modules~FileVersion.FileVersionPicker→MarkEditMac~Modules~SharedUI.RoundedNavigateButtons
- Direction
- MarkEditMac~Modules~FileVersion uses MarkEditMac~Modules~SharedUI, so a change to MarkEditMac~Modules~SharedUI can break MarkEditMac~Modules~FileVersion, while a change to MarkEditMac~Modules~FileVersion can't break MarkEditMac~Modules~SharedUI.
- Position
- Below the diagonal: MarkEditMac~Modules~FileVersion uses a module listed above it, which is the healthy direction.
27→34 MarkEditMac~Modules~FileVersion uses MarkEditCore~Extensions part of a loop✕
- Connections
- 3 pairs of types, where a type in MarkEditMac~Modules~FileVersion uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditMac~Modules~FileVersion.FileVersionLocalizable→MarkEditCore~Extensions.StringMarkEditMac~Modules~FileVersion.FileVersionPicker→MarkEditCore~Extensions.StringMarkEditMac~Modules~FileVersion.FileVersionPicker→MarkEditCore~Extensions.URL
- Direction
- MarkEditMac~Modules~FileVersion uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Modules~FileVersion, while a change to MarkEditMac~Modules~FileVersion can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so 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→22 MarkEditMac~Panels uses MarkEditMac~Modules~AppKitExtensions✕
- Connections
- 4 pairs of types, where a type in MarkEditMac~Panels uses a type in MarkEditMac~Modules~AppKitExtensions.
- The types involved
MarkEditMac~Panels.Constants→MarkEditMac~Modules~AppKitExtensions.NSFontMarkEditMac~Panels.EditorFindPanel→MarkEditMac~Modules~AppKitExtensions.NSButtonMarkEditMac~Panels.EditorFindPanel→MarkEditMac~Modules~AppKitExtensions.NSTextFieldMarkEditMac~Panels.EditorReplaceTextField→MarkEditMac~Modules~AppKitExtensions.NSTextField
- Direction
- MarkEditMac~Panels uses MarkEditMac~Modules~AppKitExtensions, so a change to MarkEditMac~Modules~AppKitExtensions can break MarkEditMac~Panels, while a change to MarkEditMac~Panels can't break MarkEditMac~Modules~AppKitExtensions.
- Position
- Below the diagonal: MarkEditMac~Panels uses a module listed above it, which is the healthy direction.
28→24 MarkEditMac~Panels uses MarkEditMac~Modules~SharedUI✕
- Connections
- 4 pairs of types, where a type in MarkEditMac~Panels uses a type in MarkEditMac~Modules~SharedUI.
- The types involved
MarkEditMac~Panels.EditorFindPanel→MarkEditMac~Modules~SharedUI.LabeledSearchFieldMarkEditMac~Panels.EditorFindPanel→MarkEditMac~Modules~SharedUI.RoundedNavigateButtonsMarkEditMac~Panels.EditorReplaceButtons→MarkEditMac~Modules~SharedUI.RoundedButtonGroupMarkEditMac~Panels.EditorReplaceTextField→MarkEditMac~Modules~SharedUI.BezelView
- Direction
- MarkEditMac~Panels uses MarkEditMac~Modules~SharedUI, so a change to MarkEditMac~Modules~SharedUI can break MarkEditMac~Panels, while a change to MarkEditMac~Panels can't break MarkEditMac~Modules~SharedUI.
- Position
- Below the diagonal: MarkEditMac~Panels uses a module listed above it, which is the healthy direction.
28→30 MarkEditMac~Panels uses MarkEditMac~Editor part of a loop✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Panels uses a type in MarkEditMac~Editor.
- The types involved
MarkEditMac~Panels.EditorFindPanel→MarkEditMac~Editor.EditorPanelViewMarkEditMac~Panels.EditorReplacePanel→MarkEditMac~Editor.EditorPanelView
- Direction
- MarkEditMac~Panels uses MarkEditMac~Editor, so a change to MarkEditMac~Editor can break MarkEditMac~Panels, while a change to MarkEditMac~Panels can't break MarkEditMac~Editor.
- Position
- Above the diagonal, so 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→31 MarkEditMac~Panels uses MarkEditMac~Modules~QuickSearchUI part of a loop✕
- Connections
- 3 pairs of types, where a type in MarkEditMac~Panels uses a type in MarkEditMac~Modules~QuickSearchUI.
- The types involved
MarkEditMac~Panels.EditorFindPanel→MarkEditMac~Modules~QuickSearchUI.NSMenuItemMarkEditMac~Panels.EditorFindPanelDelegate→MarkEditMac~Modules~QuickSearchUI.NSMenuItemMarkEditMac~Panels.EditorReplaceTextField→MarkEditMac~Modules~QuickSearchUI.CGRect
- Direction
- MarkEditMac~Panels uses MarkEditMac~Modules~QuickSearchUI, so a change to MarkEditMac~Modules~QuickSearchUI can break MarkEditMac~Panels, while a change to MarkEditMac~Panels can't break MarkEditMac~Modules~QuickSearchUI.
- Position
- Above the diagonal, so 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→32 MarkEditMac~Panels uses MarkEditKit~Bridge part of a loop✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Panels uses a type in MarkEditKit~Bridge.
- The types involved
MarkEditMac~Panels.EditorFindPanel→MarkEditKit~Bridge.SearchCounterInfo
- Direction
- MarkEditMac~Panels uses MarkEditKit~Bridge, so a change to MarkEditKit~Bridge can break MarkEditMac~Panels, while a change to MarkEditMac~Panels can't break MarkEditKit~Bridge.
- Position
- Above the diagonal, so 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→34 MarkEditMac~Panels uses MarkEditCore~Extensions part of a loop✕
- Connections
- 3 pairs of types, where a type in MarkEditMac~Panels uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditMac~Panels.EditorFindPanel→MarkEditCore~Extensions.StringMarkEditMac~Panels.EditorFindPanelDelegate→MarkEditCore~Extensions.StringMarkEditMac~Panels.EditorReplacePanelDelegate→MarkEditCore~Extensions.String
- Direction
- MarkEditMac~Panels uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Panels, while a change to MarkEditMac~Panels can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so 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→12 MarkEditMac~Extension uses MarkEditMac~Modules~FontPicker✕
- Connections
- 3 pairs of types, where a type in MarkEditMac~Extension uses a type in MarkEditMac~Modules~FontPicker.
- The types involved
MarkEditMac~Extension.ExtensionsInfoBar→MarkEditMac~Modules~FontPicker.ViewMarkEditMac~Extension.ExtensionsRowView→MarkEditMac~Modules~FontPicker.ViewMarkEditMac~Extension.ExtensionsStateView→MarkEditMac~Modules~FontPicker.View
- Direction
- MarkEditMac~Extension uses MarkEditMac~Modules~FontPicker, so a change to MarkEditMac~Modules~FontPicker can break MarkEditMac~Extension, while a change to MarkEditMac~Extension can't break MarkEditMac~Modules~FontPicker.
- Position
- Below the diagonal: MarkEditMac~Extension uses a module listed above it, which is the healthy direction.
29→17 MarkEditMac~Extension uses repository✕
- Connections
- 3 pairs of types, where a type in MarkEditMac~Extension uses a type in repository.
- The types involved
MarkEditMac~Extension.Extension→repository.ErrorMarkEditMac~Extension.ExtensionsPresenting→repository.ErrorMarkEditMac~Extension.ExtensionsViewController→repository.Error
- Direction
- MarkEditMac~Extension uses repository, so a change to repository can break MarkEditMac~Extension, while a change to MarkEditMac~Extension can't break repository.
- Position
- Below the diagonal: MarkEditMac~Extension uses a module listed above it, which is the healthy direction.
29→18 MarkEditMac~Extension uses MarkEditMac~Modules~ExtensionCore✕
- Connections
- 9 pairs of types, where a type in MarkEditMac~Extension uses a type in MarkEditMac~Modules~ExtensionCore.
- The types involved
MarkEditMac~Extension.ExtensionInstaller→MarkEditMac~Modules~ExtensionCore.ExtensionEntryMarkEditMac~Extension.ExtensionUpdater→MarkEditMac~Modules~ExtensionCore.ExtensionUpdateMarkEditMac~Extension.ExtensionsModel→MarkEditMac~Modules~ExtensionCore.CategoryMarkEditMac~Extension.ExtensionsModel→MarkEditMac~Modules~ExtensionCore.ExtensionIndexMarkEditMac~Extension.ExtensionsModel→MarkEditMac~Modules~ExtensionCore.InstalledMarkEditMac~Extension.Item→MarkEditMac~Modules~ExtensionCore.CategoryMarkEditMac~Extension.Item→MarkEditMac~Modules~ExtensionCore.ColorSchemeMarkEditMac~Extension.Item→MarkEditMac~Modules~ExtensionCore.ExtensionEntryMarkEditMac~Extension.Item→MarkEditMac~Modules~ExtensionCore.Installed
- Direction
- MarkEditMac~Extension uses MarkEditMac~Modules~ExtensionCore, so a change to MarkEditMac~Modules~ExtensionCore can break MarkEditMac~Extension, while a change to MarkEditMac~Extension can't break MarkEditMac~Modules~ExtensionCore.
- Position
- Below the diagonal: MarkEditMac~Extension uses a module listed above it, which is the healthy direction.
29→22 MarkEditMac~Extension uses MarkEditMac~Modules~AppKitExtensions✕
- Connections
- 7 pairs of types, where a type in MarkEditMac~Extension uses a type in MarkEditMac~Modules~AppKitExtensions.
- The types involved
MarkEditMac~Extension.ExtensionsViewController→MarkEditMac~Modules~AppKitExtensions.NSScrollViewMarkEditMac~Extension.ExtensionsViewController→MarkEditMac~Modules~AppKitExtensions.NSTableViewMarkEditMac~Extension.ExtensionsViewController→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Extension.ExtensionsViewController→MarkEditMac~Modules~AppKitExtensions.NSViewControllerMarkEditMac~Extension.ExtensionsWindowController→MarkEditMac~Modules~AppKitExtensions.NSSearchFieldMarkEditMac~Extension.ExtensionsWindowController→MarkEditMac~Modules~AppKitExtensions.NSSearchToolbarItemMarkEditMac~Extension.ExtensionsWindowController→MarkEditMac~Modules~AppKitExtensions.NSWindow
- Direction
- MarkEditMac~Extension uses MarkEditMac~Modules~AppKitExtensions, so a change to MarkEditMac~Modules~AppKitExtensions can break MarkEditMac~Extension, while a change to MarkEditMac~Extension can't break MarkEditMac~Modules~AppKitExtensions.
- Position
- Below the diagonal: MarkEditMac~Extension uses a module listed above it, which is the healthy direction.
29→24 MarkEditMac~Extension uses MarkEditMac~Modules~SharedUI✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Extension uses a type in MarkEditMac~Modules~SharedUI.
- The types involved
MarkEditMac~Extension.ExtensionsViewController→MarkEditMac~Modules~SharedUI.Measurer
- Direction
- MarkEditMac~Extension uses MarkEditMac~Modules~SharedUI, so a change to MarkEditMac~Modules~SharedUI can break MarkEditMac~Extension, while a change to MarkEditMac~Extension can't break MarkEditMac~Modules~SharedUI.
- Position
- Below the diagonal: MarkEditMac~Extension uses a module listed above it, which is the healthy direction.
29→26 MarkEditMac~Extension uses MarkEditMac~Extras✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Extension uses a type in MarkEditMac~Extras.
- The types involved
MarkEditMac~Extension.ExtensionsViewController→MarkEditMac~Extras.NSMenuMarkEditMac~Extension.ExtensionsWindowController→MarkEditMac~Extras.NSMenu
- Direction
- MarkEditMac~Extension uses MarkEditMac~Extras, so a change to MarkEditMac~Extras can break MarkEditMac~Extension, while a change to MarkEditMac~Extension can't break MarkEditMac~Extras.
- Position
- Below the diagonal: MarkEditMac~Extension uses a module listed above it, which is the healthy direction.
29→30 MarkEditMac~Extension uses MarkEditMac~Editor part of a loop✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Extension uses a type in MarkEditMac~Editor.
- The types involved
MarkEditMac~Extension.ExtensionsWindowController→MarkEditMac~Editor.NSToolbarItem
- Direction
- MarkEditMac~Extension uses MarkEditMac~Editor, so a change to MarkEditMac~Editor can break MarkEditMac~Extension, while a change to MarkEditMac~Extension can't break MarkEditMac~Editor.
- Position
- Above the diagonal, so 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→31 MarkEditMac~Extension uses MarkEditMac~Modules~QuickSearchUI part of a loop✕
- Connections
- 3 pairs of types, where a type in MarkEditMac~Extension uses a type in MarkEditMac~Modules~QuickSearchUI.
- The types involved
MarkEditMac~Extension.ExtensionsViewController→MarkEditMac~Modules~QuickSearchUI.CGRectMarkEditMac~Extension.ExtensionsViewController→MarkEditMac~Modules~QuickSearchUI.NSMenuItemMarkEditMac~Extension.ExtensionsWindowController→MarkEditMac~Modules~QuickSearchUI.NSMenuItem
- Direction
- MarkEditMac~Extension uses MarkEditMac~Modules~QuickSearchUI, so a change to MarkEditMac~Modules~QuickSearchUI can break MarkEditMac~Extension, while a change to MarkEditMac~Extension can't break MarkEditMac~Modules~QuickSearchUI.
- Position
- Above the diagonal, so 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→34 MarkEditMac~Extension uses MarkEditCore~Extensions part of a loop✕
- Connections
- 15 pairs of types, where a type in MarkEditMac~Extension uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditMac~Extension.Extension→MarkEditCore~Extensions.StringMarkEditMac~Extension.ExtensionInstaller→MarkEditCore~Extensions.StringMarkEditMac~Extension.ExtensionInstaller→MarkEditCore~Extensions.URLMarkEditMac~Extension.ExtensionsListInteraction→MarkEditCore~Extensions.StringMarkEditMac~Extension.ExtensionsModel→MarkEditCore~Extensions.StringMarkEditMac~Extension.ExtensionsModel→MarkEditCore~Extensions.URLMarkEditMac~Extension.ExtensionsPresenting→MarkEditCore~Extensions.StringMarkEditMac~Extension.ExtensionsRowView→MarkEditCore~Extensions.StringMarkEditMac~Extension.ExtensionsRowView→MarkEditCore~Extensions.URLMarkEditMac~Extension.ExtensionsStateView→MarkEditCore~Extensions.StringMarkEditMac~Extension.ExtensionsViewController→MarkEditCore~Extensions.StringMarkEditMac~Extension.Identifier→MarkEditCore~Extensions.StringMarkEditMac~Extension.Item→MarkEditCore~Extensions.StringMarkEditMac~Extension.Item→MarkEditCore~Extensions.URLMarkEditMac~Extension.Mode→MarkEditCore~Extensions.String
- Direction
- MarkEditMac~Extension uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Extension, while a change to MarkEditMac~Extension can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so 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→11 MarkEditMac~Editor uses MarkEditKit~Extensions✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Editor uses a type in MarkEditKit~Extensions.
- The types involved
MarkEditMac~Editor.EditorDocument→MarkEditKit~Extensions.NSFileVersionMarkEditMac~Editor.EditorViewController→MarkEditKit~Extensions.NSFileVersion
- Direction
- MarkEditMac~Editor uses MarkEditKit~Extensions, so a change to MarkEditKit~Extensions can break MarkEditMac~Editor, while a change to MarkEditMac~Editor can't break MarkEditKit~Extensions.
- Position
- Below the diagonal: MarkEditMac~Editor uses a module listed above it, which is the healthy direction.
30→12 MarkEditMac~Editor uses MarkEditMac~Modules~FontPicker✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Editor uses a type in MarkEditMac~Modules~FontPicker.
- The types involved
MarkEditMac~Editor.EditorSaveOptionsView→MarkEditMac~Modules~FontPicker.View
- Direction
- MarkEditMac~Editor uses MarkEditMac~Modules~FontPicker, so a change to MarkEditMac~Modules~FontPicker can break MarkEditMac~Editor, while a change to MarkEditMac~Editor can't break MarkEditMac~Modules~FontPicker.
- Position
- Below the diagonal: MarkEditMac~Editor uses a module listed above it, which is the healthy direction.
30→17 MarkEditMac~Editor uses repository✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Editor uses a type in repository.
- The types involved
MarkEditMac~Editor.EditorViewController→repository.WKWebViewConfiguration
- Direction
- MarkEditMac~Editor uses repository, so a change to repository can break MarkEditMac~Editor, while a change to MarkEditMac~Editor can't break repository.
- Position
- Below the diagonal: MarkEditMac~Editor uses a module listed above it, which is the healthy direction.
30→19 MarkEditMac~Editor uses MarkEditMac~Modules~TextBundle✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Editor uses a type in MarkEditMac~Modules~TextBundle.
- The types involved
MarkEditMac~Editor.EditorDocument→MarkEditMac~Modules~TextBundle.FileWrapperMarkEditMac~Editor.EditorDocument→MarkEditMac~Modules~TextBundle.TextBundleWrapper
- Direction
- MarkEditMac~Editor uses MarkEditMac~Modules~TextBundle, so a change to MarkEditMac~Modules~TextBundle can break MarkEditMac~Editor, while a change to MarkEditMac~Editor can't break MarkEditMac~Modules~TextBundle.
- Position
- Below the diagonal: MarkEditMac~Editor uses a module listed above it, which is the healthy direction.
30→20 MarkEditMac~Editor uses MarkEditMac~Scripting✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Editor uses a type in MarkEditMac~Scripting.
- The types involved
MarkEditMac~Editor.EditorViewController→MarkEditMac~Scripting.NSColor
- Direction
- MarkEditMac~Editor uses MarkEditMac~Scripting, so a change to MarkEditMac~Scripting can break MarkEditMac~Editor, while a change to MarkEditMac~Editor can't break MarkEditMac~Scripting.
- Position
- Below the diagonal: MarkEditMac~Editor uses a module listed above it, which is the healthy direction.
30→22 MarkEditMac~Editor uses MarkEditMac~Modules~AppKitExtensions✕
- Connections
- 19 pairs of types, where a type in MarkEditMac~Editor uses a type in MarkEditMac~Modules~AppKitExtensions.
- The types involved
MarkEditMac~Editor.EditorClosedTabHistory→MarkEditMac~Modules~AppKitExtensions.NSWindowMarkEditMac~Editor.EditorDocument→MarkEditMac~Modules~AppKitExtensions.NSDocumentMarkEditMac~Editor.EditorDocument→MarkEditMac~Modules~AppKitExtensions.NSSavePanelMarkEditMac~Editor.EditorDocument→MarkEditMac~Modules~AppKitExtensions.NSWindowMarkEditMac~Editor.EditorPanelView→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Editor.EditorSaveOptionsView→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Editor.EditorStatusView→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Editor.EditorViewController→MarkEditMac~Modules~AppKitExtensions.NSEventMarkEditMac~Editor.EditorViewController→MarkEditMac~Modules~AppKitExtensions.NSImageMarkEditMac~Editor.EditorViewController→MarkEditMac~Modules~AppKitExtensions.NSPopoverMarkEditMac~Editor.EditorViewController→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Editor.EditorViewController→MarkEditMac~Modules~AppKitExtensions.NSViewControllerMarkEditMac~Editor.EditorWebView→MarkEditMac~Modules~AppKitExtensions.NSEventMarkEditMac~Editor.EditorWebViewActionDelegate→MarkEditMac~Modules~AppKitExtensions.NSEventMarkEditMac~Editor.EditorWindow→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Editor.EditorWindow→MarkEditMac~Modules~AppKitExtensions.NSWindowMarkEditMac~Editor.EditorWindowController→MarkEditMac~Modules~AppKitExtensions.NSWindowMarkEditMac~Editor.GlassButton→MarkEditMac~Modules~AppKitExtensions.NSButtonMarkEditMac~Editor.RestoredTab→MarkEditMac~Modules~AppKitExtensions.NSWindow
- Direction
- MarkEditMac~Editor uses MarkEditMac~Modules~AppKitExtensions, so a change to MarkEditMac~Modules~AppKitExtensions can break MarkEditMac~Editor, while a change to MarkEditMac~Editor can't break MarkEditMac~Modules~AppKitExtensions.
- Position
- Below the diagonal: MarkEditMac~Editor uses a module listed above it, which is the healthy direction.
30→23 MarkEditMac~Editor uses MarkEditMac~Main✕
- Connections
- 6 pairs of types, where a type in MarkEditMac~Editor uses a type in MarkEditMac~Main.
- The types involved
MarkEditMac~Editor.EditorViewController→MarkEditMac~Main.AppThemeMarkEditMac~Editor.EditorViewController→MarkEditMac~Main.CustomToolbarItemMarkEditMac~Editor.EditorViewController→MarkEditMac~Main.IndentUnitMarkEditMac~Editor.EditorWebView→MarkEditMac~Main.NSUserInterfaceItemIdentifierMarkEditMac~Editor.EditorWindow→MarkEditMac~Main.ToolbarModeMarkEditMac~Editor.NSToolbarItem→MarkEditMac~Main.CustomToolbarItem
- Direction
- MarkEditMac~Editor uses MarkEditMac~Main, so a change to MarkEditMac~Main can break MarkEditMac~Editor, while a change to MarkEditMac~Editor can't break MarkEditMac~Main.
- Position
- Below the diagonal: MarkEditMac~Editor uses a module listed above it, which is the healthy direction.
30→24 MarkEditMac~Editor uses MarkEditMac~Modules~SharedUI✕
- Connections
- 5 pairs of types, where a type in MarkEditMac~Editor uses a type in MarkEditMac~Modules~SharedUI.
- The types involved
MarkEditMac~Editor.EditorPanelView→MarkEditMac~Modules~SharedUI.BackgroundThemingMarkEditMac~Editor.EditorStatusView→MarkEditMac~Modules~SharedUI.BackgroundThemingMarkEditMac~Editor.EditorViewController→MarkEditMac~Modules~SharedUI.DividerViewMarkEditMac~Editor.EditorViewController→MarkEditMac~Modules~SharedUI.MaterialViewMarkEditMac~Editor.GlassButton→MarkEditMac~Modules~SharedUI.LabelView
- Direction
- MarkEditMac~Editor uses MarkEditMac~Modules~SharedUI, so a change to MarkEditMac~Modules~SharedUI can break MarkEditMac~Editor, while a change to MarkEditMac~Editor can't break MarkEditMac~Modules~SharedUI.
- Position
- Below the diagonal: MarkEditMac~Editor uses a module listed above it, which is the healthy direction.
30→25 MarkEditMac~Editor uses MarkEditMac~Modules~Statistics✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Editor uses a type in MarkEditMac~Modules~Statistics.
- The types involved
MarkEditMac~Editor.EditorViewController→MarkEditMac~Modules~Statistics.StatisticsRule
- Direction
- MarkEditMac~Editor uses MarkEditMac~Modules~Statistics, so a change to MarkEditMac~Modules~Statistics can break MarkEditMac~Editor, while a change to MarkEditMac~Editor can't break MarkEditMac~Modules~Statistics.
- Position
- Below the diagonal: MarkEditMac~Editor uses a module listed above it, which is the healthy direction.
30→26 MarkEditMac~Editor uses MarkEditMac~Extras✕
- Connections
- 4 pairs of types, where a type in MarkEditMac~Editor uses a type in MarkEditMac~Extras.
- The types involved
MarkEditMac~Editor.EditorViewController→MarkEditMac~Extras.NSMenuMarkEditMac~Editor.EditorViewController→MarkEditMac~Extras.NSSpellCheckerMarkEditMac~Editor.EditorWebView→MarkEditMac~Extras.NSMenuMarkEditMac~Editor.NSToolbarItem→MarkEditMac~Extras.NSMenu
- Direction
- MarkEditMac~Editor uses MarkEditMac~Extras, so a change to MarkEditMac~Extras can break MarkEditMac~Editor, while a change to MarkEditMac~Editor can't break MarkEditMac~Extras.
- Position
- Below the diagonal: MarkEditMac~Editor uses a module listed above it, which is the healthy direction.
30→27 MarkEditMac~Editor uses MarkEditMac~Modules~FileVersion✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Editor uses a type in MarkEditMac~Modules~FileVersion.
- The types involved
MarkEditMac~Editor.EditorDocument→MarkEditMac~Modules~FileVersion.FileVersionPicker
- Direction
- MarkEditMac~Editor uses MarkEditMac~Modules~FileVersion, so a change to MarkEditMac~Modules~FileVersion can break MarkEditMac~Editor, while a change to MarkEditMac~Editor can't break MarkEditMac~Modules~FileVersion.
- Position
- Below the diagonal: MarkEditMac~Editor uses a module listed above it, which is the healthy direction.
30→28 MarkEditMac~Editor uses MarkEditMac~Panels✕
- Connections
- 3 pairs of types, where a type in MarkEditMac~Editor uses a type in MarkEditMac~Panels.
- The types involved
MarkEditMac~Editor.EditorViewController→MarkEditMac~Panels.EditorFindModeMarkEditMac~Editor.EditorViewController→MarkEditMac~Panels.EditorFindPanelMarkEditMac~Editor.EditorViewController→MarkEditMac~Panels.EditorReplacePanel
- Direction
- MarkEditMac~Editor uses MarkEditMac~Panels, so a change to MarkEditMac~Panels can break MarkEditMac~Editor, while a change to MarkEditMac~Editor can't break MarkEditMac~Panels.
- Position
- Below the diagonal: MarkEditMac~Editor uses a module listed above it, which is the healthy direction.
30→29 MarkEditMac~Editor uses MarkEditMac~Extension✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Editor uses a type in MarkEditMac~Extension.
- The types involved
MarkEditMac~Editor.EditorViewController→MarkEditMac~Extension.IdentifierMarkEditMac~Editor.NSToolbarItem→MarkEditMac~Extension.Identifier
- Direction
- MarkEditMac~Editor uses MarkEditMac~Extension, so a change to MarkEditMac~Extension can break MarkEditMac~Editor, while a change to MarkEditMac~Editor can't break MarkEditMac~Extension.
- Position
- Below the diagonal: MarkEditMac~Editor uses a module listed above it, which is the healthy direction.
30→31 MarkEditMac~Editor uses MarkEditMac~Modules~QuickSearchUI part of a loop✕
- Connections
- 6 pairs of types, where a type in MarkEditMac~Editor uses a type in MarkEditMac~Modules~QuickSearchUI.
- The types involved
MarkEditMac~Editor.EditorViewController→MarkEditMac~Modules~QuickSearchUI.CGRectMarkEditMac~Editor.EditorViewController→MarkEditMac~Modules~QuickSearchUI.NSMenuItemMarkEditMac~Editor.EditorWebView→MarkEditMac~Modules~QuickSearchUI.NSMenuItemMarkEditMac~Editor.EditorWebViewActionDelegate→MarkEditMac~Modules~QuickSearchUI.NSMenuItemMarkEditMac~Editor.EditorWindowController→MarkEditMac~Modules~QuickSearchUI.CGRectMarkEditMac~Editor.GlassButton→MarkEditMac~Modules~QuickSearchUI.CGRect
- Direction
- MarkEditMac~Editor uses MarkEditMac~Modules~QuickSearchUI, so a change to MarkEditMac~Modules~QuickSearchUI can break MarkEditMac~Editor, while a change to MarkEditMac~Editor can't break MarkEditMac~Modules~QuickSearchUI.
- Position
- Above the diagonal, so 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→32 MarkEditMac~Editor uses MarkEditKit~Bridge part of a loop✕
- Connections
- 20 pairs of types, where a type in MarkEditMac~Editor uses a type in MarkEditKit~Bridge.
- The types involved
MarkEditMac~Editor.EditorDocument→MarkEditKit~Bridge.LineEndingsMarkEditMac~Editor.EditorDocument→MarkEditKit~Bridge.WebModuleBridgeMarkEditMac~Editor.EditorMenuItem→MarkEditKit~Bridge.WebMenuItemMarkEditMac~Editor.EditorSelectionHistory→MarkEditKit~Bridge.LineColumnInfoMarkEditMac~Editor.EditorStatusView→MarkEditKit~Bridge.LineColumnInfoMarkEditMac~Editor.EditorViewController→MarkEditKit~Bridge.EditorModuleAPIMarkEditMac~Editor.EditorViewController→MarkEditKit~Bridge.EditorModuleCompletionMarkEditMac~Editor.EditorViewController→MarkEditKit~Bridge.EditorModuleCoreMarkEditMac~Editor.EditorViewController→MarkEditKit~Bridge.EditorModuleFoundationModelsMarkEditMac~Editor.EditorViewController→MarkEditKit~Bridge.HeadingInfoMarkEditMac~Editor.EditorViewController→MarkEditKit~Bridge.LanguageModelResponseMarkEditMac~Editor.EditorViewController→MarkEditKit~Bridge.LineColumnInfoMarkEditMac~Editor.EditorViewController→MarkEditKit~Bridge.NativeModuleCoreNotifyWindowMoveMethodMarkEditMac~Editor.EditorViewController→MarkEditKit~Bridge.NativeModuleCoreNotifyWindowResizeMethodMarkEditMac~Editor.EditorViewController→MarkEditKit~Bridge.SearchCounterInfoMarkEditMac~Editor.EditorViewController→MarkEditKit~Bridge.SearchOperationMarkEditMac~Editor.EditorViewController→MarkEditKit~Bridge.TabKeyBehaviorMarkEditMac~Editor.EditorViewController→MarkEditKit~Bridge.WebMenuItemMarkEditMac~Editor.EditorViewController→MarkEditKit~Bridge.WebModuleBridgeMarkEditMac~Editor.EditorViewController→MarkEditKit~Bridge.WebPoint
- Direction
- MarkEditMac~Editor uses MarkEditKit~Bridge, so a change to MarkEditKit~Bridge can break MarkEditMac~Editor, while a change to MarkEditMac~Editor can't break MarkEditKit~Bridge.
- Position
- Above the diagonal, so 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→33 MarkEditMac~Editor uses MarkEditKit part of a loop✕
- Connections
- 4 pairs of types, where a type in MarkEditMac~Editor uses a type in MarkEditKit.
- The types involved
MarkEditMac~Editor.ClosedTab→MarkEditKit.DataMarkEditMac~Editor.EditorDocument→MarkEditKit.DataMarkEditMac~Editor.EditorDocument→MarkEditKit.EditorTextEncodingMarkEditMac~Editor.EditorViewController→MarkEditKit.Data
- Direction
- MarkEditMac~Editor uses MarkEditKit, so a change to MarkEditKit can break MarkEditMac~Editor, while a change to MarkEditMac~Editor can't break MarkEditKit.
- Position
- Above the diagonal, so 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→34 MarkEditMac~Editor uses MarkEditCore~Extensions part of a loop✕
- Connections
- 16 pairs of types, where a type in MarkEditMac~Editor uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditMac~Editor.ClosedTab→MarkEditCore~Extensions.StringMarkEditMac~Editor.ClosedTab→MarkEditCore~Extensions.URLMarkEditMac~Editor.EditorClosedTabHistory→MarkEditCore~Extensions.URLMarkEditMac~Editor.EditorDocument→MarkEditCore~Extensions.StringMarkEditMac~Editor.EditorDocument→MarkEditCore~Extensions.URLMarkEditMac~Editor.EditorMenuItem→MarkEditCore~Extensions.StringMarkEditMac~Editor.EditorSelectionHistory→MarkEditCore~Extensions.URLMarkEditMac~Editor.EditorStatusView→MarkEditCore~Extensions.StringMarkEditMac~Editor.EditorViewController→MarkEditCore~Extensions.StringMarkEditMac~Editor.EditorViewController→MarkEditCore~Extensions.URLMarkEditMac~Editor.EditorViewController→MarkEditCore~Extensions.WKWebViewMarkEditMac~Editor.EditorWebView→MarkEditCore~Extensions.URLMarkEditMac~Editor.EditorWebView→MarkEditCore~Extensions.WKWebViewMarkEditMac~Editor.EditorWebViewActionDelegate→MarkEditCore~Extensions.URLMarkEditMac~Editor.NSToolbarItem→MarkEditCore~Extensions.StringMarkEditMac~Editor.RestoredTab→MarkEditCore~Extensions.URL
- Direction
- MarkEditMac~Editor uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Editor, while a change to MarkEditMac~Editor can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so 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→35 MarkEditMac~Editor uses MarkEditCore part of a loop✕
- Connections
- 5 pairs of types, where a type in MarkEditMac~Editor uses a type in MarkEditCore.
- The types involved
MarkEditMac~Editor.EditorSelectionHistory→MarkEditCore.SelectionRangeMarkEditMac~Editor.EditorViewController→MarkEditCore.EditorInvisiblesBehaviorMarkEditMac~Editor.EditorViewController→MarkEditCore.TextTokenizeAnchorMarkEditMac~Editor.EditorViewController→MarkEditCore.WebFontFaceMarkEditMac~Editor.SelectionRangeEntry→MarkEditCore.SelectionRange
- Direction
- MarkEditMac~Editor uses MarkEditCore, so a change to MarkEditCore can break MarkEditMac~Editor, while a change to MarkEditMac~Editor can't break MarkEditCore.
- Position
- Above the diagonal, so 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→11 MarkEditMac~Modules~QuickSearchUI uses MarkEditKit~Extensions✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Modules~QuickSearchUI uses a type in MarkEditKit~Extensions.
- The types involved
MarkEditMac~Modules~QuickSearchUI.QuickSearchController→MarkEditKit~Extensions.NSObject
- Direction
- MarkEditMac~Modules~QuickSearchUI uses MarkEditKit~Extensions, so a change to MarkEditKit~Extensions can break MarkEditMac~Modules~QuickSearchUI, while a change to MarkEditMac~Modules~QuickSearchUI can't break MarkEditKit~Extensions.
- Position
- Below the diagonal: MarkEditMac~Modules~QuickSearchUI uses a module listed above it, which is the healthy direction.
31→13 MarkEditMac~Modules~QuickSearchUI uses MarkEditMac~Modules~QuickSearchCore✕
- Connections
- 9 pairs of types, where a type in MarkEditMac~Modules~QuickSearchUI uses a type in MarkEditMac~Modules~QuickSearchCore.
- The types involved
MarkEditMac~Modules~QuickSearchUI.CachedResults→MarkEditMac~Modules~QuickSearchCore.QuickSearchDocumentSnapshotMarkEditMac~Modules~QuickSearchUI.CachedResults→MarkEditMac~Modules~QuickSearchCore.QuickSearchFilterMarkEditMac~Modules~QuickSearchUI.CachedResults→MarkEditMac~Modules~QuickSearchCore.QuickSearchResultMarkEditMac~Modules~QuickSearchUI.QuickSearchController→MarkEditMac~Modules~QuickSearchCore.BatchMarkEditMac~Modules~QuickSearchUI.QuickSearchController→MarkEditMac~Modules~QuickSearchCore.QuickSearchDocumentSnapshotMarkEditMac~Modules~QuickSearchUI.QuickSearchController→MarkEditMac~Modules~QuickSearchCore.QuickSearchFilterMarkEditMac~Modules~QuickSearchUI.QuickSearchController→MarkEditMac~Modules~QuickSearchCore.QuickSearchLocationsMarkEditMac~Modules~QuickSearchUI.QuickSearchController→MarkEditMac~Modules~QuickSearchCore.QuickSearchResultMarkEditMac~Modules~QuickSearchUI.QuickSearchMenuActions→MarkEditMac~Modules~QuickSearchCore.Action
- Direction
- MarkEditMac~Modules~QuickSearchUI uses MarkEditMac~Modules~QuickSearchCore, so a change to MarkEditMac~Modules~QuickSearchCore can break MarkEditMac~Modules~QuickSearchUI, while a change to MarkEditMac~Modules~QuickSearchUI can't break MarkEditMac~Modules~QuickSearchCore.
- Position
- Below the diagonal: MarkEditMac~Modules~QuickSearchUI uses a module listed above it, which is the healthy direction.
31→17 MarkEditMac~Modules~QuickSearchUI uses repository✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Modules~QuickSearchUI uses a type in repository.
- The types involved
MarkEditMac~Modules~QuickSearchUI.QuickSearchDocumentError→repository.Error
- Direction
- MarkEditMac~Modules~QuickSearchUI uses repository, so a change to repository can break MarkEditMac~Modules~QuickSearchUI, while a change to MarkEditMac~Modules~QuickSearchUI can't break repository.
- Position
- Below the diagonal: MarkEditMac~Modules~QuickSearchUI uses a module listed above it, which is the healthy direction.
31→20 MarkEditMac~Modules~QuickSearchUI uses MarkEditMac~Scripting✕
- Connections
- 4 pairs of types, where a type in MarkEditMac~Modules~QuickSearchUI uses a type in MarkEditMac~Scripting.
- The types involved
MarkEditMac~Modules~QuickSearchUI.QuickSearchController→MarkEditMac~Scripting.NSColorMarkEditMac~Modules~QuickSearchUI.QuickSearchItem→MarkEditMac~Scripting.NSColorMarkEditMac~Modules~QuickSearchUI.QuickSearchView→MarkEditMac~Scripting.NSColorMarkEditMac~Modules~QuickSearchUI.QuickSearchWindow→MarkEditMac~Scripting.NSColor
- Direction
- MarkEditMac~Modules~QuickSearchUI uses MarkEditMac~Scripting, so a change to MarkEditMac~Scripting can break MarkEditMac~Modules~QuickSearchUI, while a change to MarkEditMac~Modules~QuickSearchUI can't break MarkEditMac~Scripting.
- Position
- Below the diagonal: MarkEditMac~Modules~QuickSearchUI uses a module listed above it, which is the healthy direction.
31→21 MarkEditMac~Modules~QuickSearchUI uses MarkEditMac~Modules~TextCompletion✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Modules~QuickSearchUI uses a type in MarkEditMac~Modules~TextCompletion.
- The types involved
MarkEditMac~Modules~QuickSearchUI.QuickSearchController→MarkEditMac~Modules~TextCompletion.NSScreen
- Direction
- MarkEditMac~Modules~QuickSearchUI uses MarkEditMac~Modules~TextCompletion, so a change to MarkEditMac~Modules~TextCompletion can break MarkEditMac~Modules~QuickSearchUI, while a change to MarkEditMac~Modules~QuickSearchUI can't break MarkEditMac~Modules~TextCompletion.
- Position
- Below the diagonal: MarkEditMac~Modules~QuickSearchUI uses a module listed above it, which is the healthy direction.
31→22 MarkEditMac~Modules~QuickSearchUI uses MarkEditMac~Modules~AppKitExtensions✕
- Connections
- 15 pairs of types, where a type in MarkEditMac~Modules~QuickSearchUI uses a type in MarkEditMac~Modules~AppKitExtensions.
- The types involved
MarkEditMac~Modules~QuickSearchUI.QuickSearchController→MarkEditMac~Modules~AppKitExtensions.NSAppearanceMarkEditMac~Modules~QuickSearchUI.QuickSearchMenuActions→MarkEditMac~Modules~AppKitExtensions.NSWindowMarkEditMac~Modules~QuickSearchUI.QuickSearchResultsView→MarkEditMac~Modules~AppKitExtensions.NSScrollViewMarkEditMac~Modules~QuickSearchUI.QuickSearchResultsView→MarkEditMac~Modules~AppKitExtensions.NSTableViewMarkEditMac~Modules~QuickSearchUI.QuickSearchResultsView→MarkEditMac~Modules~AppKitExtensions.NSTextFieldMarkEditMac~Modules~QuickSearchUI.QuickSearchResultsView→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Modules~QuickSearchUI.QuickSearchView→MarkEditMac~Modules~AppKitExtensions.NSEventMarkEditMac~Modules~QuickSearchUI.QuickSearchView→MarkEditMac~Modules~AppKitExtensions.NSTextFieldMarkEditMac~Modules~QuickSearchUI.QuickSearchView→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Modules~QuickSearchUI.QuickSearchWindow→MarkEditMac~Modules~AppKitExtensions.NSEventMarkEditMac~Modules~QuickSearchUI.QuickSearchWindow→MarkEditMac~Modules~AppKitExtensions.NSWindowMarkEditMac~Modules~QuickSearchUI.ResultCell→MarkEditMac~Modules~AppKitExtensions.NSTextFieldMarkEditMac~Modules~QuickSearchUI.ResultCell→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Modules~QuickSearchUI.ResultRow→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Modules~QuickSearchUI.ResultsTableView→MarkEditMac~Modules~AppKitExtensions.NSTableView
- Direction
- MarkEditMac~Modules~QuickSearchUI uses MarkEditMac~Modules~AppKitExtensions, so a change to MarkEditMac~Modules~AppKitExtensions can break MarkEditMac~Modules~QuickSearchUI, while a change to MarkEditMac~Modules~QuickSearchUI can't break MarkEditMac~Modules~AppKitExtensions.
- Position
- Below the diagonal: MarkEditMac~Modules~QuickSearchUI uses a module listed above it, which is the healthy direction.
31→23 MarkEditMac~Modules~QuickSearchUI uses MarkEditMac~Main✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Modules~QuickSearchUI uses a type in MarkEditMac~Main.
- The types involved
MarkEditMac~Modules~QuickSearchUI.OpenPanelShortcut→MarkEditMac~Main.NSOpenPanelMarkEditMac~Modules~QuickSearchUI.QuickSearchController→MarkEditMac~Main.NSOpenPanel
- Direction
- MarkEditMac~Modules~QuickSearchUI uses MarkEditMac~Main, so a change to MarkEditMac~Main can break MarkEditMac~Modules~QuickSearchUI, while a change to MarkEditMac~Modules~QuickSearchUI can't break MarkEditMac~Main.
- Position
- Below the diagonal: MarkEditMac~Modules~QuickSearchUI uses a module listed above it, which is the healthy direction.
31→26 MarkEditMac~Modules~QuickSearchUI uses MarkEditMac~Extras✕
- Connections
- 4 pairs of types, where a type in MarkEditMac~Modules~QuickSearchUI uses a type in MarkEditMac~Extras.
- The types involved
MarkEditMac~Modules~QuickSearchUI.QuickSearchController→MarkEditMac~Extras.NSMenuMarkEditMac~Modules~QuickSearchUI.QuickSearchMenuActions→MarkEditMac~Extras.NSMenuMarkEditMac~Modules~QuickSearchUI.QuickSearchResultsConfiguration→MarkEditMac~Extras.NSMenuMarkEditMac~Modules~QuickSearchUI.QuickSearchView→MarkEditMac~Extras.NSMenu
- Direction
- MarkEditMac~Modules~QuickSearchUI uses MarkEditMac~Extras, so a change to MarkEditMac~Extras can break MarkEditMac~Modules~QuickSearchUI, while a change to MarkEditMac~Modules~QuickSearchUI can't break MarkEditMac~Extras.
- Position
- Below the diagonal: MarkEditMac~Modules~QuickSearchUI uses a module listed above it, which is the healthy direction.
31→30 MarkEditMac~Modules~QuickSearchUI uses MarkEditMac~Editor✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Modules~QuickSearchUI uses a type in MarkEditMac~Editor.
- The types involved
MarkEditMac~Modules~QuickSearchUI.NSMenuItem→MarkEditMac~Editor.WKContextMenuItemTag
- Direction
- MarkEditMac~Modules~QuickSearchUI uses MarkEditMac~Editor, so a change to MarkEditMac~Editor can break MarkEditMac~Modules~QuickSearchUI, while a change to MarkEditMac~Modules~QuickSearchUI can't break MarkEditMac~Editor.
- Position
- Below the diagonal: MarkEditMac~Modules~QuickSearchUI uses a module listed above it, which is the healthy direction.
31→34 MarkEditMac~Modules~QuickSearchUI uses MarkEditCore~Extensions part of a loop✕
- Connections
- 13 pairs of types, where a type in MarkEditMac~Modules~QuickSearchUI uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditMac~Modules~QuickSearchUI.CachedResults→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchUI.NSMenuItem→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchUI.QuickSearchController→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchUI.QuickSearchController→MarkEditCore~Extensions.URLMarkEditMac~Modules~QuickSearchUI.QuickSearchDocument→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchUI.QuickSearchDocument→MarkEditCore~Extensions.URLMarkEditMac~Modules~QuickSearchUI.QuickSearchFilterLabels→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchUI.QuickSearchItem→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchUI.QuickSearchMenuActions→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchUI.QuickSearchResultsView→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchUI.QuickSearchView→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchUI.QuickSearchWindow→MarkEditCore~Extensions.StringMarkEditMac~Modules~QuickSearchUI.ResultCell→MarkEditCore~Extensions.String
- Direction
- MarkEditMac~Modules~QuickSearchUI uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Modules~QuickSearchUI, while a change to MarkEditMac~Modules~QuickSearchUI can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so 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→11 MarkEditKit~Bridge uses MarkEditKit~Extensions✕
- Connections
- 2 pairs of types, where a type in MarkEditKit~Bridge uses a type in MarkEditKit~Extensions.
- The types involved
MarkEditKit~Bridge.EditorModuleAPI→MarkEditKit~Extensions.NSFileVersionMarkEditKit~Bridge.FileVersionKey→MarkEditKit~Extensions.NSFileVersion
- Direction
- MarkEditKit~Bridge uses MarkEditKit~Extensions, so a change to MarkEditKit~Extensions can break MarkEditKit~Bridge, while a change to MarkEditKit~Bridge can't break MarkEditKit~Extensions.
- Position
- Below the diagonal: MarkEditKit~Bridge uses a module listed above it, which is the healthy direction.
32→14 MarkEditKit~Bridge uses UpdateInstaller~UpdaterCore✕
- Connections
- 2 pairs of types, where a type in MarkEditKit~Bridge uses a type in UpdateInstaller~UpdaterCore.
- The types involved
MarkEditKit~Bridge.EditorModuleTokenizer→UpdateInstaller~UpdaterCore.[String: Any]MarkEditKit~Bridge.NativeModuleTokenizer→UpdateInstaller~UpdaterCore.[String: Any]
- Direction
- MarkEditKit~Bridge uses UpdateInstaller~UpdaterCore, so a change to UpdateInstaller~UpdaterCore can break MarkEditKit~Bridge, while a change to MarkEditKit~Bridge can't break UpdateInstaller~UpdaterCore.
- Position
- Below the diagonal: MarkEditKit~Bridge uses a module listed above it, which is the healthy direction.
32→25 MarkEditKit~Bridge uses MarkEditMac~Modules~Statistics✕
- Connections
- 1 pair of types, where a type in MarkEditKit~Bridge uses a type in MarkEditMac~Modules~Statistics.
- The types involved
MarkEditKit~Bridge.ReadableContent→MarkEditMac~Modules~Statistics.StatisticsResult
- Direction
- MarkEditKit~Bridge uses MarkEditMac~Modules~Statistics, so a change to MarkEditMac~Modules~Statistics can break MarkEditKit~Bridge, while a change to MarkEditKit~Bridge can't break MarkEditMac~Modules~Statistics.
- Position
- Below the diagonal: MarkEditKit~Bridge uses a module listed above it, which is the healthy direction.
32→31 MarkEditKit~Bridge uses MarkEditMac~Modules~QuickSearchUI✕
- Connections
- 1 pair of types, where a type in MarkEditKit~Bridge uses a type in MarkEditMac~Modules~QuickSearchUI.
- The types involved
MarkEditKit~Bridge.WebRect→MarkEditMac~Modules~QuickSearchUI.CGRect
- Direction
- MarkEditKit~Bridge uses MarkEditMac~Modules~QuickSearchUI, so a change to MarkEditMac~Modules~QuickSearchUI can break MarkEditKit~Bridge, while a change to MarkEditKit~Bridge can't break MarkEditMac~Modules~QuickSearchUI.
- Position
- Below the diagonal: MarkEditKit~Bridge uses a module listed above it, which is the healthy direction.
32→33 MarkEditKit~Bridge uses MarkEditKit part of a loop✕
- Connections
- 12 pairs of types, where a type in MarkEditKit~Bridge uses a type in MarkEditKit.
- The types involved
MarkEditKit~Bridge.EditorModuleAPIDelegate→MarkEditKit.DataMarkEditKit~Bridge.EditorModuleSecretStorage→MarkEditKit.KeychainSecretStorageMarkEditKit~Bridge.FileVersionKey→MarkEditKit.DataMarkEditKit~Bridge.NativeBridge→MarkEditKit.DataMarkEditKit~Bridge.NativeBridgeAPI→MarkEditKit.DataMarkEditKit~Bridge.NativeBridgeCompletion→MarkEditKit.DataMarkEditKit~Bridge.NativeBridgeCore→MarkEditKit.DataMarkEditKit~Bridge.NativeBridgeFoundationModels→MarkEditKit.DataMarkEditKit~Bridge.NativeBridgeSecretStorage→MarkEditKit.DataMarkEditKit~Bridge.NativeBridgeTokenizer→MarkEditKit.DataMarkEditKit~Bridge.NativeBridgeTranslation→MarkEditKit.DataMarkEditKit~Bridge.WebDataTransfer→MarkEditKit.Data
- Direction
- MarkEditKit~Bridge uses MarkEditKit, so a change to MarkEditKit can break MarkEditKit~Bridge, while a change to MarkEditKit~Bridge can't break MarkEditKit.
- Position
- Above the diagonal, so 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→34 MarkEditKit~Bridge uses MarkEditCore~Extensions part of a loop✕
- Connections
- 78 pairs of types, where a type in MarkEditKit~Bridge uses a type in MarkEditCore~Extensions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
MarkEditKit~Bridge.CIImage→MarkEditCore~Extensions.StringMarkEditKit~Bridge.Context→MarkEditCore~Extensions.StringMarkEditKit~Bridge.CreateFileOptions→MarkEditCore~Extensions.StringMarkEditKit~Bridge.DocumentOutline→MarkEditCore~Extensions.StringMarkEditKit~Bridge.EditCommand→MarkEditCore~Extensions.StringMarkEditKit~Bridge.EditorModuleAPI→MarkEditCore~Extensions.StringMarkEditKit~Bridge.EditorModuleAPI→MarkEditCore~Extensions.URLMarkEditKit~Bridge.EditorModuleAPIDelegate→MarkEditCore~Extensions.StringMarkEditKit~Bridge.EditorModuleAPIDelegate→MarkEditCore~Extensions.URLMarkEditKit~Bridge.EditorModuleCompletion→MarkEditCore~Extensions.StringMarkEditKit~Bridge.EditorModuleCompletionDelegate→MarkEditCore~Extensions.StringMarkEditKit~Bridge.EditorModuleCore→MarkEditCore~Extensions.StringMarkEditKit~Bridge.EditorModuleCoreDelegate→MarkEditCore~Extensions.StringMarkEditKit~Bridge.EditorModuleFoundationModels→MarkEditCore~Extensions.StringMarkEditKit~Bridge.EditorModuleFoundationModelsDelegate→MarkEditCore~Extensions.StringMarkEditKit~Bridge.EditorModuleSecretStorage→MarkEditCore~Extensions.StringMarkEditKit~Bridge.EditorModuleSecretStorageDelegate→MarkEditCore~Extensions.StringMarkEditKit~Bridge.EditorModuleTokenizer→MarkEditCore~Extensions.StringMarkEditKit~Bridge.EditorModuleTranslation→MarkEditCore~Extensions.StringMarkEditKit~Bridge.FileManager→MarkEditCore~Extensions.URLMarkEditKit~Bridge.HeadingInfo→MarkEditCore~Extensions.StringMarkEditKit~Bridge.LanguageModelAvailability→MarkEditCore~Extensions.StringMarkEditKit~Bridge.LanguageModelGenerationOptions→MarkEditCore~Extensions.StringMarkEditKit~Bridge.LanguageModelResponse→MarkEditCore~Extensions.StringMarkEditKit~Bridge.LineColumnInfo→MarkEditCore~Extensions.String
- Direction
- MarkEditKit~Bridge uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditKit~Bridge, while a change to MarkEditKit~Bridge can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so 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→35 MarkEditKit~Bridge uses MarkEditCore part of a loop✕
- Connections
- 12 pairs of types, where a type in MarkEditKit~Bridge uses a type in MarkEditCore.
- The types involved
MarkEditKit~Bridge.EditorModuleCompletion→MarkEditCore.TextTokenizeAnchorMarkEditKit~Bridge.EditorModuleCompletionDelegate→MarkEditCore.TextTokenizeAnchorMarkEditKit~Bridge.EditorModuleTokenizer→MarkEditCore.TextTokenizeAnchorMarkEditKit~Bridge.LineColumnInfo→MarkEditCore.SelectionRangeMarkEditKit~Bridge.NativeModuleCompletion→MarkEditCore.TextTokenizeAnchorMarkEditKit~Bridge.NativeModuleTokenizer→MarkEditCore.TextTokenizeAnchorMarkEditKit~Bridge.WebBridgeConfig→MarkEditCore.EditorInvisiblesBehaviorMarkEditKit~Bridge.WebBridgeConfig→MarkEditCore.WebFontFaceMarkEditKit~Bridge.WebBridgeCore→MarkEditCore.SelectionRangeMarkEditKit~Bridge.WebBridgeDummy→MarkEditCore.EditorHostMarkEditKit~Bridge.WebBridgeDummy→MarkEditCore.EditorIndentBehaviorMarkEditKit~Bridge.WebBridgeDummy→MarkEditCore.RuntimeInfo
- Direction
- MarkEditKit~Bridge uses MarkEditCore, so a change to MarkEditCore can break MarkEditKit~Bridge, while a change to MarkEditKit~Bridge can't break MarkEditCore.
- Position
- Above the diagonal, so 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→11 MarkEditKit uses MarkEditKit~Extensions✕
- Connections
- 1 pair of types, where a type in MarkEditKit uses a type in MarkEditKit~Extensions.
- The types involved
MarkEditKit.EditorMessageHandler→MarkEditKit~Extensions.NSObject
- Direction
- MarkEditKit uses MarkEditKit~Extensions, so a change to MarkEditKit~Extensions can break MarkEditKit, while a change to MarkEditKit can't break MarkEditKit~Extensions.
- Position
- Below the diagonal: MarkEditKit uses a module listed above it, which is the healthy direction.
33→14 MarkEditKit uses UpdateInstaller~UpdaterCore✕
- Connections
- 3 pairs of types, where a type in MarkEditKit uses a type in UpdateInstaller~UpdaterCore.
- The types involved
MarkEditKit.KeychainSecretStorage→UpdateInstaller~UpdaterCore.[String: Any]MarkEditKit.SecretKeychain→UpdateInstaller~UpdaterCore.[String: Any]MarkEditKit.SystemSecretKeychain→UpdateInstaller~UpdaterCore.[String: Any]
- Direction
- MarkEditKit uses UpdateInstaller~UpdaterCore, so a change to UpdateInstaller~UpdaterCore can break MarkEditKit, while a change to MarkEditKit can't break UpdateInstaller~UpdaterCore.
- Position
- Below the diagonal: MarkEditKit uses a module listed above it, which is the healthy direction.
33→32 MarkEditKit uses MarkEditKit~Bridge✕
- Connections
- 1 pair of types, where a type in MarkEditKit uses a type in MarkEditKit~Bridge.
- The types involved
MarkEditKit.EditorMessageHandler→MarkEditKit~Bridge.NativeModules
- Direction
- MarkEditKit uses MarkEditKit~Bridge, so a change to MarkEditKit~Bridge can break MarkEditKit, while a change to MarkEditKit can't break MarkEditKit~Bridge.
- Position
- Below the diagonal: MarkEditKit uses a module listed above it, which is the healthy direction.
33→34 MarkEditKit uses MarkEditCore~Extensions part of a loop✕
- Connections
- 6 pairs of types, where a type in MarkEditKit uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditKit.Data→MarkEditCore~Extensions.EncodingMarkEditKit.Data→MarkEditCore~Extensions.StringMarkEditKit.Data→MarkEditCore~Extensions.URLMarkEditKit.EditorTextEncoding→MarkEditCore~Extensions.StringMarkEditKit.KeychainSecretStorage→MarkEditCore~Extensions.StringMarkEditKit.SecretStorageError→MarkEditCore~Extensions.String
- Direction
- MarkEditKit uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditKit, while a change to MarkEditKit can't break MarkEditCore~Extensions.
- Position
- Above the diagonal, so 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→35 MarkEditKit uses MarkEditCore part of a loop✕
- Connections
- 1 pair of types, where a type in MarkEditKit uses a type in MarkEditCore.
- The types involved
MarkEditKit.EditorTextEncoding→MarkEditCore.CompactCodableEnum
- Direction
- MarkEditKit uses MarkEditCore, so a change to MarkEditCore can break MarkEditKit, while a change to MarkEditKit can't break MarkEditCore.
- Position
- Above the diagonal, so 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→11 MarkEditCore~Extensions uses MarkEditKit~Extensions✕
- Connections
- 1 pair of types, where a type in MarkEditCore~Extensions uses a type in MarkEditKit~Extensions.
- The types involved
MarkEditCore~Extensions.WebKitConfigSPI→MarkEditKit~Extensions.NSObject
- Direction
- MarkEditCore~Extensions uses MarkEditKit~Extensions, so a change to MarkEditKit~Extensions can break MarkEditCore~Extensions, while a change to MarkEditCore~Extensions can't break MarkEditKit~Extensions.
- Position
- Below the diagonal: MarkEditCore~Extensions uses a module listed above it, which is the healthy direction.
34→33 MarkEditCore~Extensions uses MarkEditKit✕
- Connections
- 2 pairs of types, where a type in MarkEditCore~Extensions uses a type in MarkEditKit.
- The types involved
MarkEditCore~Extensions.String→MarkEditKit.DataMarkEditCore~Extensions.URL→MarkEditKit.Data
- Direction
- MarkEditCore~Extensions uses MarkEditKit, so a change to MarkEditKit can break MarkEditCore~Extensions, while a change to MarkEditCore~Extensions can't break MarkEditKit.
- Position
- Below the diagonal: MarkEditCore~Extensions uses a module listed above it, which is the healthy direction.
35→11 MarkEditCore uses MarkEditKit~Extensions✕
- Connections
- 1 pair of types, where a type in MarkEditCore uses a type in MarkEditKit~Extensions.
- The types involved
MarkEditCore.EditorImageLoader→MarkEditKit~Extensions.NSObject
- Direction
- MarkEditCore uses MarkEditKit~Extensions, so a change to MarkEditKit~Extensions can break MarkEditCore, while a change to MarkEditCore can't break MarkEditKit~Extensions.
- Position
- Below the diagonal: MarkEditCore uses a module listed above it, which is the healthy direction.
35→33 MarkEditCore uses MarkEditKit✕
- Connections
- 2 pairs of types, where a type in MarkEditCore uses a type in MarkEditKit.
- The types involved
MarkEditCore.EditorConfig→MarkEditKit.DataMarkEditCore.EditorIndexHtml→MarkEditKit.Data
- Direction
- MarkEditCore uses MarkEditKit, so a change to MarkEditKit can break MarkEditCore, while a change to MarkEditCore can't break MarkEditKit.
- Position
- Below the diagonal: MarkEditCore uses a module listed above it, which is the healthy direction.
35→34 MarkEditCore uses MarkEditCore~Extensions✕
- Connections
- 22 pairs of types, where a type in MarkEditCore uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditCore.BridgeFieldKey→MarkEditCore~Extensions.StringMarkEditCore.BridgeMessage→MarkEditCore~Extensions.EncodableMarkEditCore.CaseNameCodingKey→MarkEditCore~Extensions.StringMarkEditCore.EditorConfig→MarkEditCore~Extensions.EncodableMarkEditCore.EditorConfig→MarkEditCore~Extensions.StringMarkEditCore.EditorHost→MarkEditCore~Extensions.StringMarkEditCore.EditorImageLoader→MarkEditCore~Extensions.StringMarkEditCore.EditorImageLoader→MarkEditCore~Extensions.WKWebViewMarkEditCore.EditorIndentBehavior→MarkEditCore~Extensions.StringMarkEditCore.EditorIndexHtml→MarkEditCore~Extensions.StringMarkEditCore.EditorIndexHtml→MarkEditCore~Extensions.URLMarkEditCore.EditorInvisiblesBehavior→MarkEditCore~Extensions.StringMarkEditCore.EditorLocalizable→MarkEditCore~Extensions.EncodableMarkEditCore.EditorLocalizable→MarkEditCore~Extensions.StringMarkEditCore.EditorUserAsset→MarkEditCore~Extensions.StringMarkEditCore.EditorUserAsset→MarkEditCore~Extensions.URLMarkEditCore.KeyedDecodingContainer→MarkEditCore~Extensions.StringMarkEditCore.KeyedEncodingContainer→MarkEditCore~Extensions.EncodableMarkEditCore.KeyedEncodingContainer→MarkEditCore~Extensions.StringMarkEditCore.RuntimeInfo→MarkEditCore~Extensions.StringMarkEditCore.TextTokenizeAnchor→MarkEditCore~Extensions.StringMarkEditCore.WebFontFace→MarkEditCore~Extensions.String
- Direction
- MarkEditCore uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditCore, while a change to MarkEditCore can't break MarkEditCore~Extensions.
- Position
- Below the diagonal: MarkEditCore uses a module listed above it, which is the healthy direction.
36→20 MarkEditMac~Modules~DiffKit uses MarkEditMac~Scripting✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Modules~DiffKit uses a type in MarkEditMac~Scripting.
- The types involved
MarkEditMac~Modules~DiffKit.Result→MarkEditMac~Scripting.NSColor
- Direction
- MarkEditMac~Modules~DiffKit uses MarkEditMac~Scripting, so a change to MarkEditMac~Scripting can break MarkEditMac~Modules~DiffKit, while a change to MarkEditMac~Modules~DiffKit can't break MarkEditMac~Scripting.
- Position
- Below the diagonal: MarkEditMac~Modules~DiffKit uses a module listed above it, which is the healthy direction.
36→34 MarkEditMac~Modules~DiffKit uses MarkEditCore~Extensions✕
- Connections
- 3 pairs of types, where a type in MarkEditMac~Modules~DiffKit uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditMac~Modules~DiffKit.Diff→MarkEditCore~Extensions.StringMarkEditMac~Modules~DiffKit.Mode→MarkEditCore~Extensions.StringMarkEditMac~Modules~DiffKit.Result→MarkEditCore~Extensions.String
- Direction
- MarkEditMac~Modules~DiffKit uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Modules~DiffKit, while a change to MarkEditMac~Modules~DiffKit can't break MarkEditCore~Extensions.
- Position
- Below the diagonal: MarkEditMac~Modules~DiffKit uses a module listed above it, which is the healthy direction.
37→12 MarkEditMac~Modules~SettingsUI uses MarkEditMac~Modules~FontPicker✕
- Connections
- 4 pairs of types, where a type in MarkEditMac~Modules~SettingsUI uses a type in MarkEditMac~Modules~FontPicker.
- The types involved
MarkEditMac~Modules~SettingsUI.Builder→MarkEditMac~Modules~FontPicker.ViewMarkEditMac~Modules~SettingsUI.FlexibleButtonSize→MarkEditMac~Modules~FontPicker.ViewMarkEditMac~Modules~SettingsUI.SettingsForm→MarkEditMac~Modules~FontPicker.ViewMarkEditMac~Modules~SettingsUI.SettingsTabViewController→MarkEditMac~Modules~FontPicker.View
- Direction
- MarkEditMac~Modules~SettingsUI uses MarkEditMac~Modules~FontPicker, so a change to MarkEditMac~Modules~FontPicker can break MarkEditMac~Modules~SettingsUI, while a change to MarkEditMac~Modules~SettingsUI can't break MarkEditMac~Modules~FontPicker.
- Position
- Below the diagonal: MarkEditMac~Modules~SettingsUI uses a module listed above it, which is the healthy direction.
37→22 MarkEditMac~Modules~SettingsUI uses MarkEditMac~Modules~AppKitExtensions✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Modules~SettingsUI uses a type in MarkEditMac~Modules~AppKitExtensions.
- The types involved
MarkEditMac~Modules~SettingsUI.SettingsTabViewController→MarkEditMac~Modules~AppKitExtensions.NSViewMarkEditMac~Modules~SettingsUI.SettingsTabViewController→MarkEditMac~Modules~AppKitExtensions.NSViewController
- Direction
- MarkEditMac~Modules~SettingsUI uses MarkEditMac~Modules~AppKitExtensions, so a change to MarkEditMac~Modules~AppKitExtensions can break MarkEditMac~Modules~SettingsUI, while a change to MarkEditMac~Modules~SettingsUI can't break MarkEditMac~Modules~AppKitExtensions.
- Position
- Below the diagonal: MarkEditMac~Modules~SettingsUI uses a module listed above it, which is the healthy direction.
37→34 MarkEditMac~Modules~SettingsUI uses MarkEditCore~Extensions✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Modules~SettingsUI uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditMac~Modules~SettingsUI.SettingsTabViewController→MarkEditCore~Extensions.String
- Direction
- MarkEditMac~Modules~SettingsUI uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Modules~SettingsUI, while a change to MarkEditMac~Modules~SettingsUI can't break MarkEditCore~Extensions.
- Position
- Below the diagonal: MarkEditMac~Modules~SettingsUI uses a module listed above it, which is the healthy direction.
38→12 MarkEditMac~Settings uses MarkEditMac~Modules~FontPicker✕
- Connections
- 6 pairs of types, where a type in MarkEditMac~Settings uses a type in MarkEditMac~Modules~FontPicker.
- The types involved
MarkEditMac~Settings.AssistantSettingsView→MarkEditMac~Modules~FontPicker.ViewMarkEditMac~Settings.EditorSettingsView→MarkEditMac~Modules~FontPicker.FontPickerConfigurationMarkEditMac~Settings.EditorSettingsView→MarkEditMac~Modules~FontPicker.FontPickerHandlersMarkEditMac~Settings.EditorSettingsView→MarkEditMac~Modules~FontPicker.ViewMarkEditMac~Settings.GeneralSettingsView→MarkEditMac~Modules~FontPicker.ViewMarkEditMac~Settings.WindowSettingsView→MarkEditMac~Modules~FontPicker.View
- Direction
- MarkEditMac~Settings uses MarkEditMac~Modules~FontPicker, so a change to MarkEditMac~Modules~FontPicker can break MarkEditMac~Settings, while a change to MarkEditMac~Settings can't break MarkEditMac~Modules~FontPicker.
- Position
- Below the diagonal: MarkEditMac~Settings uses a module listed above it, which is the healthy direction.
38→22 MarkEditMac~Settings uses MarkEditMac~Modules~AppKitExtensions✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Settings uses a type in MarkEditMac~Modules~AppKitExtensions.
- The types involved
MarkEditMac~Settings.EditorSettingsView→MarkEditMac~Modules~AppKitExtensions.NSImage
- Direction
- MarkEditMac~Settings uses MarkEditMac~Modules~AppKitExtensions, so a change to MarkEditMac~Modules~AppKitExtensions can break MarkEditMac~Settings, while a change to MarkEditMac~Settings can't break MarkEditMac~Modules~AppKitExtensions.
- Position
- Below the diagonal: MarkEditMac~Settings uses a module listed above it, which is the healthy direction.
38→29 MarkEditMac~Settings uses MarkEditMac~Extension✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Settings uses a type in MarkEditMac~Extension.
- The types involved
MarkEditMac~Settings.EditorSettingsView→MarkEditMac~Extension.ExtensionsModelMarkEditMac~Settings.EditorSettingsView→MarkEditMac~Extension.ExtensionsScrollTarget
- Direction
- MarkEditMac~Settings uses MarkEditMac~Extension, so a change to MarkEditMac~Extension can break MarkEditMac~Settings, while a change to MarkEditMac~Settings can't break MarkEditMac~Extension.
- Position
- Below the diagonal: MarkEditMac~Settings uses a module listed above it, which is the healthy direction.
38→34 MarkEditMac~Settings uses MarkEditCore~Extensions✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Settings uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditMac~Settings.EditorSettingsView→MarkEditCore~Extensions.String
- Direction
- MarkEditMac~Settings uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Settings, while a change to MarkEditMac~Settings can't break MarkEditCore~Extensions.
- Position
- Below the diagonal: MarkEditMac~Settings uses a module listed above it, which is the healthy direction.
39→17 MarkEditMac~Shortcuts uses repository✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Shortcuts uses a type in repository.
- The types involved
MarkEditMac~Shortcuts.IntentError→repository.Error
- Direction
- MarkEditMac~Shortcuts uses repository, so a change to repository can break MarkEditMac~Shortcuts, while a change to MarkEditMac~Shortcuts can't break repository.
- Position
- Below the diagonal: MarkEditMac~Shortcuts uses a module listed above it, which is the healthy direction.
39→30 MarkEditMac~Shortcuts uses MarkEditMac~Editor✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Shortcuts uses a type in MarkEditMac~Editor.
- The types involved
MarkEditMac~Shortcuts.AppIntent→MarkEditMac~Editor.EditorViewController
- Direction
- MarkEditMac~Shortcuts uses MarkEditMac~Editor, so a change to MarkEditMac~Editor can break MarkEditMac~Shortcuts, while a change to MarkEditMac~Shortcuts can't break MarkEditMac~Editor.
- Position
- Below the diagonal: MarkEditMac~Shortcuts uses a module listed above it, which is the healthy direction.
39→32 MarkEditMac~Shortcuts uses MarkEditKit~Bridge✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Shortcuts uses a type in MarkEditKit~Bridge.
- The types involved
MarkEditMac~Shortcuts.Granularity→MarkEditKit~Bridge.ReplaceGranularity
- Direction
- MarkEditMac~Shortcuts uses MarkEditKit~Bridge, so a change to MarkEditKit~Bridge can break MarkEditMac~Shortcuts, while a change to MarkEditMac~Shortcuts can't break MarkEditKit~Bridge.
- Position
- Below the diagonal: MarkEditMac~Shortcuts uses a module listed above it, which is the healthy direction.
39→34 MarkEditMac~Shortcuts uses MarkEditCore~Extensions✕
- Connections
- 4 pairs of types, where a type in MarkEditMac~Shortcuts uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditMac~Shortcuts.CreateNewDocumentIntent→MarkEditCore~Extensions.StringMarkEditMac~Shortcuts.EvaluateJavaScriptIntent→MarkEditCore~Extensions.StringMarkEditMac~Shortcuts.Granularity→MarkEditCore~Extensions.StringMarkEditMac~Shortcuts.UpdateFileContentIntent→MarkEditCore~Extensions.String
- Direction
- MarkEditMac~Shortcuts uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Shortcuts, while a change to MarkEditMac~Shortcuts can't break MarkEditCore~Extensions.
- Position
- Below the diagonal: MarkEditMac~Shortcuts uses a module listed above it, which is the healthy direction.
40→17 MarkEditMac~Updater uses repository✕
- Connections
- 1 pair of types, where a type in MarkEditMac~Updater uses a type in repository.
- The types involved
MarkEditMac~Updater.AppUpdater→repository.Error
- Direction
- MarkEditMac~Updater uses repository, so a change to repository can break MarkEditMac~Updater, while a change to MarkEditMac~Updater can't break repository.
- Position
- Below the diagonal: MarkEditMac~Updater uses a module listed above it, which is the healthy direction.
40→22 MarkEditMac~Updater uses MarkEditMac~Modules~AppKitExtensions✕
- Connections
- 2 pairs of types, where a type in MarkEditMac~Updater uses a type in MarkEditMac~Modules~AppKitExtensions.
- The types involved
MarkEditMac~Updater.AppUpdater→MarkEditMac~Modules~AppKitExtensions.NSAlertMarkEditMac~Updater.AppUpdater→MarkEditMac~Modules~AppKitExtensions.NSImage
- Direction
- MarkEditMac~Updater uses MarkEditMac~Modules~AppKitExtensions, so a change to MarkEditMac~Modules~AppKitExtensions can break MarkEditMac~Updater, while a change to MarkEditMac~Updater can't break MarkEditMac~Modules~AppKitExtensions.
- Position
- Below the diagonal: MarkEditMac~Updater uses a module listed above it, which is the healthy direction.
40→34 MarkEditMac~Updater uses MarkEditCore~Extensions✕
- Connections
- 6 pairs of types, where a type in MarkEditMac~Updater uses a type in MarkEditCore~Extensions.
- The types involved
MarkEditMac~Updater.AppUpdater→MarkEditCore~Extensions.StringMarkEditMac~Updater.AppUpdater→MarkEditCore~Extensions.URLMarkEditMac~Updater.AppVersion→MarkEditCore~Extensions.StringMarkEditMac~Updater.Asset→MarkEditCore~Extensions.StringMarkEditMac~Updater.Constants→MarkEditCore~Extensions.StringMarkEditMac~Updater.ReleaseInfo→MarkEditCore~Extensions.String
- Direction
- MarkEditMac~Updater uses MarkEditCore~Extensions, so a change to MarkEditCore~Extensions can break MarkEditMac~Updater, while a change to MarkEditMac~Updater can't break MarkEditCore~Extensions.
- Position
- Below the diagonal: MarkEditMac~Updater uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 8 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 4 | Medium |
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +4.7 pts | Low | Documentation Quality |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +7.4 pts | Medium | Security & performance tooling |
| Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (4). | +2.2 pts | Low | Dependency Hygiene |
| 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. | +4.4 pts | Medium | Architecture documentation |
| Resolve the 14 No assertions finding(s) in Test Quality — start with RuntimeTests.swift (12), SecretStorageTests.swift, EditorDocumentTests.swift. | +3.5 pts | Medium | Test Quality |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +3.0 pts | Medium | Release Hygiene |
| Resolve the 4 Skipped test finding(s) in Test Quality — start with MoveFileTests.swift, NativeBridgeParametersTests.swift, EditorDocumentTests.swift. | +1.0 pts | Low | Test Quality |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +1.8 pts | Medium | Observability |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.7 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| MarkEditKit/Sources/Bridge/Native/Modules/EditorModuleAPI.swift | 5.9 | Mixed | Cognitive Complexity: EditorModuleAPI.deleteLocalFileVersions (cognitive 17) |
| MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchMenuActions.swift | 6.3 | Mixed | Cyclomatic Complexity: QuickSearchMenuActions.resolve (cyclomatic 16) |
| MarkEditMac/Sources/Editor/Models/EditorDocument.swift | 6.3 | Mixed | Cognitive Complexity: EditorDocument.presentedItemDidChange (cognitive 17) |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| MarkEditMac/Sources/Editor/Controllers/EditorViewController.swift | 7.0 | Mixed | God Classes: TooManyMethods: EditorViewController |
| MarkEditMac/Sources/Main/Application/AppDelegate.swift | 7.0 | Mixed | God Classes: TooManyMethods: AppDelegate |
| MarkEditMac/Sources/Extension/ExtensionsViewController.swift | 7.0 | Mixed | God Classes: TooManyMethods: ExtensionsViewController |
| MarkEditMac/Modules/Tests/RuntimeTests.swift | 7.0 | Mixed | Test Quality: Skipped test: testExistenceOfAppKitSearchField |
| MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchController.swift | 7.0 | Mixed | Cyclomatic Complexity: QuickSearchController.activate (cyclomatic 26) |
| CoreEditor/src/@vendor/lang-markdown/commands.ts | 7.1 | Mixed | Cyclomatic Complexity: commands.insertNewlineContinueMarkupCommand.<returned closure> (cyclomatic 44) |
| MarkEditMac/Modules/Sources/ExtensionCore/ExtensionRegistry.swift | 7.1 | Mixed | Cyclomatic Complexity: ExtensionRelease.pageURL (cyclomatic 17) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| CoreEditor/src/@vendor/lang-html/complete.ts | 7.4 | Mixed | Cyclomatic Complexity: complete.htmlCompletionFor (cyclomatic 25) |
| MarkEditMac/Sources/Editor/Controllers/EditorViewController+Menu.swift | 7.4 | Mixed | Cyclomatic Complexity: EditorViewController.validateMenuItem (cyclomatic 18) |
| CoreEditor/src/modules/input/index.ts | 7.8 | Mixed | Cyclomatic Complexity: index.observeChanges (cyclomatic 32) |
| MarkEditMac/Modules/Sources/QuickSearchCore/FuzzyMatcher.swift | 7.8 | Mixed | Cyclomatic Complexity: FuzzyMatcher.match (cyclomatic 31) |
| MarkEditMac/Sources/Editor/Controllers/EditorViewController+Events.swift | 7.8 | Mixed | Cyclomatic Complexity: EditorViewController.addLocalMonitorForEvents (cyclomatic 30) |
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
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 47 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 47 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, 205 of 218 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 or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
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 |
| Canine Code Analyzer 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 |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half measured 65.8% (jest via `yarn install --immutable --mode=skip-build` in CoreEditor/); the Swift half could not be measured — the Swift suite in MarkEditCore produced no coverage export. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 297 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 40 test source file(s) (.ts, .cjs) that it cannot: it reads the test types the .swift frontend declared, so a suite in any other language is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT SCORED: this repository's production source includes .swift, and the swift executor ran against the .swift half and could not be re-run to completion inside our analyzer environment — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (jest via `yarn install --immutable --mode=skip-build` in CoreEditor/ (503 tests)): measured (1 flaky) suite(s) did re-run, and came back with 1 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The remedy is our analyzer environment, not a runner nobody has built.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — none of the 0 package(s) this repository's SwiftPM files bring in could be read at a pinned revision or is a repository the public index (api.deps.dev) knows, so no licence could be read for any of them: they are private, self-hosted, or unpinned and too little-referenced to be indexed. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- 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 (10 contributor(s) across 1650 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 9 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Project size and spread are measured over build units (a .NET project, a Maven or Gradle module, an npm, Deno or JSR package, a Go module, a Cargo crate, a Python, Composer, Bundler, RubyGems, Mix, rebar3, sbt, SwiftPM or pub package, an OTP application, an Xcode project or XcodeGen spec, or a checkout that declares no build at all) whose source a code model reads. This repository's production source is in a language no model reads, or in units whose build tool D26 does not recognise. That is a gap in this analyzer's language reach — not a finding that the repository's projects are cohesive.
- D27 Navigability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Tracing effort is measured over resolved call sites, and all 288 sampled here came from .swift files. This repository's .ts source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `CoreEditor/src/@types/global.d.ts`, `MarkEditCore/Sources/Extensions/WebKit+Extension.swift`, `MarkEditMac/Modules/Sources/QuickSearchCore/FileDiscovery.swift`, `MarkEditMac/Modules/Sources/QuickSearchCore/FuzzyMatcher.swift`, `MarkEditMac/Modules/Sources/QuickSearchCore/QuickSearchContext.swift`, … (+19 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Swift is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Swift 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X26 Unsynchronised callback handoff — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Swift (Foundation mutable collections) is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- 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.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- 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
25 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was commands.insertNewlineContinueMarkupCommand.<returned closure> at 44. A further 4 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 NSMenuItem.shortcutHint at 23 — they are counted neither in the figure above nor in this dimension's score. 2 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: MarkEditKit/Sources/EditorTextEncoding.swift (EditorTextEncoding.decode at 18), MarkEditMac/Sources/Editor/Models/EditorToolbarItems.swift (Identifier.itemLabel at 18). 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 3 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with commands.insertNewlineContinueMarkupCommand.<returned closure> (cyclomatic 44), index.observeChanges (cyclomatic 32), FuzzyMatcher.match (cyclomatic 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 6.9 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
35 method(s) exceeded the cognitive complexity threshold of 15; the worst was index.observeChanges at 57.
What to do
- Bring the 35 bodies over 15 down to 15 or less in Cognitive Complexity — start with index.observeChanges (cognitive 57), FileDiscovery.scan (cognitive 56), FuzzyMatcher.match (cognitive 53). — 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 35 together lifts Cognitive Complexity from 6.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
6 god class(es) detected.
What to do
- Resolve the 5 TooManyMethods finding(s) in God Classes — start with EditorViewController.swift, AppDelegate.swift, ExtensionsViewController.swift. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with QuickSearchController.swift. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
1 duplicated block group(s) detected. 0.5 % of the production lines (186 of 36,490) are in a reported copy. A further 8 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .ts (30% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
What to do
- Resolve the 1 Edited copies of one member (3 members, 23+ corresponding lines) finding(s) in Code Duplication — start with ExtensionRegistry.swift. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with EditorModuleAPI.swift. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with AppWritingTools.swift. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
17 production modules (npm+SwiftPM), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence, with abstractness counted on 16 of the 17 (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 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
D6 · Cohesion (LCOM4)
20 of 64 classes have LCOM4 above 3.
What to do
- Resolve the 20 Low cohesion finding(s) in Cohesion (LCOM4) — start with EditorViewController.swift, AppDelegate.swift, EditorModuleAPI.swift. — One of this dimension's main actionable groups (20 warning-level).
D10 · Test Quality
4 skipped, 14 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 297 tests. Measured on the .swift suite only — at least 40 test source file(s) (.ts, .cjs) went unread, so its test quality is unmeasured and is not in these counts.
What to do
- Resolve the 14 No assertions finding(s) in Test Quality — start with RuntimeTests.swift (12), SecretStorageTests.swift, EditorDocumentTests.swift. — One of this dimension's main actionable groups (14 warning-level).
- Resolve the 4 Skipped test finding(s) in Test Quality — start with MoveFileTests.swift, NativeBridgeParametersTests.swift, EditorDocumentTests.swift. — One of this dimension's main actionable groups (4 warning-level).
D12 · Dependency Hygiene
2 outdated direct production npm dependency(ies) of 14 graded, 0 pinning defect(s), across 1 package.json (1 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 1 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
What to do
- Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (4). — One of this dimension's main actionable groups (4 recommendation-level).
- Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with package.json. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
Top hotspots: MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchController.swift (13×26=338); MarkEditMac/Sources/Main/Application/AppDelegate+QuickSearch.swift (8×18=144); CoreEditor/src/core.ts (6×18=108)
What to do
- Resolve the 6 Hotspot finding(s) in Churn × Complexity Hotspots — start with QuickSearchController.swift, AppDelegate+QuickSearch.swift, core.ts. — One of this dimension's main actionable groups (6 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 36490 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 9 document(s) read across 2 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
2 of 409 judged comments only repeat the code they sit on (0.5 %). 17 comment(s) in another language or script were not judged.
D27 · Navigability
23 % of calls cross a namespace and 40 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated. Measured over the .swift source only — this repository's .ts was not sampled for call sites, so this score covers part of the tree, not all of it.
What to do
- Resolve the 1 High interface indirection finding(s) in Navigability. — 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)
8 finding(s): 0 critical, 3 high, 5 medium, 0 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `CoreEditor/src/@types/global.d.ts` (line 29), `MarkEditMac/Tests/EditorDocumentTests.swift` — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
4 finding(s): 0 critical, 0 high, 3 medium, 1 low.
What to do
- Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 157 of the 433 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: modules.ts↔api.ts 71%; config.ts↔AppPreferences.swift 63%; ui.ts↔EditorModuleAPI.swift 60%
What to do
- Resolve the 5 Change coupling finding(s) in Change Coupling — start with config.ts (2), ui.ts, NSEvent+Extension.swift. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with api.ts. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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.
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.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 4/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `MarkEditTools`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
- `CoreEditor/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — CoreEditor/package.json:16
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- CoreEditor/src/styling/themes/minimal-dark.ts:16 · CoreEditor/src/styling/themes/minimal-light.ts:16 — the 2 copies are spread across 2 files, 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. — CoreEditor/src/styling/themes/minimal-dark.ts:16
- CoreEditor/src/styling/helper.ts:5 · CoreEditor/src/styling/helper.ts:21 — 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. — CoreEditor/src/styling/helper.ts:5
- CoreEditor/src/modules/completion/index.ts:168 · CoreEditor/src/modules/tokenizer/index.ts:12 — the two spans are one implementation copied and then locally edited — 54 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. — CoreEditor/src/modules/completion/index.ts:168
- CoreEditor/src/modules/smartQuotes/index.ts:78 · CoreEditor/src/modules/smartQuotes/index.ts:112 — 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. — CoreEditor/src/modules/smartQuotes/index.ts:78
- CoreEditor/src/styling/themes/cobalt.ts:25 · CoreEditor/src/styling/themes/github-dark.ts:19 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — CoreEditor/src/styling/themes/cobalt.ts:25
- CoreEditor/src/styling/themes/dracula.ts:25 · CoreEditor/src/styling/themes/synthwave84.ts:35 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — CoreEditor/src/styling/themes/dracula.ts:25
- CoreEditor/src/styling/nodes/indent.ts:8 · CoreEditor/src/styling/nodes/indent.ts:24 — 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. — CoreEditor/src/styling/nodes/indent.ts:8
- CoreEditor/src/styling/themes/rose-pine-dawn.ts:28 · CoreEditor/src/styling/themes/rose-pine.ts:28 — the 2 copies are spread across 2 files, 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. — CoreEditor/src/styling/themes/rose-pine-dawn.ts:28
- CoreEditor/index.ts:114 · CoreEditor/index.ts:122 — 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. — CoreEditor/index.ts:114
- CoreEditor/src/styling/themes/rose-pine-dawn.ts:40 · CoreEditor/src/styling/themes/rose-pine.ts:40 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — CoreEditor/src/styling/themes/rose-pine-dawn.ts:40
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
- (anonymous) has cyclomatic complexity 43 and cognitive complexity 62; 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. — CoreEditor/src/@vendor/lang-markdown/commands.ts:106
- (anonymous) has cyclomatic complexity 28 and cognitive complexity 49; 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. — CoreEditor/src/modules/input/index.ts:137
- htmlCompletionFor has cyclomatic complexity 25 and cognitive complexity 25; 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. — CoreEditor/src/@vendor/lang-html/complete.ts:481
- handleKeyDown has cyclomatic complexity 18 and cognitive complexity 11; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — CoreEditor/src/modules/tokenizer/index.ts:48
- getContext has cyclomatic complexity 17 and cognitive complexity 23; 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. — CoreEditor/src/@vendor/lang-markdown/commands.ts:34
- (anonymous) has cyclomatic complexity 16 and cognitive complexity 30; 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. — CoreEditor/src/@vendor/lang-markdown/commands.ts:245
- (anonymous) has cyclomatic complexity 16 and cognitive complexity 17; 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. — CoreEditor/src/@vendor/lang-html/html.ts:109
- (anonymous) has cyclomatic complexity 15 and cognitive complexity 19; 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. — CoreEditor/src/modules/events/index.ts:164
- (anonymous) has cyclomatic complexity 15 and cognitive complexity 15; 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. — CoreEditor/src/modules/completion/index.ts:37
- filterTransaction has cyclomatic complexity 15 and cognitive complexity 13; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — CoreEditor/src/modules/input/index.ts:22
- formatContent has cyclomatic complexity 14 and cognitive complexity 22; 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. — CoreEditor/src/modules/commands/formatContent.ts:16
- update has cyclomatic complexity 14 and cognitive complexity 19; 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. — CoreEditor/src/@vendor/commands/history.ts:61
- resetEditor has cyclomatic complexity 13 and cognitive complexity 14; 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. — CoreEditor/src/core.ts:59
- parse has cyclomatic complexity 12 and cognitive complexity 20; 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. — CoreEditor/src/modules/math/index.ts:144
- pop has cyclomatic complexity 12 and cognitive complexity 16; 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. — CoreEditor/src/@vendor/commands/history.ts:362
- (anonymous) has cyclomatic complexity 12 and cognitive complexity 11; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — CoreEditor/src/modules/input/index.ts:99
- updateQuery has cyclomatic complexity 11 and cognitive complexity 21; 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. — CoreEditor/src/modules/search/index.ts:91
- extensions has cyclomatic complexity 11 and cognitive complexity 10; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — CoreEditor/src/extensions.ts:74
R3 · Large Files
- CoreEditor/src/@vendor/lang-html/complete.ts has 502 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — CoreEditor/src/@vendor/lang-html/complete.ts:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×15) — CoreEditor/index.ts:1, CoreEditor/src/bridge/web/format.ts:1, CoreEditor/src/bridge/web/config.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
R7 · Dead Code
- Unreachable from the 9 application, 4 tooling and 40 test entry point(s) detected in this repo. Gate removals on `npm run typecheck` — an undetected custom entry would make these reachable.
- no import path from any entry point (9 application, 4 tooling, 40 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — CoreEditor/src/bridge/web/dummy.ts
- Nothing imports this binding — it is safe to review for removal. — CoreEditor/src/styling/matchers/lezer.ts:30
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. — CoreEditor/src/styling/builder.ts:4
- Declared in CoreEditor/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.
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- CoreEditor/src/api/methods.ts → CoreEditor/src/extensions.ts → CoreEditor/src/api/methods.ts (one verified cycle inside a mutually-dependent group of 29 files) — CoreEditor/src/api/methods.ts:6
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
X26 · Unsynchronised callback handoff
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×4) — MarkEditKit/Sources/Extensions/URL+Extension.swift:24, MarkEditKit/Sources/Extensions/URL+Extension.swift:130, MarkEditKit/Sources/Bridge/Native/Modules/EditorModuleAPI.swift:166, …
- `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×2) — CoreEditor/src/modules/preview/overlay.ts:43, CoreEditor/src/modules/preview/renderers/mermaid.ts:31
What to do
- Swallowed exception (caught, then discarded)
X5 · Nullable reference types
- ~2.4 `!` null assertions per 1k TypeScript source lines — 30 assertion(s) across the 12717 source line(s) of the 167 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: CoreEditor/src/@vendor/lang-markdown/commands.ts (15), CoreEditor/src/@vendor/lang-html/html.ts (6), CoreEditor/src/@vendor/commands/history.ts (5). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 82% | Strong | Solid. |
| Architecture | 80% | Strong | Solid. |
| Maturity | 66% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 54% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 82% | Checked 3 of 8 | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 2 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 — 76 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — AX6 reached only 30% of this repository's production lines — swift (25,569 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D11 Test Reliability — Test reliability not scored — polyglot repository, one half's runner produced no measurement
- D14 License Compliance — SwiftPM package licences not graded — no dependency repository could be read
- 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 2 candidate(s) found and not reported.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Swift surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 measured no build unit over this repository's .swift source. 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) — 24 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — Swift suite
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 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
- M4 Documentation accuracy — Not applicable: the 9 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (environment variable 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Swift source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — X1 reached only 30% of this repository's production lines — swift (25,569 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X12 Unreachable branch — X12 reached only 30% of this repository's production lines — swift (25,569 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — X16 reached only 30% of this repository's production lines — swift (25,569 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X21 Side-effecting pattern guard — X21 reached only 30% of this repository's production lines — swift (25,569 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — X24 reached only 30% of this repository's production lines — swift (25,569 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X25 Inert configuration knob — X25 reached only 30% of this repository's production lines — swift (25,569 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X29 Per-element action decided by a fixed element — X29 reached only 30% of this repository's production lines — swift (25,569 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 6 finding(s)
- REDACTED
- REDACTED
- Flaky test: CoreEditor/test/task.test.ts::Task marker decoration decorates mixed task lists with the correct state per line
- REDACTED
- Unlisted import 'style-mod' CoreEditor/src/styling/builder.ts:4
- Import cycle (2 files) CoreEditor/src/api/methods.ts:6
Serious — 189 finding(s)
- Low cohesion: EditorViewController (LCOM4 31) MarkEditMac/Sources/Editor/Controllers/EditorViewController.swift:16
- Low cohesion: AppDelegate (LCOM4 22) MarkEditMac/Sources/Main/Application/AppDelegate.swift:15
- Low cohesion: EditorModuleAPI (LCOM4 7) MarkEditKit/Sources/Bridge/Native/Modules/EditorModuleAPI.swift:46
- Low cohesion: NSMenuItem (LCOM4 7) MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchMenuActions.swift:132
- Low cohesion: Data (LCOM4 6) MarkEditKit/Sources/EditorTextEncoding.swift:112
- Low cohesion: NSView (LCOM4 6) MarkEditMac/Modules/Sources/AppKitExtensions/UI/NSView+Extension.swift:11
- Low cohesion: NSWindow (LCOM4 6) MarkEditMac/Modules/Sources/AppKitExtensions/UI/NSWindow+Extension.swift:9
- Low cohesion: View (LCOM4 6) MarkEditMac/Modules/Sources/FontPicker/FontPicker.swift:204
- Low cohesion: String (LCOM4 5) MarkEditCore/Sources/Extensions/String+Extension.swift:9
- Low cohesion: URL (LCOM4 5) MarkEditCore/Sources/Extensions/URL+Extension.swift:9
- Low cohesion: EditorWindowController (LCOM4 5) MarkEditMac/Sources/Editor/EditorWindowController.swift:11
- Low cohesion: EditorDocument (LCOM4 5) MarkEditMac/Sources/Editor/Models/EditorDocument.swift:18
- Low cohesion: QuickSearchWindow (LCOM4 5) MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchWindow.swift:9
- Low cohesion: QuickLookViewController (LCOM4 5) QuickLookMac/QuickLookViewController.swift:13
- Low cohesion: WKWebView (LCOM4 4) MarkEditCore/Sources/Extensions/WebKit+Extension.swift:9
- Low cohesion: EditorStatusView (LCOM4 4) MarkEditMac/Sources/Editor/Views/EditorStatusView.swift:15
- Low cohesion: ExtensionsModel (LCOM4 4) MarkEditMac/Sources/Extension/ExtensionsModel.swift:26
- Low cohesion: ExtensionsViewController (LCOM4 4) MarkEditMac/Sources/Extension/ExtensionsViewController.swift:37
- Low cohesion: NSApplication (LCOM4 4) MarkEditMac/Sources/Extras/NSApplication+Extras.swift:11
- Low cohesion: NSMenu (LCOM4 4) MarkEditMac/Sources/Extras/NSMenu+Extras.swift:10
- No test reaches this file CoreEditor/index.ts:1
- No test reaches this file CoreEditor/src/bridge/web/format.ts:1
- No test reaches this file CoreEditor/src/bridge/web/config.ts:1
- No test reaches this file CoreEditor/src/bridge/web/search.ts:1
- No test reaches this file CoreEditor/src/bridge/web/core.ts:1
- No test reaches this file CoreEditor/src/bridge/web/selection.ts:1
- No test reaches this file CoreEditor/src/bridge/web/history.ts:1
- No test reaches this file CoreEditor/src/bridge/web/toc.ts:1
- No test reaches this file CoreEditor/src/bridge/web/api.ts:1
- No test reaches this file CoreEditor/src/bridge/web/completion.ts:1
- No test reaches this file CoreEditor/src/bridge/web/foundationModels.ts:1
- No test reaches this file CoreEditor/src/bridge/web/dummy.ts:1
- No test reaches this file CoreEditor/src/bridge/web/lineEndings.ts:1
- No test reaches this file CoreEditor/src/bridge/web/writingTools.ts:1
- No test reaches this file CoreEditor/src/modules/snippets/index.ts:1
- No assertions: testKeychainErrorsAreNotAbsence MarkEditKit/Tests/SecretStorageTests.swift:60
- No assertions: testConcurrentOpeningThroughAppKit MarkEditMac/Tests/EditorDocumentTests.swift:868
- No assertions: testExistenceOfDrawsBackground MarkEditMac/Modules/Tests/RuntimeTests.swift:13
- No assertions: testExistenceOfDeveloperPreferences MarkEditMac/Modules/Tests/RuntimeTests.swift:49
- No assertions: testExistenceOfPerformancePreferences MarkEditMac/Modules/Tests/RuntimeTests.swift:61
- No assertions: testExistenceOfBulkFeatureDisabling MarkEditMac/Modules/Tests/RuntimeTests.swift:92
- No assertions: testExistenceOfAutomaticInlineCompletion MarkEditMac/Modules/Tests/RuntimeTests.swift:98
- No assertions: testExistenceOfAutomaticInlinePredictionBeingPresented MarkEditMac/Modules/Tests/RuntimeTests.swift:103
- No assertions: testExistenceOfShowCompletionForCandidate MarkEditMac/Modules/Tests/RuntimeTests.swift:108
- No assertions: testExistenceOfCancelCorrection MarkEditMac/Modules/Tests/RuntimeTests.swift:113
- No assertions: testExistenceOfImageTintColor MarkEditMac/Modules/Tests/RuntimeTests.swift:118
- No assertions: testPrivateAppKitClasses MarkEditMac/Modules/Tests/RuntimeTests.swift:184
- No assertions: testDelayedAppKitInternalFunctions MarkEditMac/Modules/Tests/RuntimeTests.swift:218
- No assertions: testExistenceOfShowWritingTools MarkEditMac/Modules/Tests/RuntimeTests.swift:230
- Hotspot: MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchController.swift MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchController.swift:574
- Hotspot: MarkEditMac/Sources/Main/Application/AppDelegate+QuickSearch.swift MarkEditMac/Sources/Main/Application/AppDelegate+QuickSearch.swift:41
- Hotspot: CoreEditor/src/core.ts CoreEditor/src/core.ts:59
- Hotspot: CoreEditor/src/modules/input/index.ts CoreEditor/src/modules/input/index.ts:135
- Hotspot: MarkEditMac/Sources/Extension/ExtensionsRowView.swift MarkEditMac/Sources/Extension/ExtensionsRowView.swift:21
- Hotspot: MarkEditMac/Modules/Sources/QuickSearchCore/Results/ContentSearchResult.swift MarkEditMac/Modules/Sources/QuickSearchCore/Results/ContentSearchResult.swift:72
- TooManyMethods: EditorViewController MarkEditMac/Sources/Editor/Controllers/EditorViewController.swift:16
- TooManyMethods: AppDelegate MarkEditMac/Sources/Main/Application/AppDelegate.swift:15
- TooManyMethods: ExtensionsViewController MarkEditMac/Sources/Extension/ExtensionsViewController.swift:37
- TooManyMethods: EditorDocument MarkEditMac/Sources/Editor/Models/EditorDocument.swift:18
- TooManyMethods: EditorModuleAPI MarkEditKit/Sources/Bridge/Native/Modules/EditorModuleAPI.swift:46
- Change coupling: config.ts ↔ AppPreferences.swift CoreEditor/src/config.ts:1
- Change coupling: ui.ts ↔ EditorModuleAPI.swift CoreEditor/src/api/ui.ts:1
- Change coupling: NSEvent+Extension.swift ↔ EditorViewController+Events.swift MarkEditMac/Modules/Sources/AppKitExtensions/Foundation/NSEvent+Extension.swift:1
- Change coupling: config.ts ↔ QuickLookViewController.swift CoreEditor/src/config.ts:1
- Change coupling: selection.ts ↔ EditorViewController+Menu.swift CoreEditor/src/bridge/web/selection.ts:1
- Skipped test: testCrossVolumeContract MarkEditKit/Tests/MoveFileTests.swift:100
- Skipped test: testInvalidArgumentsDoNotInvokeNativeMethods MarkEditKit/Tests/NativeBridgeParametersTests.swift:93
- Skipped test: testSecretStorageWithSystemKeychain MarkEditMac/Tests/EditorDocumentTests.swift:697
- Skipped test: testExistenceOfAppKitSearchField MarkEditMac/Modules/Tests/RuntimeTests.swift:122
- Swallowed exception (caught, then discarded) MarkEditKit/Sources/Extensions/URL+Extension.swift:24
- Swallowed exception (caught, then discarded) MarkEditKit/Sources/Extensions/URL+Extension.swift:130
- Swallowed exception (caught, then discarded) MarkEditKit/Sources/Bridge/Native/Modules/EditorModuleAPI.swift:166
- Swallowed exception (caught, then discarded) MarkEditKit/Sources/Bridge/Native/Modules/EditorModuleAPI.swift:179
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Off the main sequence: DiffKit
- Off the main sequence: QuickSearchCore
- Off the main sequence: TextBundle
- Duplicated block (8 lines × 2 locations) CoreEditor/src/styling/themes/cobalt.ts:25
- Duplicated block (8 lines × 2 locations) CoreEditor/src/styling/themes/dracula.ts:25
- Duplicated block (6 lines × 2 locations) CoreEditor/src/styling/nodes/indent.ts:8
- Duplicated block (6 lines × 2 locations) CoreEditor/src/styling/themes/rose-pine-dawn.ts:28
- Duplicated block (5 lines × 2 locations) CoreEditor/index.ts:114
- Duplicated block (5 lines × 2 locations) CoreEditor/src/styling/themes/rose-pine-dawn.ts:40
- Swallowed exception (empty catch) CoreEditor/src/modules/preview/overlay.ts:43
- Swallowed exception (empty catch) CoreEditor/src/modules/preview/renderers/mermaid.ts:31
- commands.insertNewlineContinueMarkupCommand.<returned closure> (cyclomatic 44) CoreEditor/src/@vendor/lang-markdown/commands.ts:104
- index.observeChanges (cyclomatic 32) CoreEditor/src/modules/input/index.ts:135
- FuzzyMatcher.match (cyclomatic 31) MarkEditMac/Modules/Sources/QuickSearchCore/FuzzyMatcher.swift:16
- EditorViewController.addLocalMonitorForEvents (cyclomatic 30) MarkEditMac/Sources/Editor/Controllers/EditorViewController+Events.swift:13
- FileDiscovery.scan (cyclomatic 26) MarkEditMac/Modules/Sources/QuickSearchCore/FileDiscovery.swift:20
- QuickSearchResult.search (cyclomatic 26) MarkEditMac/Modules/Sources/QuickSearchCore/Results/ContentSearchResult.swift:72
- QuickSearchController.activate (cyclomatic 26) MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchController.swift:574
- complete.htmlCompletionFor (cyclomatic 25) CoreEditor/src/@vendor/lang-html/complete.ts:481
- index.handleKeyDown (cyclomatic 24) CoreEditor/src/modules/tokenizer/index.ts:48
- html.autoCloseTags (cyclomatic 23) CoreEditor/src/@vendor/lang-html/html.ts:105
- EditorViewController.updateTextFinderMode (cyclomatic 22) MarkEditMac/Sources/Editor/Controllers/EditorViewController+TextFinder.swift:12
- EditorViewController.toolbar (cyclomatic 22) MarkEditMac/Sources/Editor/Controllers/EditorViewController+Toolbar.swift:80
- QuickSearchController.refreshDocument (cyclomatic 19) MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchController.swift:190
- EditorViewController.validateMenuItem (cyclomatic 18) MarkEditMac/Sources/Editor/Controllers/EditorViewController+Menu.swift:85
- AppDelegate.quickSearch (cyclomatic 18) MarkEditMac/Sources/Main/Application/AppDelegate+QuickSearch.swift:41
- QuickSearchController.search (cyclomatic 18) MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchController.swift:300
- core.resetEditor (cyclomatic 18) CoreEditor/src/core.ts:59
- ExtensionRelease.pageURL (cyclomatic 17) MarkEditMac/Modules/Sources/ExtensionCore/ExtensionRegistry.swift:39
- ResultCell.compactSubtitle (cyclomatic 17) MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchResultsView.swift:407
- toggleBlockWithMarks.toggleBlockWithMarks (cyclomatic 17) CoreEditor/src/modules/commands/toggleBlockWithMarks.ts:14
- commands.getContext (cyclomatic 17) CoreEditor/src/@vendor/lang-markdown/commands.ts:34
- commands.deleteMarkupBackward (cyclomatic 17) CoreEditor/src/@vendor/lang-markdown/commands.ts:243
- ExtensionsRowView.body (cyclomatic 16) MarkEditMac/Sources/Extension/ExtensionsRowView.swift:21
- ExtensionRegistry.refresh (cyclomatic 16) MarkEditMac/Modules/Sources/ExtensionCore/ExtensionRegistry.swift:236
- QuickSearchMenuActions.resolve (cyclomatic 16) MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchMenuActions.swift:42
- Deprecated: eslint CoreEditor/package.json:37
- index.observeChanges (cognitive 57) CoreEditor/src/modules/input/index.ts:135
- FileDiscovery.scan (cognitive 56) MarkEditMac/Modules/Sources/QuickSearchCore/FileDiscovery.swift:20
- FuzzyMatcher.match (cognitive 53) MarkEditMac/Modules/Sources/QuickSearchCore/FuzzyMatcher.swift:16
- commands.insertNewlineContinueMarkupCommand.<returned closure> (cognitive 51) CoreEditor/src/@vendor/lang-markdown/commands.ts:104
- EditorViewController.addLocalMonitorForEvents (cognitive 35) MarkEditMac/Sources/Editor/Controllers/EditorViewController+Events.swift:13
- QuickSearchController.activate (cognitive 34) MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchController.swift:574
- toggleListStyle.toggleListStyle (cognitive 31) CoreEditor/src/modules/commands/toggleListStyle.ts:14
- commands.deleteMarkupBackward (cognitive 29) CoreEditor/src/@vendor/lang-markdown/commands.ts:243
- toggleBlockWithMarks.toggleBlockWithMarks (cognitive 27) CoreEditor/src/modules/commands/toggleBlockWithMarks.ts:14
- QuickSearchResult.search (cognitive 26) MarkEditMac/Modules/Sources/QuickSearchCore/Results/ContentSearchResult.swift:72
- EditorViewController.updateTextFinderMode (cognitive 25) MarkEditMac/Sources/Editor/Controllers/EditorViewController+TextFinder.swift:12
- complete.htmlCompletionFor (cognitive 25) CoreEditor/src/@vendor/lang-html/complete.ts:481
- formatContent.formatContent (cognitive 23) CoreEditor/src/modules/commands/formatContent.ts:16
- commands.getContext (cognitive 23) CoreEditor/src/@vendor/lang-markdown/commands.ts:34
- QuickSearchMenuActions.resolve (cognitive 22) MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchMenuActions.swift:42
- QuickSearchController.refreshDocument (cognitive 21) MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchController.swift:190
- ExtensionsRowView.body (cognitive 20) MarkEditMac/Sources/Extension/ExtensionsRowView.swift:21
- QuickSearchController.search (cognitive 20) MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchController.swift:300
- index.handleKeyDown (cognitive 20) CoreEditor/src/modules/tokenizer/index.ts:48
- core.resetEditor (cognitive 20) CoreEditor/src/core.ts:59
- EditorViewController.validateMenuItem (cognitive 19) MarkEditMac/Sources/Editor/Controllers/EditorViewController+Menu.swift:85
- EditorWebView.updateMenuItems (cognitive 19) MarkEditMac/Sources/Editor/Views/EditorWebView.swift:196
- AppDelegate.quickSearch (cognitive 19) MarkEditMac/Sources/Main/Application/AppDelegate+QuickSearch.swift:41
- index.observeEventsForCompletion (cognitive 19) CoreEditor/src/modules/events/index.ts:163
- ExtensionRelease.pageURL (cognitive 18) MarkEditMac/Modules/Sources/ExtensionCore/ExtensionRegistry.swift:39
- EditorFindPanel.navigateRecentSearches (cognitive 18) MarkEditMac/Sources/Panels/Find/EditorFindPanel+Delegate.swift:51
- index.wrapMath (cognitive 18) CoreEditor/src/modules/math/index.ts:41
- index.updateQuery (cognitive 18) CoreEditor/src/modules/search/index.ts:91
- EditorModuleAPI.deleteLocalFileVersions (cognitive 17) MarkEditKit/Sources/Bridge/Native/Modules/EditorModuleAPI.swift:488
- EditorDocument.presentedItemDidChange (cognitive 17) MarkEditMac/Sources/Editor/Models/EditorDocument.swift:441
- ExtensionRegistry.refresh (cognitive 17) MarkEditMac/Modules/Sources/ExtensionCore/ExtensionRegistry.swift:236
- ResultCell.compactSubtitle (cognitive 17) MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchResultsView.swift:407
- EditorWindow.updateTitleBarAppearance (cognitive 16) MarkEditMac/Sources/Editor/EditorWindow.swift:75
- toggleLineLeadingMark.toggleLineLeadingMark (cognitive 16) REDACTED:10
- complete.completeAttrValue (cognitive 16) CoreEditor/src/@vendor/lang-html/complete.ts:453
- REDACTED
- REDACTED
- FileTooLong: QuickSearchUI/QuickSearchController.swift MarkEditMac/Modules/Sources/QuickSearchUI/QuickSearchController.swift
- Change-coupling hub: api.ts → methods.ts, modules.ts, ui.ts CoreEditor/src/bridge/native/api.ts
- REDACTED
- Edited copies of one member (3 members, 23+ corresponding lines) MarkEditMac/Modules/Sources/ExtensionCore/ExtensionRegistry.swift:112
- Edited copy of a member (15 corresponding lines) MarkEditKit/Sources/Bridge/Native/Modules/EditorModuleAPI.swift:452
- Edited copy of a member (8 corresponding lines) MarkEditMac/Sources/Main/AppWritingTools.swift:134
- Edited copy of a member (11 corresponding lines) MarkEditMac/Sources/Extension/Core/ExtensionInstaller.swift:101
- Edited copy of a member (10 corresponding lines) MarkEditMac/Sources/Editor/Controllers/EditorViewController+Menu.swift:366
- Edited copy of a member (6 corresponding lines) MarkEditMac/Modules/Sources/AppKitExtensions/UI/NSColor+Extension.swift:28
- Edited copies of one member (3 members, 5+ corresponding lines) MarkEditKit/Sources/Bridge/Native/Modules/EditorModuleSecretStorage.swift:46
- Duplicated block (9 lines × 2) MarkEditMac/Modules/Sources/ExtensionCore/ExtensionConfig.swift:225
- Duplicated block (15 lines × 2 locations) CoreEditor/src/styling/themes/minimal-dark.ts:16
- Duplicated block (14 lines × 2 locations) CoreEditor/src/styling/helper.ts:5
- Duplicated block with local edits (11 matched lines × 2 locations) CoreEditor/src/modules/completion/index.ts:168
- Duplicated block (9 lines × 2 locations) CoreEditor/src/modules/smartQuotes/index.ts:78
- Complex function (anonymous) (cyclomatic 43, cognitive 62) CoreEditor/src/@vendor/lang-markdown/commands.ts:106
- Complex function (anonymous) (cyclomatic 28, cognitive 49) CoreEditor/src/modules/input/index.ts:137
- Complex function htmlCompletionFor (cyclomatic 25, cognitive 25) CoreEditor/src/@vendor/lang-html/complete.ts:481
- Complex function handleKeyDown (cyclomatic 18, cognitive 11) CoreEditor/src/modules/tokenizer/index.ts:48
- Complex function getContext (cyclomatic 17, cognitive 23) CoreEditor/src/@vendor/lang-markdown/commands.ts:34
- Complex function (anonymous) (cyclomatic 16, cognitive 30) CoreEditor/src/@vendor/lang-markdown/commands.ts:245
- Complex function (anonymous) (cyclomatic 16, cognitive 17) CoreEditor/src/@vendor/lang-html/html.ts:109
- Complex function (anonymous) (cyclomatic 15, cognitive 19) CoreEditor/src/modules/events/index.ts:164
- Complex function (anonymous) (cyclomatic 15, cognitive 15) CoreEditor/src/modules/completion/index.ts:37
- Complex function filterTransaction (cyclomatic 15, cognitive 13) CoreEditor/src/modules/input/index.ts:22
- Complex function formatContent (cyclomatic 14, cognitive 22) CoreEditor/src/modules/commands/formatContent.ts:16
- Complex function update (cyclomatic 14, cognitive 19) CoreEditor/src/@vendor/commands/history.ts:61
- Complex function resetEditor (cyclomatic 13, cognitive 14) CoreEditor/src/core.ts:59
- Complex function parse (cyclomatic 12, cognitive 20) CoreEditor/src/modules/math/index.ts:144
- Complex function pop (cyclomatic 12, cognitive 16) CoreEditor/src/@vendor/commands/history.ts:362
- Complex function (anonymous) (cyclomatic 12, cognitive 11) CoreEditor/src/modules/input/index.ts:99
- Complex function updateQuery (cyclomatic 11, cognitive 21) CoreEditor/src/modules/search/index.ts:91
- Complex function extensions (cyclomatic 11, cognitive 10) CoreEditor/src/extensions.ts:74
- CoreEditor/src/@vendor/lang-html/complete.ts: 502 lines of code CoreEditor/src/@vendor/lang-html/complete.ts:1
- Dead file (~23 LoC) CoreEditor/src/bridge/web/dummy.ts
- Unused dependency 'tslib'
Minor — 20 finding(s)
- Deprecated: glob REDACTED:3029
- Deprecated: glob REDACTED:3056
- Deprecated: inflight REDACTED:3211
- Deprecated: whatwg-encoding REDACTED:5439
- redundant comment CoreEditor/src/@vendor/lang-markdown/index.ts:11
- redundant comment CoreEditor/src/@vendor/lang-markdown/index.ts:22
- Silent fallback default in catch MarkEditCore/Sources/Extensions/Encodable+Extension.swift:11
- Silent fallback default in catch MarkEditMac/Modules/Sources/Statistics/StatisticsRule.swift:38
- Documentation: no build, run or usage example README.md:1
- High interface indirection
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- No SAST REDACTED:6
- No dependency-update automation CoreEditor/package.json:16
- No changelog
- Unused export 'createMarkDeco' CoreEditor/src/styling/matchers/lezer.ts:30
- Duplicated predicate MarkEditMac/Sources/Editor/EditorWindowController.swift:204
- Null assertions (`!`) override strict null checking
Minor — 3 finding(s)
- Outdated (npm): @lezer/common
- Outdated (npm): @lezer/lr
- doc comments repeat the names CoreEditor/src/modules/input/wrapBlock.ts:8
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b11d4b63ddc3448c8553f4c8f3063c98/history.json --exit-code 0 --source . | 17 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b11d4b63ddc3448c8553f4c8f3063c98/tree.json --exit-code 0 --source . | 3 | 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/canine-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 --exclude MarkEditKit/Sources/Bridge/Native/Generated --exclude MarkEditKit/Sources/Bridge/Web/Generated . | 8 | 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/** . | 4 | 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 24 file(s) — `CoreEditor/src/@types/global.d.ts`, `MarkEditCore/Sources/Extensions/WebKit+Extension.swift`, `MarkEditMac/Modules/Sources/QuickSearchCore/FileDiscovery.swift`, `MarkEditMac/Modules/Sources/QuickSearchCore/FuzzyMatcher.swift`, `MarkEditMac/Modules/Sources/QuickSearchCore/QuickSearchContext.swift`, … (+19 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |