Executive summary
bitgapp/eqMac falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 36 out of 100 and is rated Weak, and none of its 28 critical findings concern security.
Production Readiness, at 21, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 5 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 4 points. Raising Production Readiness to 70 would lift the score to about 47.
Seventeen controls can't be used without a mouse. Nine buttons or links have no name a screen reader can say, and one form field can't be read by a screen reader. Making the controls work with a keyboard, naming the buttons and links, and labelling the form fields would close these risks. The loop of files that import each other needs breaking.
The product code is 15,323 lines, about €13,000 to rebuild.
If Production Readiness rose from 21 to 70, the lowest score rated Strong, the score would rise from 36 to about 47.
New since the last survey: 41 findings
- Code Duplication · Edited copy of a member (30 corresponding lines) native/shared/Source/CircularBuffer.swift
- Code Duplication · Edited copy of a member (11 corresponding lines) native/app/Source/Audio/Effects/Equalizers/Advanced/AdvancedEqualizer.swift
- Code Duplication · Edited copy of a member (11 corresponding lines) native/app/Source/Audio/Effects/Equalizers/Advanced/AdvancedEqualizer.swift
- Code Duplication · Edited copy of a member (7 corresponding lines) native/app/Source/Audio/AudioDeviceEvents.swift
- Code Duplication · Edited copy of a member (5 corresponding lines) native/app/Source/Audio/Effects/Equalizers/Advanced/AdvancedEqualizer.swift
- Code Duplication · Edited copy of a member (3 corresponding lines) native/app/Source/Audio/Effects/Equalizers/Advanced/AdvancedEqualizer.swift
- Dependency Hygiene · Unused dependency '@angular/compiler-cli'
- Dependency Hygiene · Unused dependency '@angular/language-service'
- Dependency Hygiene · Unused dependency 'cloudflare'
- Dependency Hygiene · Unused dependency 'core-js'
- Dependency Hygiene · Unused dependency 'dayjs'
- Dependency Hygiene · Unused dependency 'dotenv'
- Dependency Hygiene · Unused dependency 'ng-packagr'
- Dependency Hygiene · Unused dependency 'tslib'
- Dependency Hygiene · Unused dependency 'tslint'
- Forms & labels · Custom control with no accessible name on <div> modules/components/src/components/dropdown/dropdown.component.html
- Forms & labels · Custom control with no accessible name on <div> modules/components/src/components/dropdown/dropdown.component.html
- Forms & labels · Custom control with no accessible name on <div> modules/components/src/components/toggle/toggle.component.html
- Forms & labels · Custom control with no accessible name on <div> ui/src/app/sections/header/header.component.html
- Forms & labels · Custom control with no accessible name on <div> ui/src/app/sections/header/header.component.html
- Forms & labels · Custom control with no accessible name on <div> ui/src/app/sections/header/header.component.html
- Forms & labels · Custom control with no accessible name on <div> ui/src/app/sections/header/header.component.html
- Forms & labels · Custom control with no accessible name on <div> ui/src/app/sections/header/header.component.html
- Forms & labels · Custom control with no accessible name on <div> ui/src/app/sections/header/header.component.html
- Keyboard semantics · Click handler on a non-interactive <div> modules/components/src/components/button/button.component.html
- Keyboard semantics · Click handler on a non-interactive <div> modules/components/src/components/dropdown/dropdown.component.html
- Keyboard semantics · Click handler on a non-interactive <div> modules/components/src/components/dropdown/dropdown.component.html
- Keyboard semantics · Double-click handler on a non-interactive <div> modules/components/src/components/flat-slider/flat-slider.component.html
- Keyboard semantics · Double-click handler on a non-interactive <div> modules/components/src/components/knob/knob.component.html
- Keyboard semantics · Click handler on a non-interactive <div> modules/components/src/components/select-box/select-box.component.html
- Keyboard semantics · Double-click handler on a non-interactive <div> modules/components/src/components/skeuomorph-slider/skeuomorph-slider.component.html
- Keyboard semantics · Click handler on a non-interactive <div> modules/components/src/components/toggle/toggle.component.html
- Keyboard semantics · Click handler on a non-interactive <div> ui/src/app/components/options/options.component.html
- Keyboard semantics · Click handler on a non-interactive <div> ui/src/app/components/options/options.component.html
- Keyboard semantics · Hover-only interaction on <div> ui/src/app/sections/header/header.component.html
- Keyboard semantics · Click handler on a non-interactive <div> ui/src/app/sections/header/header.component.html
- Keyboard semantics · Click handler on a non-interactive <div> ui/src/app/sections/header/header.component.html
- Keyboard semantics · Click handler on a non-interactive <div> ui/src/app/sections/header/header.component.html
- Keyboard semantics · Click handler on a non-interactive <div> ui/src/app/sections/header/header.component.html
- Keyboard semantics · Click handler on a non-interactive <div> ui/src/app/sections/header/header.component.html
- Keyboard semantics · Click handler on a non-interactive <div> ui/src/app/sections/header/header.component.html
Fixed since the last survey: 12 findings
- Code Duplication · Duplicated block (12 lines × 4) native/app/Source/Settings/SettingsDataBus.swift
- Code Duplication · Duplicated block (11 lines × 2) native/app/Source/UI/UIDataBus.swift
- Code Duplication · Duplicated block (9 lines × 2) native/app/Source/Audio/Effects/Equalizers/EqualizersDataBus.swift
- Code Duplication · Duplicated block (9 lines × 2) native/app/Source/Audio/Volume/VolumeDataBus.swift
- Code Duplication · Duplicated block (9 lines × 2) native/app/Source/UI/UIDataBus.swift
- Code Duplication · Duplicated block (8 lines × 6) native/app/Source/Audio/Volume/VolumeDataBus.swift
- Code Duplication · Duplicated block (8 lines × 2) native/app/Source/Audio/Effects/Equalizers/EqualizersDataBus.swift
- Code Duplication · Duplicated block (8 lines × 2) native/app/Source/UI/UIDataBus.swift
- Code Duplication · Duplicated block (8 lines × 2) native/app/Source/UI/UIDataBus.swift
- Code Duplication · Duplicated block (5 lines × 3) native/app/Source/UI/UIDataBus.swift
- Secrets (history) · High secret: WD-SECRET-0005 site/package-lock.json
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €13,000 · Estimate
| Cost to rebuild | €4,300 to €22,000, for 72 to 229 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 36. 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 | Small: 15,323 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: which parts of the code depend on which
| uses → | 1 modules.components.src.services.colors_service | 2 modules.components.src.services.utilities_service | 3 ui.src.app.services.toast_service | 4 modules.components.src.components.dropdown.dropdown_component | 5 modules.components.src.components.flat-slider.flat-slider_component | 6 modules.components.src.components.knob.knob_component | 7 modules.components.src.components.tooltip.tooltip_component | 8 native~shared | 9 ui.src.app.sections.effects.equalizers.equalizers_service | 10 ui.src.app.services.data_service | 11 modules.components.src.components.tooltip.tooltip_directive | 12 native~app~Extensions | 13 ui.src.app.sections.settings.settings_service | 14 ui.src.app.sections.source.source_service | 15 ui.src.app.services.transitions_service | 16 ui.src.app.services.ui_service | 17 ui.src.app.services.volume_service | 18 native~app~UI | 19 ui.src.app.services.app_service | 20 native~app~DataBus | 21 ui.src.app.components.options.options_component | 22 ui.src.app.sections.header.header_component | 23 ui.src.app.sections.outputs.outputs_component | 24 ui.src.app.sections.source.file.file_component | 25 ui.src.app.sections.volume.booster-balance.balance.balance_component | 26 ui.src.app.sections.volume.booster-balance.booster.booster_component | 27 ui.src.app.services.analytics_service | 28 native~app~Audio | 29 native~app~Settings | 30 native~app~Transition | 31 ui.src.app.components.options-dialog.options-dialog_component | 32 ui.src.app.sections.help.help_component | 33 ui.src.app.sections.settings.settings_component | 34 native~app~Helpers | 35 ui.src.app.sections.effects.equalizers.equalizer_component | 36 native~app | 37 ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component | 38 ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component | 39 ui.src.app.sections.effects.equalizers.equalizers_component | 40 ui.src.app.app_component |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 modules.components.src.services.colors_service | ||||||||||||||||||||||||||||||||||||||||
| 2 modules.components.src.services.utilities_service | ||||||||||||||||||||||||||||||||||||||||
| 3 ui.src.app.services.toast_service | ||||||||||||||||||||||||||||||||||||||||
| 4 modules.components.src.components.dropdown.dropdown_component | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 5 modules.components.src.components.flat-slider.flat-slider_component | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 6 modules.components.src.components.knob.knob_component | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 modules.components.src.components.tooltip.tooltip_component | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 native~shared | 4 | |||||||||||||||||||||||||||||||||||||||
| 9 ui.src.app.sections.effects.equalizers.equalizers_service | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 ui.src.app.services.data_service | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 modules.components.src.components.tooltip.tooltip_directive | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 native~app~Extensions | 8 | |||||||||||||||||||||||||||||||||||||||
| 13 ui.src.app.sections.settings.settings_service | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 ui.src.app.sections.source.source_service | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 ui.src.app.services.transitions_service | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 ui.src.app.services.ui_service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 ui.src.app.services.volume_service | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 native~app~UI | 14 | 10 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 19 ui.src.app.services.app_service | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 native~app~DataBus | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 ui.src.app.components.options.options_component | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 ui.src.app.sections.header.header_component | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 ui.src.app.sections.outputs.outputs_component | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 ui.src.app.sections.source.file.file_component | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 ui.src.app.sections.volume.booster-balance.balance.balance_component | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 ui.src.app.sections.volume.booster-balance.booster.booster_component | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 ui.src.app.services.analytics_service | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 native~app~Audio | 34 | 24 | 7 | 7 | 5 | |||||||||||||||||||||||||||||||||||
| 29 native~app~Settings | 2 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 30 native~app~Transition | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 ui.src.app.components.options-dialog.options-dialog_component | 2 | |||||||||||||||||||||||||||||||||||||||
| 32 ui.src.app.sections.help.help_component | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 ui.src.app.sections.settings.settings_component | 1 | 1 | 1 | 1 | 8 | 1 | ||||||||||||||||||||||||||||||||||
| 34 native~app~Helpers | 13 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 ui.src.app.sections.effects.equalizers.equalizer_component | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 native~app | 6 | 8 | 3 | 1 | 4 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 37 ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component | 1 | 1 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 38 ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 ui.src.app.sections.effects.equalizers.equalizers_component | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||
| 40 ui.src.app.app_component | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
4→1 modules.components.src.components.dropdown.dropdown_component uses modules.components.src.services.colors_service✕
- Connections
- 1 pair of types, where a type in modules.components.src.components.dropdown.dropdown_component uses a type in modules.components.src.services.colors_service.
- The types involved
modules.components.src.components.dropdown.dropdown_component.DropdownComponent→modules.components.src.services.colors_service.ColorsService
- Direction
- modules.components.src.components.dropdown.dropdown_component uses modules.components.src.services.colors_service, so a change to modules.components.src.services.colors_service can break modules.components.src.components.dropdown.dropdown_component, while a change to modules.components.src.components.dropdown.dropdown_component can't break modules.components.src.services.colors_service.
- Position
- Below the diagonal: modules.components.src.components.dropdown.dropdown_component uses a module listed above it, which is the healthy direction.
4→2 modules.components.src.components.dropdown.dropdown_component uses modules.components.src.services.utilities_service✕
- Connections
- 1 pair of types, where a type in modules.components.src.components.dropdown.dropdown_component uses a type in modules.components.src.services.utilities_service.
- The types involved
modules.components.src.components.dropdown.dropdown_component.DropdownComponent→modules.components.src.services.utilities_service.UtilitiesService
- Direction
- modules.components.src.components.dropdown.dropdown_component uses modules.components.src.services.utilities_service, so a change to modules.components.src.services.utilities_service can break modules.components.src.components.dropdown.dropdown_component, while a change to modules.components.src.components.dropdown.dropdown_component can't break modules.components.src.services.utilities_service.
- Position
- Below the diagonal: modules.components.src.components.dropdown.dropdown_component uses a module listed above it, which is the healthy direction.
5→1 modules.components.src.components.flat-slider.flat-slider_component uses modules.components.src.services.colors_service✕
- Connections
- 1 pair of types, where a type in modules.components.src.components.flat-slider.flat-slider_component uses a type in modules.components.src.services.colors_service.
- The types involved
modules.components.src.components.flat-slider.flat-slider_component.FlatSliderComponent→modules.components.src.services.colors_service.ColorsService
- Direction
- modules.components.src.components.flat-slider.flat-slider_component uses modules.components.src.services.colors_service, so a change to modules.components.src.services.colors_service can break modules.components.src.components.flat-slider.flat-slider_component, while a change to modules.components.src.components.flat-slider.flat-slider_component can't break modules.components.src.services.colors_service.
- Position
- Below the diagonal: modules.components.src.components.flat-slider.flat-slider_component uses a module listed above it, which is the healthy direction.
5→2 modules.components.src.components.flat-slider.flat-slider_component uses modules.components.src.services.utilities_service✕
- Connections
- 1 pair of types, where a type in modules.components.src.components.flat-slider.flat-slider_component uses a type in modules.components.src.services.utilities_service.
- The types involved
modules.components.src.components.flat-slider.flat-slider_component.FlatSliderComponent→modules.components.src.services.utilities_service.UtilitiesService
- Direction
- modules.components.src.components.flat-slider.flat-slider_component uses modules.components.src.services.utilities_service, so a change to modules.components.src.services.utilities_service can break modules.components.src.components.flat-slider.flat-slider_component, while a change to modules.components.src.components.flat-slider.flat-slider_component can't break modules.components.src.services.utilities_service.
- Position
- Below the diagonal: modules.components.src.components.flat-slider.flat-slider_component uses a module listed above it, which is the healthy direction.
6→2 modules.components.src.components.knob.knob_component uses modules.components.src.services.utilities_service✕
- Connections
- 1 pair of types, where a type in modules.components.src.components.knob.knob_component uses a type in modules.components.src.services.utilities_service.
- The types involved
modules.components.src.components.knob.knob_component.KnobComponent→modules.components.src.services.utilities_service.UtilitiesService
- Direction
- modules.components.src.components.knob.knob_component uses modules.components.src.services.utilities_service, so a change to modules.components.src.services.utilities_service can break modules.components.src.components.knob.knob_component, while a change to modules.components.src.components.knob.knob_component can't break modules.components.src.services.utilities_service.
- Position
- Below the diagonal: modules.components.src.components.knob.knob_component uses a module listed above it, which is the healthy direction.
7→2 modules.components.src.components.tooltip.tooltip_component uses modules.components.src.services.utilities_service✕
- Connections
- 1 pair of types, where a type in modules.components.src.components.tooltip.tooltip_component uses a type in modules.components.src.services.utilities_service.
- The types involved
modules.components.src.components.tooltip.tooltip_component.TooltipComponent→modules.components.src.services.utilities_service.UtilitiesService
- Direction
- modules.components.src.components.tooltip.tooltip_component uses modules.components.src.services.utilities_service, so a change to modules.components.src.services.utilities_service can break modules.components.src.components.tooltip.tooltip_component, while a change to modules.components.src.components.tooltip.tooltip_component can't break modules.components.src.services.utilities_service.
- Position
- Below the diagonal: modules.components.src.components.tooltip.tooltip_component uses a module listed above it, which is the healthy direction.
8→12 native~shared uses native~app~Extensions part of a loop✕
- Connections
- 4 pairs of types, where a type in native~shared uses a type in native~app~Extensions.
- The types involved
native~shared.Array→native~app~Extensions.Boolnative~shared.CircularBufferTimeBounds→native~app~Extensions.Boolnative~shared.EQMClient→native~app~Extensions.Boolnative~shared.Location→native~app~Extensions.Bool
- Direction
- native~shared uses native~app~Extensions, so a change to native~app~Extensions can break native~shared, while a change to native~shared can't break native~app~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.
9→39 ui.src.app.sections.effects.equalizers.equalizers_service uses ui.src.app.sections.effects.equalizers.equalizers_component part of a loop✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.equalizers_service uses a type in ui.src.app.sections.effects.equalizers.equalizers_component.
- The types involved
ui.src.app.sections.effects.equalizers.equalizers_service.EqualizersService→ui.src.app.sections.effects.equalizers.equalizers_component.EqualizersComponent
- Direction
- ui.src.app.sections.effects.equalizers.equalizers_service uses ui.src.app.sections.effects.equalizers.equalizers_component, so a change to ui.src.app.sections.effects.equalizers.equalizers_component can break ui.src.app.sections.effects.equalizers.equalizers_service, while a change to ui.src.app.sections.effects.equalizers.equalizers_service can't break ui.src.app.sections.effects.equalizers.equalizers_component.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→3 ui.src.app.services.data_service uses ui.src.app.services.toast_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.services.data_service uses a type in ui.src.app.services.toast_service.
- The types involved
ui.src.app.services.data_service.DataService→ui.src.app.services.toast_service.ToastService
- Direction
- ui.src.app.services.data_service uses ui.src.app.services.toast_service, so a change to ui.src.app.services.toast_service can break ui.src.app.services.data_service, while a change to ui.src.app.services.data_service can't break ui.src.app.services.toast_service.
- Position
- Below the diagonal: ui.src.app.services.data_service uses a module listed above it, which is the healthy direction.
11→7 modules.components.src.components.tooltip.tooltip_directive uses modules.components.src.components.tooltip.tooltip_component✕
- Connections
- 1 pair of types, where a type in modules.components.src.components.tooltip.tooltip_directive uses a type in modules.components.src.components.tooltip.tooltip_component.
- The types involved
modules.components.src.components.tooltip.tooltip_directive.TooltipDirective→modules.components.src.components.tooltip.tooltip_component.TooltipPositionSide
- Direction
- modules.components.src.components.tooltip.tooltip_directive uses modules.components.src.components.tooltip.tooltip_component, so a change to modules.components.src.components.tooltip.tooltip_component can break modules.components.src.components.tooltip.tooltip_directive, while a change to modules.components.src.components.tooltip.tooltip_directive can't break modules.components.src.components.tooltip.tooltip_component.
- Position
- Below the diagonal: modules.components.src.components.tooltip.tooltip_directive uses a module listed above it, which is the healthy direction.
12→8 native~app~Extensions uses native~shared✕
- Connections
- 8 pairs of types, where a type in native~app~Extensions uses a type in native~shared.
- The types involved
native~app~Extensions.AudioDevice→native~shared.Doublenative~app~Extensions.AudioDevice→native~shared.Stringnative~app~Extensions.AudioDevice→native~shared.UInt32native~app~Extensions.Data→native~shared.Stringnative~app~Extensions.Date→native~shared.Stringnative~app~Extensions.NSImage→native~shared.Stringnative~app~Extensions.NSObject→native~shared.Stringnative~app~Extensions.NSSavePanel→native~shared.String
- Direction
- native~app~Extensions uses native~shared, so a change to native~shared can break native~app~Extensions, while a change to native~app~Extensions can't break native~shared.
- Position
- Below the diagonal: native~app~Extensions uses a module listed above it, which is the healthy direction.
13→10 ui.src.app.sections.settings.settings_service uses ui.src.app.services.data_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.settings.settings_service uses a type in ui.src.app.services.data_service.
- The types involved
ui.src.app.sections.settings.settings_service.SettingsService→ui.src.app.services.data_service.DataService
- Direction
- ui.src.app.sections.settings.settings_service uses ui.src.app.services.data_service, so a change to ui.src.app.services.data_service can break ui.src.app.sections.settings.settings_service, while a change to ui.src.app.sections.settings.settings_service can't break ui.src.app.services.data_service.
- Position
- Below the diagonal: ui.src.app.sections.settings.settings_service uses a module listed above it, which is the healthy direction.
14→10 ui.src.app.sections.source.source_service uses ui.src.app.services.data_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.source.source_service uses a type in ui.src.app.services.data_service.
- The types involved
ui.src.app.sections.source.source_service.SourceService→ui.src.app.services.data_service.DataService
- Direction
- ui.src.app.sections.source.source_service uses ui.src.app.services.data_service, so a change to ui.src.app.services.data_service can break ui.src.app.sections.source.source_service, while a change to ui.src.app.sections.source.source_service can't break ui.src.app.services.data_service.
- Position
- Below the diagonal: ui.src.app.sections.source.source_service uses a module listed above it, which is the healthy direction.
15→10 ui.src.app.services.transitions_service uses ui.src.app.services.data_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.services.transitions_service uses a type in ui.src.app.services.data_service.
- The types involved
ui.src.app.services.transitions_service.TransitionService→ui.src.app.services.data_service.DataService
- Direction
- ui.src.app.services.transitions_service uses ui.src.app.services.data_service, so a change to ui.src.app.services.data_service can break ui.src.app.services.transitions_service, while a change to ui.src.app.services.transitions_service can't break ui.src.app.services.data_service.
- Position
- Below the diagonal: ui.src.app.services.transitions_service uses a module listed above it, which is the healthy direction.
16→6 ui.src.app.services.ui_service uses modules.components.src.components.knob.knob_component✕
- Connections
- 1 pair of types, where a type in ui.src.app.services.ui_service uses a type in modules.components.src.components.knob.knob_component.
- The types involved
ui.src.app.services.ui_service.UISettings→modules.components.src.components.knob.knob_component.KnobControlStyle
- Direction
- ui.src.app.services.ui_service uses modules.components.src.components.knob.knob_component, so a change to modules.components.src.components.knob.knob_component can break ui.src.app.services.ui_service, while a change to ui.src.app.services.ui_service can't break modules.components.src.components.knob.knob_component.
- Position
- Below the diagonal: ui.src.app.services.ui_service uses a module listed above it, which is the healthy direction.
16→10 ui.src.app.services.ui_service uses ui.src.app.services.data_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.services.ui_service uses a type in ui.src.app.services.data_service.
- The types involved
ui.src.app.services.ui_service.UIService→ui.src.app.services.data_service.DataService
- Direction
- ui.src.app.services.ui_service uses ui.src.app.services.data_service, so a change to ui.src.app.services.data_service can break ui.src.app.services.ui_service, while a change to ui.src.app.services.ui_service can't break ui.src.app.services.data_service.
- Position
- Below the diagonal: ui.src.app.services.ui_service uses a module listed above it, which is the healthy direction.
17→10 ui.src.app.services.volume_service uses ui.src.app.services.data_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.services.volume_service uses a type in ui.src.app.services.data_service.
- The types involved
ui.src.app.services.volume_service.VolumeService→ui.src.app.services.data_service.DataService
- Direction
- ui.src.app.services.volume_service uses ui.src.app.services.data_service, so a change to ui.src.app.services.data_service can break ui.src.app.services.volume_service, while a change to ui.src.app.services.volume_service can't break ui.src.app.services.data_service.
- Position
- Below the diagonal: ui.src.app.services.volume_service uses a module listed above it, which is the healthy direction.
18→8 native~app~UI uses native~shared✕
- Connections
- 14 pairs of types, where a type in native~app~UI uses a type in native~shared.
- The types involved
native~app~UI.Bridge→native~shared.Stringnative~app~UI.BridgeResponseData→native~shared.Stringnative~app~UI.MinHeightDefault→native~shared.Doublenative~app~UI.MinWidthDefault→native~shared.Doublenative~app~UI.ScaleDefault→native~shared.Doublenative~app~UI.StatusItem→native~shared.Doublenative~app~UI.StatusItem→native~shared.Stringnative~app~UI.StatusItemIconType→native~shared.Stringnative~app~UI.UI→native~shared.Doublenative~app~UI.UIDataBus→native~shared.Stringnative~app~UI.UIMode→native~shared.Stringnative~app~UI.UIState→native~shared.Doublenative~app~UI.ViewController→native~shared.Doublenative~app~UI.Window→native~shared.Double
- Direction
- native~app~UI uses native~shared, so a change to native~shared can break native~app~UI, while a change to native~app~UI can't break native~shared.
- Position
- Below the diagonal: native~app~UI uses a module listed above it, which is the healthy direction.
18→12 native~app~UI uses native~app~Extensions✕
- Connections
- 10 pairs of types, where a type in native~app~UI uses a type in native~app~Extensions.
- The types involved
native~app~UI.MinHeightDefault→native~app~Extensions.DefaultCodableStrategynative~app~UI.MinWidthDefault→native~app~Extensions.DefaultCodableStrategynative~app~UI.ScaleDefault→native~app~Extensions.DefaultCodableStrategynative~app~UI.StatusItem→native~app~Extensions.Boolnative~app~UI.StatusItem→native~app~Extensions.NSImagenative~app~UI.StatusItemIconTypeDefault→native~app~Extensions.DefaultCodableStrategynative~app~UI.UI→native~app~Extensions.Boolnative~app~UI.UIState→native~app~Extensions.Boolnative~app~UI.View→native~app~Extensions.Boolnative~app~UI.Window→native~app~Extensions.Bool
- Direction
- native~app~UI uses native~app~Extensions, so a change to native~app~Extensions can break native~app~UI, while a change to native~app~UI can't break native~app~Extensions.
- Position
- Below the diagonal: native~app~UI uses a module listed above it, which is the healthy direction.
18→20 native~app~UI uses native~app~DataBus part of a loop✕
- Connections
- 1 pair of types, where a type in native~app~UI uses a type in native~app~DataBus.
- The types involved
native~app~UI.UIDataBus→native~app~DataBus.DataBus
- Direction
- native~app~UI uses native~app~DataBus, so a change to native~app~DataBus can break native~app~UI, while a change to native~app~UI can't break native~app~DataBus.
- Position
- Above the diagonal, so 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→36 native~app~UI uses native~app part of a loop✕
- Connections
- 1 pair of types, where a type in native~app~UI uses a type in native~app.
- The types involved
native~app~UI.UIState→native~app.State
- Direction
- native~app~UI uses native~app, so a change to native~app can break native~app~UI, while a change to native~app~UI can't break native~app.
- Position
- Above the diagonal, so 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→3 ui.src.app.services.app_service uses ui.src.app.services.toast_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.services.app_service uses a type in ui.src.app.services.toast_service.
- The types involved
ui.src.app.services.app_service.ApplicationService→ui.src.app.services.toast_service.ToastService
- Direction
- ui.src.app.services.app_service uses ui.src.app.services.toast_service, so a change to ui.src.app.services.toast_service can break ui.src.app.services.app_service, while a change to ui.src.app.services.app_service can't break ui.src.app.services.toast_service.
- Position
- Below the diagonal: ui.src.app.services.app_service uses a module listed above it, which is the healthy direction.
19→10 ui.src.app.services.app_service uses ui.src.app.services.data_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.services.app_service uses a type in ui.src.app.services.data_service.
- The types involved
ui.src.app.services.app_service.ApplicationService→ui.src.app.services.data_service.DataService
- Direction
- ui.src.app.services.app_service uses ui.src.app.services.data_service, so a change to ui.src.app.services.data_service can break ui.src.app.services.app_service, while a change to ui.src.app.services.app_service can't break ui.src.app.services.data_service.
- Position
- Below the diagonal: ui.src.app.services.app_service uses a module listed above it, which is the healthy direction.
19→16 ui.src.app.services.app_service uses ui.src.app.services.ui_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.services.app_service uses a type in ui.src.app.services.ui_service.
- The types involved
ui.src.app.services.app_service.ApplicationService→ui.src.app.services.ui_service.UIService
- Direction
- ui.src.app.services.app_service uses ui.src.app.services.ui_service, so a change to ui.src.app.services.ui_service can break ui.src.app.services.app_service, while a change to ui.src.app.services.app_service can't break ui.src.app.services.ui_service.
- Position
- Below the diagonal: ui.src.app.services.app_service uses a module listed above it, which is the healthy direction.
19→40 ui.src.app.services.app_service uses ui.src.app.app_component part of a loop✕
- Connections
- 1 pair of types, where a type in ui.src.app.services.app_service uses a type in ui.src.app.app_component.
- The types involved
ui.src.app.services.app_service.ApplicationService→ui.src.app.app_component.AppComponent
- Direction
- ui.src.app.services.app_service uses ui.src.app.app_component, so a change to ui.src.app.app_component can break ui.src.app.services.app_service, while a change to ui.src.app.services.app_service can't break ui.src.app.app_component.
- Position
- Above the diagonal, so 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→8 native~app~DataBus uses native~shared✕
- Connections
- 2 pairs of types, where a type in native~app~DataBus uses a type in native~shared.
- The types involved
native~app~DataBus.DataBus→native~shared.Stringnative~app~DataBus.DataMethod→native~shared.String
- Direction
- native~app~DataBus uses native~shared, so a change to native~shared can break native~app~DataBus, while a change to native~app~DataBus can't break native~shared.
- Position
- Below the diagonal: native~app~DataBus uses a module listed above it, which is the healthy direction.
20→18 native~app~DataBus uses native~app~UI✕
- Connections
- 1 pair of types, where a type in native~app~DataBus uses a type in native~app~UI.
- The types involved
native~app~DataBus.DataBus→native~app~UI.Bridge
- Direction
- native~app~DataBus uses native~app~UI, so a change to native~app~UI can break native~app~DataBus, while a change to native~app~DataBus can't break native~app~UI.
- Position
- Below the diagonal: native~app~DataBus uses a module listed above it, which is the healthy direction.
21→19 ui.src.app.components.options.options_component uses ui.src.app.services.app_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.components.options.options_component uses a type in ui.src.app.services.app_service.
- The types involved
ui.src.app.components.options.options_component.OptionsComponent→ui.src.app.services.app_service.ApplicationService
- Direction
- ui.src.app.components.options.options_component uses ui.src.app.services.app_service, so a change to ui.src.app.services.app_service can break ui.src.app.components.options.options_component, while a change to ui.src.app.components.options.options_component can't break ui.src.app.services.app_service.
- Position
- Below the diagonal: ui.src.app.components.options.options_component uses a module listed above it, which is the healthy direction.
22→13 ui.src.app.sections.header.header_component uses ui.src.app.sections.settings.settings_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.header.header_component uses a type in ui.src.app.sections.settings.settings_service.
- The types involved
ui.src.app.sections.header.header_component.HeaderComponent→ui.src.app.sections.settings.settings_service.SettingsService
- Direction
- ui.src.app.sections.header.header_component uses ui.src.app.sections.settings.settings_service, so a change to ui.src.app.sections.settings.settings_service can break ui.src.app.sections.header.header_component, while a change to ui.src.app.sections.header.header_component can't break ui.src.app.sections.settings.settings_service.
- Position
- Below the diagonal: ui.src.app.sections.header.header_component uses a module listed above it, which is the healthy direction.
22→16 ui.src.app.sections.header.header_component uses ui.src.app.services.ui_service✕
- Connections
- 2 pairs of types, where a type in ui.src.app.sections.header.header_component uses a type in ui.src.app.services.ui_service.
- The types involved
ui.src.app.sections.header.header_component.HeaderComponent→ui.src.app.services.ui_service.UIModeui.src.app.sections.header.header_component.HeaderComponent→ui.src.app.services.ui_service.UIService
- Direction
- ui.src.app.sections.header.header_component uses ui.src.app.services.ui_service, so a change to ui.src.app.services.ui_service can break ui.src.app.sections.header.header_component, while a change to ui.src.app.sections.header.header_component can't break ui.src.app.services.ui_service.
- Position
- Below the diagonal: ui.src.app.sections.header.header_component uses a module listed above it, which is the healthy direction.
22→19 ui.src.app.sections.header.header_component uses ui.src.app.services.app_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.header.header_component uses a type in ui.src.app.services.app_service.
- The types involved
ui.src.app.sections.header.header_component.HeaderComponent→ui.src.app.services.app_service.ApplicationService
- Direction
- ui.src.app.sections.header.header_component uses ui.src.app.services.app_service, so a change to ui.src.app.services.app_service can break ui.src.app.sections.header.header_component, while a change to ui.src.app.sections.header.header_component can't break ui.src.app.services.app_service.
- Position
- Below the diagonal: ui.src.app.sections.header.header_component uses a module listed above it, which is the healthy direction.
23→1 ui.src.app.sections.outputs.outputs_component uses modules.components.src.services.colors_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.outputs.outputs_component uses a type in modules.components.src.services.colors_service.
- The types involved
ui.src.app.sections.outputs.outputs_component.OutputsComponent→modules.components.src.services.colors_service.ColorsService
- Direction
- ui.src.app.sections.outputs.outputs_component uses modules.components.src.services.colors_service, so a change to modules.components.src.services.colors_service can break ui.src.app.sections.outputs.outputs_component, while a change to ui.src.app.sections.outputs.outputs_component can't break modules.components.src.services.colors_service.
- Position
- Below the diagonal: ui.src.app.sections.outputs.outputs_component uses a module listed above it, which is the healthy direction.
23→19 ui.src.app.sections.outputs.outputs_component uses ui.src.app.services.app_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.outputs.outputs_component uses a type in ui.src.app.services.app_service.
- The types involved
ui.src.app.sections.outputs.outputs_component.OutputsComponent→ui.src.app.services.app_service.ApplicationService
- Direction
- ui.src.app.sections.outputs.outputs_component uses ui.src.app.services.app_service, so a change to ui.src.app.services.app_service can break ui.src.app.sections.outputs.outputs_component, while a change to ui.src.app.sections.outputs.outputs_component can't break ui.src.app.services.app_service.
- Position
- Below the diagonal: ui.src.app.sections.outputs.outputs_component uses a module listed above it, which is the healthy direction.
24→2 ui.src.app.sections.source.file.file_component uses modules.components.src.services.utilities_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.source.file.file_component uses a type in modules.components.src.services.utilities_service.
- The types involved
ui.src.app.sections.source.file.file_component.FileComponent→modules.components.src.services.utilities_service.UtilitiesService
- Direction
- ui.src.app.sections.source.file.file_component uses modules.components.src.services.utilities_service, so a change to modules.components.src.services.utilities_service can break ui.src.app.sections.source.file.file_component, while a change to ui.src.app.sections.source.file.file_component can't break modules.components.src.services.utilities_service.
- Position
- Below the diagonal: ui.src.app.sections.source.file.file_component uses a module listed above it, which is the healthy direction.
24→19 ui.src.app.sections.source.file.file_component uses ui.src.app.services.app_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.source.file.file_component uses a type in ui.src.app.services.app_service.
- The types involved
ui.src.app.sections.source.file.file_component.FileComponent→ui.src.app.services.app_service.ApplicationService
- Direction
- ui.src.app.sections.source.file.file_component uses ui.src.app.services.app_service, so a change to ui.src.app.services.app_service can break ui.src.app.sections.source.file.file_component, while a change to ui.src.app.sections.source.file.file_component can't break ui.src.app.services.app_service.
- Position
- Below the diagonal: ui.src.app.sections.source.file.file_component uses a module listed above it, which is the healthy direction.
25→16 ui.src.app.sections.volume.booster-balance.balance.balance_component uses ui.src.app.services.ui_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.volume.booster-balance.balance.balance_component uses a type in ui.src.app.services.ui_service.
- The types involved
ui.src.app.sections.volume.booster-balance.balance.balance_component.BalanceComponent→ui.src.app.services.ui_service.UIService
- Direction
- ui.src.app.sections.volume.booster-balance.balance.balance_component uses ui.src.app.services.ui_service, so a change to ui.src.app.services.ui_service can break ui.src.app.sections.volume.booster-balance.balance.balance_component, while a change to ui.src.app.sections.volume.booster-balance.balance.balance_component can't break ui.src.app.services.ui_service.
- Position
- Below the diagonal: ui.src.app.sections.volume.booster-balance.balance.balance_component uses a module listed above it, which is the healthy direction.
25→19 ui.src.app.sections.volume.booster-balance.balance.balance_component uses ui.src.app.services.app_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.volume.booster-balance.balance.balance_component uses a type in ui.src.app.services.app_service.
- The types involved
ui.src.app.sections.volume.booster-balance.balance.balance_component.BalanceComponent→ui.src.app.services.app_service.ApplicationService
- Direction
- ui.src.app.sections.volume.booster-balance.balance.balance_component uses ui.src.app.services.app_service, so a change to ui.src.app.services.app_service can break ui.src.app.sections.volume.booster-balance.balance.balance_component, while a change to ui.src.app.sections.volume.booster-balance.balance.balance_component can't break ui.src.app.services.app_service.
- Position
- Below the diagonal: ui.src.app.sections.volume.booster-balance.balance.balance_component uses a module listed above it, which is the healthy direction.
26→16 ui.src.app.sections.volume.booster-balance.booster.booster_component uses ui.src.app.services.ui_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.volume.booster-balance.booster.booster_component uses a type in ui.src.app.services.ui_service.
- The types involved
ui.src.app.sections.volume.booster-balance.booster.booster_component.BoosterComponent→ui.src.app.services.ui_service.UIService
- Direction
- ui.src.app.sections.volume.booster-balance.booster.booster_component uses ui.src.app.services.ui_service, so a change to ui.src.app.services.ui_service can break ui.src.app.sections.volume.booster-balance.booster.booster_component, while a change to ui.src.app.sections.volume.booster-balance.booster.booster_component can't break ui.src.app.services.ui_service.
- Position
- Below the diagonal: ui.src.app.sections.volume.booster-balance.booster.booster_component uses a module listed above it, which is the healthy direction.
26→19 ui.src.app.sections.volume.booster-balance.booster.booster_component uses ui.src.app.services.app_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.volume.booster-balance.booster.booster_component uses a type in ui.src.app.services.app_service.
- The types involved
ui.src.app.sections.volume.booster-balance.booster.booster_component.BoosterComponent→ui.src.app.services.app_service.ApplicationService
- Direction
- ui.src.app.sections.volume.booster-balance.booster.booster_component uses ui.src.app.services.app_service, so a change to ui.src.app.services.app_service can break ui.src.app.sections.volume.booster-balance.booster.booster_component, while a change to ui.src.app.sections.volume.booster-balance.booster.booster_component can't break ui.src.app.services.app_service.
- Position
- Below the diagonal: ui.src.app.sections.volume.booster-balance.booster.booster_component uses a module listed above it, which is the healthy direction.
27→2 ui.src.app.services.analytics_service uses modules.components.src.services.utilities_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.services.analytics_service uses a type in modules.components.src.services.utilities_service.
- The types involved
ui.src.app.services.analytics_service.AnalyticsService→modules.components.src.services.utilities_service.UtilitiesService
- Direction
- ui.src.app.services.analytics_service uses modules.components.src.services.utilities_service, so a change to modules.components.src.services.utilities_service can break ui.src.app.services.analytics_service, while a change to ui.src.app.services.analytics_service can't break modules.components.src.services.utilities_service.
- Position
- Below the diagonal: ui.src.app.services.analytics_service uses a module listed above it, which is the healthy direction.
27→16 ui.src.app.services.analytics_service uses ui.src.app.services.ui_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.services.analytics_service uses a type in ui.src.app.services.ui_service.
- The types involved
ui.src.app.services.analytics_service.AnalyticsService→ui.src.app.services.ui_service.UIService
- Direction
- ui.src.app.services.analytics_service uses ui.src.app.services.ui_service, so a change to ui.src.app.services.ui_service can break ui.src.app.services.analytics_service, while a change to ui.src.app.services.analytics_service can't break ui.src.app.services.ui_service.
- Position
- Below the diagonal: ui.src.app.services.analytics_service uses a module listed above it, which is the healthy direction.
27→19 ui.src.app.services.analytics_service uses ui.src.app.services.app_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.services.analytics_service uses a type in ui.src.app.services.app_service.
- The types involved
ui.src.app.services.analytics_service.AnalyticsService→ui.src.app.services.app_service.ApplicationService
- Direction
- ui.src.app.services.analytics_service uses ui.src.app.services.app_service, so a change to ui.src.app.services.app_service can break ui.src.app.services.analytics_service, while a change to ui.src.app.services.analytics_service can't break ui.src.app.services.app_service.
- Position
- Below the diagonal: ui.src.app.services.analytics_service uses a module listed above it, which is the healthy direction.
28→8 native~app~Audio uses native~shared✕
- Connections
- 34 pairs of types, where a type in native~app~Audio uses a type in native~shared. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
native~app~Audio.AdvancedEqualizer→native~shared.Doublenative~app~Audio.AdvancedEqualizer→native~shared.Stringnative~app~Audio.AdvancedEqualizerDataBus→native~shared.Stringnative~app~Audio.AdvancedEqualizerPreset→native~shared.Stringnative~app~Audio.AdvancedEqualizerPresetGains→native~shared.Doublenative~app~Audio.AdvancedEqualizerState→native~shared.Stringnative~app~Audio.AudioDeviceEvents→native~shared.Intnative~app~Audio.BasicEqualizer→native~shared.Doublenative~app~Audio.BasicEqualizer→native~shared.Intnative~app~Audio.BasicEqualizer→native~shared.Stringnative~app~Audio.BasicEqualizerDataBus→native~shared.Stringnative~app~Audio.BasicEqualizerPreset→native~shared.Stringnative~app~Audio.BasicEqualizerPresetGains→native~shared.Doublenative~app~Audio.BasicEqualizerState→native~shared.Stringnative~app~Audio.Driver→native~shared.Intnative~app~Audio.Driver→native~shared.Stringnative~app~Audio.Driver→native~shared.UInt32native~app~Audio.Effect→native~shared.Stringnative~app~Audio.EffectsDataBus→native~shared.Stringnative~app~Audio.Engine→native~shared.CircularBuffernative~app~Audio.Engine→native~shared.Doublenative~app~Audio.EngineDataBus→native~shared.Stringnative~app~Audio.Equalizer→native~shared.Doublenative~app~Audio.Equalizer→native~shared.Intnative~app~Audio.EqualizerType→native~shared.String
- Direction
- native~app~Audio uses native~shared, so a change to native~shared can break native~app~Audio, while a change to native~app~Audio can't break native~shared.
- Position
- Below the diagonal: native~app~Audio uses a module listed above it, which is the healthy direction.
28→12 native~app~Audio uses native~app~Extensions✕
- Connections
- 24 pairs of types, where a type in native~app~Audio uses a type in native~app~Extensions.
- The types involved
native~app~Audio.AdvancedEqualizer→native~app~Extensions.Boolnative~app~Audio.AdvancedEqualizerPreset→native~app~Extensions.Boolnative~app~Audio.AdvancedEqualizerPresetGains→native~app~Extensions.Boolnative~app~Audio.AdvancedEqualizerState→native~app~Extensions.Boolnative~app~Audio.AudioDeviceEvents→native~app~Extensions.AudioDevicenative~app~Audio.AudioDeviceEvents→native~app~Extensions.Boolnative~app~Audio.BasicEqualizer→native~app~Extensions.Boolnative~app~Audio.BasicEqualizerPreset→native~app~Extensions.Boolnative~app~Audio.BasicEqualizerPresetGains→native~app~Extensions.Boolnative~app~Audio.BasicEqualizerState→native~app~Extensions.Boolnative~app~Audio.Driver→native~app~Extensions.AudioDevicenative~app~Audio.Driver→native~app~Extensions.Boolnative~app~Audio.Effect→native~app~Extensions.Boolnative~app~Audio.Engine→native~app~Extensions.AVAudioEnginenative~app~Audio.EqualizersState→native~app~Extensions.Boolnative~app~Audio.InputSource→native~app~Extensions.AudioDevicenative~app~Audio.InputSource→native~app~Extensions.Boolnative~app~Audio.ListChangedDevices→native~app~Extensions.AudioDevicenative~app~Audio.Output→native~app~Extensions.AVAudioEnginenative~app~Audio.Output→native~app~Extensions.AudioDevicenative~app~Audio.Outputs→native~app~Extensions.AudioDevicenative~app~Audio.Outputs→native~app~Extensions.Boolnative~app~Audio.Volume→native~app~Extensions.Boolnative~app~Audio.VolumeState→native~app~Extensions.Bool
- Direction
- native~app~Audio uses native~app~Extensions, so a change to native~app~Extensions can break native~app~Audio, while a change to native~app~Audio can't break native~app~Extensions.
- Position
- Below the diagonal: native~app~Audio uses a module listed above it, which is the healthy direction.
28→18 native~app~Audio uses native~app~UI✕
- Connections
- 7 pairs of types, where a type in native~app~Audio uses a type in native~app~UI.
- The types involved
native~app~Audio.AdvancedEqualizerDataBus→native~app~UI.Bridgenative~app~Audio.BasicEqualizerDataBus→native~app~UI.Bridgenative~app~Audio.EffectsDataBus→native~app~UI.Bridgenative~app~Audio.EngineDataBus→native~app~UI.Bridgenative~app~Audio.EqualizersDataBus→native~app~UI.Bridgenative~app~Audio.OutputsDataBus→native~app~UI.Bridgenative~app~Audio.VolumeDataBus→native~app~UI.Bridge
- Direction
- native~app~Audio uses native~app~UI, so a change to native~app~UI can break native~app~Audio, while a change to native~app~Audio can't break native~app~UI.
- Position
- Below the diagonal: native~app~Audio uses a module listed above it, which is the healthy direction.
28→20 native~app~Audio uses native~app~DataBus✕
- Connections
- 7 pairs of types, where a type in native~app~Audio uses a type in native~app~DataBus.
- The types involved
native~app~Audio.AdvancedEqualizerDataBus→native~app~DataBus.DataBusnative~app~Audio.BasicEqualizerDataBus→native~app~DataBus.DataBusnative~app~Audio.EffectsDataBus→native~app~DataBus.DataBusnative~app~Audio.EngineDataBus→native~app~DataBus.DataBusnative~app~Audio.EqualizersDataBus→native~app~DataBus.DataBusnative~app~Audio.OutputsDataBus→native~app~DataBus.DataBusnative~app~Audio.VolumeDataBus→native~app~DataBus.DataBus
- Direction
- native~app~Audio uses native~app~DataBus, so a change to native~app~DataBus can break native~app~Audio, while a change to native~app~Audio can't break native~app~DataBus.
- Position
- Below the diagonal: native~app~Audio uses a module listed above it, which is the healthy direction.
28→36 native~app~Audio uses native~app part of a loop✕
- Connections
- 5 pairs of types, where a type in native~app~Audio uses a type in native~app.
- The types involved
native~app~Audio.AdvancedEqualizerState→native~app.Statenative~app~Audio.BasicEqualizerState→native~app.Statenative~app~Audio.EffectsState→native~app.Statenative~app~Audio.EqualizersState→native~app.Statenative~app~Audio.VolumeState→native~app.State
- Direction
- native~app~Audio uses native~app, so a change to native~app can break native~app~Audio, while a change to native~app~Audio can't break native~app.
- Position
- Above the diagonal, so 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→8 native~app~Settings uses native~shared✕
- Connections
- 2 pairs of types, where a type in native~app~Settings uses a type in native~shared.
- The types involved
native~app~Settings.IconMode→native~shared.Stringnative~app~Settings.SettingsDataBus→native~shared.String
- Direction
- native~app~Settings uses native~shared, so a change to native~shared can break native~app~Settings, while a change to native~app~Settings can't break native~shared.
- Position
- Below the diagonal: native~app~Settings uses a module listed above it, which is the healthy direction.
29→12 native~app~Settings uses native~app~Extensions✕
- Connections
- 2 pairs of types, where a type in native~app~Settings uses a type in native~app~Extensions.
- The types involved
native~app~Settings.Settings→native~app~Extensions.Boolnative~app~Settings.SettingsState→native~app~Extensions.Bool
- Direction
- native~app~Settings uses native~app~Extensions, so a change to native~app~Extensions can break native~app~Settings, while a change to native~app~Settings can't break native~app~Extensions.
- Position
- Below the diagonal: native~app~Settings uses a module listed above it, which is the healthy direction.
29→18 native~app~Settings uses native~app~UI✕
- Connections
- 1 pair of types, where a type in native~app~Settings uses a type in native~app~UI.
- The types involved
native~app~Settings.SettingsDataBus→native~app~UI.Bridge
- Direction
- native~app~Settings uses native~app~UI, so a change to native~app~UI can break native~app~Settings, while a change to native~app~Settings can't break native~app~UI.
- Position
- Below the diagonal: native~app~Settings uses a module listed above it, which is the healthy direction.
29→20 native~app~Settings uses native~app~DataBus✕
- Connections
- 1 pair of types, where a type in native~app~Settings uses a type in native~app~DataBus.
- The types involved
native~app~Settings.SettingsDataBus→native~app~DataBus.DataBus
- Direction
- native~app~Settings uses native~app~DataBus, so a change to native~app~DataBus can break native~app~Settings, while a change to native~app~Settings can't break native~app~DataBus.
- Position
- Below the diagonal: native~app~Settings uses a module listed above it, which is the healthy direction.
29→36 native~app~Settings uses native~app part of a loop✕
- Connections
- 1 pair of types, where a type in native~app~Settings uses a type in native~app.
- The types involved
native~app~Settings.SettingsState→native~app.State
- Direction
- native~app~Settings uses native~app, so a change to native~app can break native~app~Settings, while a change to native~app~Settings can't break native~app.
- Position
- Above the diagonal, so 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→8 native~app~Transition uses native~shared✕
- Connections
- 2 pairs of types, where a type in native~app~Transition uses a type in native~shared.
- The types involved
native~app~Transition.Transition→native~shared.Doublenative~app~Transition.TransitionDataBus→native~shared.String
- Direction
- native~app~Transition uses native~shared, so a change to native~shared can break native~app~Transition, while a change to native~app~Transition can't break native~shared.
- Position
- Below the diagonal: native~app~Transition uses a module listed above it, which is the healthy direction.
30→18 native~app~Transition uses native~app~UI✕
- Connections
- 1 pair of types, where a type in native~app~Transition uses a type in native~app~UI.
- The types involved
native~app~Transition.TransitionDataBus→native~app~UI.Bridge
- Direction
- native~app~Transition uses native~app~UI, so a change to native~app~UI can break native~app~Transition, while a change to native~app~Transition can't break native~app~UI.
- Position
- Below the diagonal: native~app~Transition uses a module listed above it, which is the healthy direction.
30→20 native~app~Transition uses native~app~DataBus✕
- Connections
- 1 pair of types, where a type in native~app~Transition uses a type in native~app~DataBus.
- The types involved
native~app~Transition.TransitionDataBus→native~app~DataBus.DataBus
- Direction
- native~app~Transition uses native~app~DataBus, so a change to native~app~DataBus can break native~app~Transition, while a change to native~app~Transition can't break native~app~DataBus.
- Position
- Below the diagonal: native~app~Transition uses a module listed above it, which is the healthy direction.
31→21 ui.src.app.components.options-dialog.options-dialog_component uses ui.src.app.components.options.options_component✕
- Connections
- 2 pairs of types, where a type in ui.src.app.components.options-dialog.options-dialog_component uses a type in ui.src.app.components.options.options_component.
- The types involved
ui.src.app.components.options-dialog.options-dialog_component.OptionsDialogComponent→ui.src.app.components.options.options_component.Optionsui.src.app.components.options-dialog.options-dialog_component.OptionsDialogData→ui.src.app.components.options.options_component.Options
- Direction
- ui.src.app.components.options-dialog.options-dialog_component uses ui.src.app.components.options.options_component, so a change to ui.src.app.components.options.options_component can break ui.src.app.components.options-dialog.options-dialog_component, while a change to ui.src.app.components.options-dialog.options-dialog_component can't break ui.src.app.components.options.options_component.
- Position
- Below the diagonal: ui.src.app.components.options-dialog.options-dialog_component uses a module listed above it, which is the healthy direction.
32→16 ui.src.app.sections.help.help_component uses ui.src.app.services.ui_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.help.help_component uses a type in ui.src.app.services.ui_service.
- The types involved
ui.src.app.sections.help.help_component.HelpComponent→ui.src.app.services.ui_service.UIService
- Direction
- ui.src.app.sections.help.help_component uses ui.src.app.services.ui_service, so a change to ui.src.app.services.ui_service can break ui.src.app.sections.help.help_component, while a change to ui.src.app.sections.help.help_component can't break ui.src.app.services.ui_service.
- Position
- Below the diagonal: ui.src.app.sections.help.help_component uses a module listed above it, which is the healthy direction.
32→19 ui.src.app.sections.help.help_component uses ui.src.app.services.app_service✕
- Connections
- 2 pairs of types, where a type in ui.src.app.sections.help.help_component uses a type in ui.src.app.services.app_service.
- The types involved
ui.src.app.sections.help.help_component.HelpComponent→ui.src.app.services.app_service.ApplicationServiceui.src.app.sections.help.help_component.HelpComponent→ui.src.app.services.app_service.Info
- Direction
- ui.src.app.sections.help.help_component uses ui.src.app.services.app_service, so a change to ui.src.app.services.app_service can break ui.src.app.sections.help.help_component, while a change to ui.src.app.sections.help.help_component can't break ui.src.app.services.app_service.
- Position
- Below the diagonal: ui.src.app.sections.help.help_component uses a module listed above it, which is the healthy direction.
32→21 ui.src.app.sections.help.help_component uses ui.src.app.components.options.options_component✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.help.help_component uses a type in ui.src.app.components.options.options_component.
- The types involved
ui.src.app.sections.help.help_component.HelpComponent→ui.src.app.components.options.options_component.Options
- Direction
- ui.src.app.sections.help.help_component uses ui.src.app.components.options.options_component, so a change to ui.src.app.components.options.options_component can break ui.src.app.sections.help.help_component, while a change to ui.src.app.sections.help.help_component can't break ui.src.app.components.options.options_component.
- Position
- Below the diagonal: ui.src.app.sections.help.help_component uses a module listed above it, which is the healthy direction.
33→6 ui.src.app.sections.settings.settings_component uses modules.components.src.components.knob.knob_component✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.settings.settings_component uses a type in modules.components.src.components.knob.knob_component.
- The types involved
ui.src.app.sections.settings.settings_component.SettingsComponent→modules.components.src.components.knob.knob_component.KnobControlStyle
- Direction
- ui.src.app.sections.settings.settings_component uses modules.components.src.components.knob.knob_component, so a change to modules.components.src.components.knob.knob_component can break ui.src.app.sections.settings.settings_component, while a change to ui.src.app.sections.settings.settings_component can't break modules.components.src.components.knob.knob_component.
- Position
- Below the diagonal: ui.src.app.sections.settings.settings_component uses a module listed above it, which is the healthy direction.
33→13 ui.src.app.sections.settings.settings_component uses ui.src.app.sections.settings.settings_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.settings.settings_component uses a type in ui.src.app.sections.settings.settings_service.
- The types involved
ui.src.app.sections.settings.settings_component.SettingsComponent→ui.src.app.sections.settings.settings_service.SettingsService
- Direction
- ui.src.app.sections.settings.settings_component uses ui.src.app.sections.settings.settings_service, so a change to ui.src.app.sections.settings.settings_service can break ui.src.app.sections.settings.settings_component, while a change to ui.src.app.sections.settings.settings_component can't break ui.src.app.sections.settings.settings_service.
- Position
- Below the diagonal: ui.src.app.sections.settings.settings_component uses a module listed above it, which is the healthy direction.
33→16 ui.src.app.sections.settings.settings_component uses ui.src.app.services.ui_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.settings.settings_component uses a type in ui.src.app.services.ui_service.
- The types involved
ui.src.app.sections.settings.settings_component.SettingsComponent→ui.src.app.services.ui_service.UIService
- Direction
- ui.src.app.sections.settings.settings_component uses ui.src.app.services.ui_service, so a change to ui.src.app.services.ui_service can break ui.src.app.sections.settings.settings_component, while a change to ui.src.app.sections.settings.settings_component can't break ui.src.app.services.ui_service.
- Position
- Below the diagonal: ui.src.app.sections.settings.settings_component uses a module listed above it, which is the healthy direction.
33→19 ui.src.app.sections.settings.settings_component uses ui.src.app.services.app_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.settings.settings_component uses a type in ui.src.app.services.app_service.
- The types involved
ui.src.app.sections.settings.settings_component.SettingsComponent→ui.src.app.services.app_service.ApplicationService
- Direction
- ui.src.app.sections.settings.settings_component uses ui.src.app.services.app_service, so a change to ui.src.app.services.app_service can break ui.src.app.sections.settings.settings_component, while a change to ui.src.app.sections.settings.settings_component can't break ui.src.app.services.app_service.
- Position
- Below the diagonal: ui.src.app.sections.settings.settings_component uses a module listed above it, which is the healthy direction.
33→21 ui.src.app.sections.settings.settings_component uses ui.src.app.components.options.options_component✕
- Connections
- 8 pairs of types, where a type in ui.src.app.sections.settings.settings_component uses a type in ui.src.app.components.options.options_component.
- The types involved
ui.src.app.sections.settings.settings_component.SettingsComponent→ui.src.app.components.options.options_component.ButtonOptionui.src.app.sections.settings.settings_component.SettingsComponent→ui.src.app.components.options.options_component.CheckboxOptionui.src.app.sections.settings.settings_component.SettingsComponent→ui.src.app.components.options.options_component.DividerOptionui.src.app.sections.settings.settings_component.SettingsComponent→ui.src.app.components.options.options_component.FlatSliderOptionui.src.app.sections.settings.settings_component.SettingsComponent→ui.src.app.components.options.options_component.LabelOptionui.src.app.sections.settings.settings_component.SettingsComponent→ui.src.app.components.options.options_component.Optionsui.src.app.sections.settings.settings_component.SettingsComponent→ui.src.app.components.options.options_component.SelectOptionui.src.app.sections.settings.settings_component.SettingsComponent→ui.src.app.components.options.options_component.ValueScreenOption
- Direction
- ui.src.app.sections.settings.settings_component uses ui.src.app.components.options.options_component, so a change to ui.src.app.components.options.options_component can break ui.src.app.sections.settings.settings_component, while a change to ui.src.app.sections.settings.settings_component can't break ui.src.app.components.options.options_component.
- Position
- Below the diagonal: ui.src.app.sections.settings.settings_component uses a module listed above it, which is the healthy direction.
33→27 ui.src.app.sections.settings.settings_component uses ui.src.app.services.analytics_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.settings.settings_component uses a type in ui.src.app.services.analytics_service.
- The types involved
ui.src.app.sections.settings.settings_component.SettingsComponent→ui.src.app.services.analytics_service.AnalyticsService
- Direction
- ui.src.app.sections.settings.settings_component uses ui.src.app.services.analytics_service, so a change to ui.src.app.services.analytics_service can break ui.src.app.sections.settings.settings_component, while a change to ui.src.app.sections.settings.settings_component can't break ui.src.app.services.analytics_service.
- Position
- Below the diagonal: ui.src.app.sections.settings.settings_component uses a module listed above it, which is the healthy direction.
34→8 native~app~Helpers uses native~shared✕
- Connections
- 13 pairs of types, where a type in native~app~Helpers uses a type in native~shared.
- The types involved
native~app~Helpers.Alert→native~shared.Stringnative~app~Helpers.Buffer.swift→native~shared.Doublenative~app~Helpers.CheckErr.swift→native~shared.Intnative~app~Helpers.CheckErr.swift→native~shared.Stringnative~app~Helpers.Console→native~shared.Intnative~app~Helpers.Console→native~shared.Stringnative~app~Helpers.File→native~shared.Stringnative~app~Helpers.Script→native~shared.Stringnative~app~Helpers.Sysctl→native~shared.Int32native~app~Helpers.Sysctl→native~shared.Int64native~app~Helpers.Sysctl→native~shared.Stringnative~app~Helpers.Sysctl→native~shared.UInt64native~app~Helpers.Time→native~shared.UInt
- Direction
- native~app~Helpers uses native~shared, so a change to native~shared can break native~app~Helpers, while a change to native~app~Helpers can't break native~shared.
- Position
- Below the diagonal: native~app~Helpers uses a module listed above it, which is the healthy direction.
34→12 native~app~Helpers uses native~app~Extensions✕
- Connections
- 4 pairs of types, where a type in native~app~Helpers uses a type in native~app~Extensions.
- The types involved
native~app~Helpers.Buffer.swift→native~app~Extensions.UnsafeMutableAudioBufferListPointernative~app~Helpers.File→native~app~Extensions.Boolnative~app~Helpers.File→native~app~Extensions.NSOpenPanelnative~app~Helpers.File→native~app~Extensions.NSSavePanel
- Direction
- native~app~Helpers uses native~app~Extensions, so a change to native~app~Extensions can break native~app~Helpers, while a change to native~app~Helpers can't break native~app~Extensions.
- Position
- Below the diagonal: native~app~Helpers uses a module listed above it, which is the healthy direction.
34→28 native~app~Helpers uses native~app~Audio✕
- Connections
- 1 pair of types, where a type in native~app~Helpers uses a type in native~app~Audio.
- The types involved
native~app~Helpers.eqMac2→native~app~Audio.AdvancedEqualizerPreset
- Direction
- native~app~Helpers uses native~app~Audio, so a change to native~app~Audio can break native~app~Helpers, while a change to native~app~Helpers can't break native~app~Audio.
- Position
- Below the diagonal: native~app~Helpers uses a module listed above it, which is the healthy direction.
35→21 ui.src.app.sections.effects.equalizers.equalizer_component uses ui.src.app.components.options.options_component✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.equalizer_component uses a type in ui.src.app.components.options.options_component.
- The types involved
ui.src.app.sections.effects.equalizers.equalizer_component.EqualizerComponent→ui.src.app.components.options.options_component.Options
- Direction
- ui.src.app.sections.effects.equalizers.equalizer_component uses ui.src.app.components.options.options_component, so a change to ui.src.app.components.options.options_component can break ui.src.app.sections.effects.equalizers.equalizer_component, while a change to ui.src.app.sections.effects.equalizers.equalizer_component can't break ui.src.app.components.options.options_component.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.equalizer_component uses a module listed above it, which is the healthy direction.
35→31 ui.src.app.sections.effects.equalizers.equalizer_component uses ui.src.app.components.options-dialog.options-dialog_component✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.equalizer_component uses a type in ui.src.app.components.options-dialog.options-dialog_component.
- The types involved
ui.src.app.sections.effects.equalizers.equalizer_component.EqualizerComponent→ui.src.app.components.options-dialog.options-dialog_component.OptionsDialogComponent
- Direction
- ui.src.app.sections.effects.equalizers.equalizer_component uses ui.src.app.components.options-dialog.options-dialog_component, so a change to ui.src.app.components.options-dialog.options-dialog_component can break ui.src.app.sections.effects.equalizers.equalizer_component, while a change to ui.src.app.sections.effects.equalizers.equalizer_component can't break ui.src.app.components.options-dialog.options-dialog_component.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.equalizer_component uses a module listed above it, which is the healthy direction.
36→8 native~app uses native~shared✕
- Connections
- 6 pairs of types, where a type in native~app uses a type in native~shared.
- The types involved
native~app.Application→native~shared.Stringnative~app.ApplicationDataBus→native~shared.Stringnative~app.Constants→native~shared.Doublenative~app.Constants→native~shared.Stringnative~app.Constants→native~shared.UIntnative~app.VolumeChangeDirection→native~shared.String
- Direction
- native~app uses native~shared, so a change to native~shared can break native~app, while a change to native~app can't break native~shared.
- Position
- Below the diagonal: native~app uses a module listed above it, which is the healthy direction.
36→12 native~app uses native~app~Extensions✕
- Connections
- 8 pairs of types, where a type in native~app uses a type in native~app~Extensions.
- The types involved
native~app.AppDelegate→native~app~Extensions.Boolnative~app.AppDelegate→native~app~Extensions.NSObjectnative~app.Application→native~app~Extensions.AudioDevicenative~app.Application→native~app~Extensions.Boolnative~app.ApplicationState→native~app~Extensions.Boolnative~app.Constants→native~app~Extensions.Boolnative~app.EventInterceptor→native~app~Extensions.Boolnative~app.VolumeDefault→native~app~Extensions.DefaultCodableStrategy
- Direction
- native~app uses native~app~Extensions, so a change to native~app~Extensions can break native~app, while a change to native~app can't break native~app~Extensions.
- Position
- Below the diagonal: native~app uses a module listed above it, which is the healthy direction.
36→18 native~app uses native~app~UI✕
- Connections
- 3 pairs of types, where a type in native~app uses a type in native~app~UI.
- The types involved
native~app.Application→native~app~UI.UInative~app.ApplicationDataBus→native~app~UI.Bridgenative~app.ApplicationState→native~app~UI.UIState
- Direction
- native~app uses native~app~UI, so a change to native~app~UI can break native~app, while a change to native~app can't break native~app~UI.
- Position
- Below the diagonal: native~app uses a module listed above it, which is the healthy direction.
36→20 native~app uses native~app~DataBus✕
- Connections
- 1 pair of types, where a type in native~app uses a type in native~app~DataBus.
- The types involved
native~app.ApplicationDataBus→native~app~DataBus.DataBus
- Direction
- native~app uses native~app~DataBus, so a change to native~app~DataBus can break native~app, while a change to native~app can't break native~app~DataBus.
- Position
- Below the diagonal: native~app uses a module listed above it, which is the healthy direction.
36→28 native~app uses native~app~Audio✕
- Connections
- 4 pairs of types, where a type in native~app uses a type in native~app~Audio.
- The types involved
native~app.Application→native~app~Audio.Enginenative~app.Application→native~app~Audio.Outputnative~app.ApplicationState→native~app~Audio.EffectsStatenative~app.VolumeDefault→native~app~Audio.VolumeState
- Direction
- native~app uses native~app~Audio, so a change to native~app~Audio can break native~app, while a change to native~app can't break native~app~Audio.
- Position
- Below the diagonal: native~app uses a module listed above it, which is the healthy direction.
36→29 native~app uses native~app~Settings✕
- Connections
- 2 pairs of types, where a type in native~app uses a type in native~app~Settings.
- The types involved
native~app.Application→native~app~Settings.Settingsnative~app.ApplicationState→native~app~Settings.SettingsState
- Direction
- native~app uses native~app~Settings, so a change to native~app~Settings can break native~app, while a change to native~app can't break native~app~Settings.
- Position
- Below the diagonal: native~app uses a module listed above it, which is the healthy direction.
36→34 native~app uses native~app~Helpers✕
- Connections
- 1 pair of types, where a type in native~app uses a type in native~app~Helpers.
- The types involved
native~app.AppDelegate→native~app~Helpers.Error
- Direction
- native~app uses native~app~Helpers, so a change to native~app~Helpers can break native~app, while a change to native~app can't break native~app~Helpers.
- Position
- Below the diagonal: native~app uses a module listed above it, which is the healthy direction.
37→1 ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses modules.components.src.services.colors_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses a type in modules.components.src.services.colors_service.
- The types involved
ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component.AdvancedEqualizerComponent→modules.components.src.services.colors_service.ColorsService
- Direction
- ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses modules.components.src.services.colors_service, so a change to modules.components.src.services.colors_service can break ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component, while a change to ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component can't break modules.components.src.services.colors_service.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses a module listed above it, which is the healthy direction.
37→3 ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses ui.src.app.services.toast_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses a type in ui.src.app.services.toast_service.
- The types involved
ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component.AdvancedEqualizerComponent→ui.src.app.services.toast_service.ToastService
- Direction
- ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses ui.src.app.services.toast_service, so a change to ui.src.app.services.toast_service can break ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component, while a change to ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component can't break ui.src.app.services.toast_service.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses a module listed above it, which is the healthy direction.
37→15 ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses ui.src.app.services.transitions_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses a type in ui.src.app.services.transitions_service.
- The types involved
ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component.AdvancedEqualizerComponent→ui.src.app.services.transitions_service.TransitionService
- Direction
- ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses ui.src.app.services.transitions_service, so a change to ui.src.app.services.transitions_service can break ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component, while a change to ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component can't break ui.src.app.services.transitions_service.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses a module listed above it, which is the healthy direction.
37→19 ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses ui.src.app.services.app_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses a type in ui.src.app.services.app_service.
- The types involved
ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component.AdvancedEqualizerComponent→ui.src.app.services.app_service.ApplicationService
- Direction
- ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses ui.src.app.services.app_service, so a change to ui.src.app.services.app_service can break ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component, while a change to ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component can't break ui.src.app.services.app_service.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses a module listed above it, which is the healthy direction.
37→21 ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses ui.src.app.components.options.options_component✕
- Connections
- 2 pairs of types, where a type in ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses a type in ui.src.app.components.options.options_component.
- The types involved
ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component.AdvancedEqualizerComponent→ui.src.app.components.options.options_component.CheckboxOptionui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component.AdvancedEqualizerComponent→ui.src.app.components.options.options_component.Options
- Direction
- ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses ui.src.app.components.options.options_component, so a change to ui.src.app.components.options.options_component can break ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component, while a change to ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component can't break ui.src.app.components.options.options_component.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses a module listed above it, which is the healthy direction.
37→35 ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses ui.src.app.sections.effects.equalizers.equalizer_component✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses a type in ui.src.app.sections.effects.equalizers.equalizer_component.
- The types involved
ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component.AdvancedEqualizerComponent→ui.src.app.sections.effects.equalizers.equalizer_component.EqualizerComponent
- Direction
- ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses ui.src.app.sections.effects.equalizers.equalizer_component, so a change to ui.src.app.sections.effects.equalizers.equalizer_component can break ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component, while a change to ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component can't break ui.src.app.sections.effects.equalizers.equalizer_component.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component uses a module listed above it, which is the healthy direction.
38→6 ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component uses modules.components.src.components.knob.knob_component✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component uses a type in modules.components.src.components.knob.knob_component.
- The types involved
ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component.BasicEqualizerComponent→modules.components.src.components.knob.knob_component.KnobValueChangedEvent
- Direction
- ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component uses modules.components.src.components.knob.knob_component, so a change to modules.components.src.components.knob.knob_component can break ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component, while a change to ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component can't break modules.components.src.components.knob.knob_component.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component uses a module listed above it, which is the healthy direction.
38→15 ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component uses ui.src.app.services.transitions_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component uses a type in ui.src.app.services.transitions_service.
- The types involved
ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component.BasicEqualizerComponent→ui.src.app.services.transitions_service.TransitionService
- Direction
- ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component uses ui.src.app.services.transitions_service, so a change to ui.src.app.services.transitions_service can break ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component, while a change to ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component can't break ui.src.app.services.transitions_service.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component uses a module listed above it, which is the healthy direction.
38→16 ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component uses ui.src.app.services.ui_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component uses a type in ui.src.app.services.ui_service.
- The types involved
ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component.BasicEqualizerComponent→ui.src.app.services.ui_service.UIService
- Direction
- ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component uses ui.src.app.services.ui_service, so a change to ui.src.app.services.ui_service can break ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component, while a change to ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component can't break ui.src.app.services.ui_service.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component uses a module listed above it, which is the healthy direction.
38→19 ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component uses ui.src.app.services.app_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component uses a type in ui.src.app.services.app_service.
- The types involved
ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component.BasicEqualizerComponent→ui.src.app.services.app_service.ApplicationService
- Direction
- ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component uses ui.src.app.services.app_service, so a change to ui.src.app.services.app_service can break ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component, while a change to ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component can't break ui.src.app.services.app_service.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component uses a module listed above it, which is the healthy direction.
38→35 ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component uses ui.src.app.sections.effects.equalizers.equalizer_component✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component uses a type in ui.src.app.sections.effects.equalizers.equalizer_component.
- The types involved
ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component.BasicEqualizerComponent→ui.src.app.sections.effects.equalizers.equalizer_component.EqualizerComponent
- Direction
- ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component uses ui.src.app.sections.effects.equalizers.equalizer_component, so a change to ui.src.app.sections.effects.equalizers.equalizer_component can break ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component, while a change to ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component can't break ui.src.app.sections.effects.equalizers.equalizer_component.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component uses a module listed above it, which is the healthy direction.
39→1 ui.src.app.sections.effects.equalizers.equalizers_component uses modules.components.src.services.colors_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.equalizers_component uses a type in modules.components.src.services.colors_service.
- The types involved
ui.src.app.sections.effects.equalizers.equalizers_component.EqualizersComponent→modules.components.src.services.colors_service.ColorsService
- Direction
- ui.src.app.sections.effects.equalizers.equalizers_component uses modules.components.src.services.colors_service, so a change to modules.components.src.services.colors_service can break ui.src.app.sections.effects.equalizers.equalizers_component, while a change to ui.src.app.sections.effects.equalizers.equalizers_component can't break modules.components.src.services.colors_service.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.equalizers_component uses a module listed above it, which is the healthy direction.
39→2 ui.src.app.sections.effects.equalizers.equalizers_component uses modules.components.src.services.utilities_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.equalizers_component uses a type in modules.components.src.services.utilities_service.
- The types involved
ui.src.app.sections.effects.equalizers.equalizers_component.EqualizersComponent→modules.components.src.services.utilities_service.UtilitiesService
- Direction
- ui.src.app.sections.effects.equalizers.equalizers_component uses modules.components.src.services.utilities_service, so a change to modules.components.src.services.utilities_service can break ui.src.app.sections.effects.equalizers.equalizers_component, while a change to ui.src.app.sections.effects.equalizers.equalizers_component can't break modules.components.src.services.utilities_service.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.equalizers_component uses a module listed above it, which is the healthy direction.
39→9 ui.src.app.sections.effects.equalizers.equalizers_component uses ui.src.app.sections.effects.equalizers.equalizers_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.equalizers_component uses a type in ui.src.app.sections.effects.equalizers.equalizers_service.
- The types involved
ui.src.app.sections.effects.equalizers.equalizers_component.EqualizersComponent→ui.src.app.sections.effects.equalizers.equalizers_service.EqualizersService
- Direction
- ui.src.app.sections.effects.equalizers.equalizers_component uses ui.src.app.sections.effects.equalizers.equalizers_service, so a change to ui.src.app.sections.effects.equalizers.equalizers_service can break ui.src.app.sections.effects.equalizers.equalizers_component, while a change to ui.src.app.sections.effects.equalizers.equalizers_component can't break ui.src.app.sections.effects.equalizers.equalizers_service.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.equalizers_component uses a module listed above it, which is the healthy direction.
39→16 ui.src.app.sections.effects.equalizers.equalizers_component uses ui.src.app.services.ui_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.equalizers_component uses a type in ui.src.app.services.ui_service.
- The types involved
ui.src.app.sections.effects.equalizers.equalizers_component.EqualizersComponent→ui.src.app.services.ui_service.UIService
- Direction
- ui.src.app.sections.effects.equalizers.equalizers_component uses ui.src.app.services.ui_service, so a change to ui.src.app.services.ui_service can break ui.src.app.sections.effects.equalizers.equalizers_component, while a change to ui.src.app.sections.effects.equalizers.equalizers_component can't break ui.src.app.services.ui_service.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.equalizers_component uses a module listed above it, which is the healthy direction.
39→19 ui.src.app.sections.effects.equalizers.equalizers_component uses ui.src.app.services.app_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.equalizers_component uses a type in ui.src.app.services.app_service.
- The types involved
ui.src.app.sections.effects.equalizers.equalizers_component.EqualizersComponent→ui.src.app.services.app_service.ApplicationService
- Direction
- ui.src.app.sections.effects.equalizers.equalizers_component uses ui.src.app.services.app_service, so a change to ui.src.app.services.app_service can break ui.src.app.sections.effects.equalizers.equalizers_component, while a change to ui.src.app.sections.effects.equalizers.equalizers_component can't break ui.src.app.services.app_service.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.equalizers_component uses a module listed above it, which is the healthy direction.
39→31 ui.src.app.sections.effects.equalizers.equalizers_component uses ui.src.app.components.options-dialog.options-dialog_component✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.equalizers_component uses a type in ui.src.app.components.options-dialog.options-dialog_component.
- The types involved
ui.src.app.sections.effects.equalizers.equalizers_component.EqualizersComponent→ui.src.app.components.options-dialog.options-dialog_component.OptionsDialogComponent
- Direction
- ui.src.app.sections.effects.equalizers.equalizers_component uses ui.src.app.components.options-dialog.options-dialog_component, so a change to ui.src.app.components.options-dialog.options-dialog_component can break ui.src.app.sections.effects.equalizers.equalizers_component, while a change to ui.src.app.sections.effects.equalizers.equalizers_component can't break ui.src.app.components.options-dialog.options-dialog_component.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.equalizers_component uses a module listed above it, which is the healthy direction.
39→35 ui.src.app.sections.effects.equalizers.equalizers_component uses ui.src.app.sections.effects.equalizers.equalizer_component✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.equalizers_component uses a type in ui.src.app.sections.effects.equalizers.equalizer_component.
- The types involved
ui.src.app.sections.effects.equalizers.equalizers_component.EqualizersComponent→ui.src.app.sections.effects.equalizers.equalizer_component.EqualizerComponent
- Direction
- ui.src.app.sections.effects.equalizers.equalizers_component uses ui.src.app.sections.effects.equalizers.equalizer_component, so a change to ui.src.app.sections.effects.equalizers.equalizer_component can break ui.src.app.sections.effects.equalizers.equalizers_component, while a change to ui.src.app.sections.effects.equalizers.equalizers_component can't break ui.src.app.sections.effects.equalizers.equalizer_component.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.equalizers_component uses a module listed above it, which is the healthy direction.
39→37 ui.src.app.sections.effects.equalizers.equalizers_component uses ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.equalizers_component uses a type in ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component.
- The types involved
ui.src.app.sections.effects.equalizers.equalizers_component.EqualizersComponent→ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component.AdvancedEqualizerComponent
- Direction
- ui.src.app.sections.effects.equalizers.equalizers_component uses ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component, so a change to ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component can break ui.src.app.sections.effects.equalizers.equalizers_component, while a change to ui.src.app.sections.effects.equalizers.equalizers_component can't break ui.src.app.sections.effects.equalizers.advanced-equalizer.advanced-equalizer_component.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.equalizers_component uses a module listed above it, which is the healthy direction.
39→38 ui.src.app.sections.effects.equalizers.equalizers_component uses ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component✕
- Connections
- 1 pair of types, where a type in ui.src.app.sections.effects.equalizers.equalizers_component uses a type in ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component.
- The types involved
ui.src.app.sections.effects.equalizers.equalizers_component.EqualizersComponent→ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component.BasicEqualizerComponent
- Direction
- ui.src.app.sections.effects.equalizers.equalizers_component uses ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component, so a change to ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component can break ui.src.app.sections.effects.equalizers.equalizers_component, while a change to ui.src.app.sections.effects.equalizers.equalizers_component can't break ui.src.app.sections.effects.equalizers.basic-equalizer.basic-equalizer_component.
- Position
- Below the diagonal: ui.src.app.sections.effects.equalizers.equalizers_component uses a module listed above it, which is the healthy direction.
40→2 ui.src.app.app_component uses modules.components.src.services.utilities_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.app_component uses a type in modules.components.src.services.utilities_service.
- The types involved
ui.src.app.app_component.AppComponent→modules.components.src.services.utilities_service.UtilitiesService
- Direction
- ui.src.app.app_component uses modules.components.src.services.utilities_service, so a change to modules.components.src.services.utilities_service can break ui.src.app.app_component, while a change to ui.src.app.app_component can't break modules.components.src.services.utilities_service.
- Position
- Below the diagonal: ui.src.app.app_component uses a module listed above it, which is the healthy direction.
40→3 ui.src.app.app_component uses ui.src.app.services.toast_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.app_component uses a type in ui.src.app.services.toast_service.
- The types involved
ui.src.app.app_component.AppComponent→ui.src.app.services.toast_service.ToastService
- Direction
- ui.src.app.app_component uses ui.src.app.services.toast_service, so a change to ui.src.app.services.toast_service can break ui.src.app.app_component, while a change to ui.src.app.app_component can't break ui.src.app.services.toast_service.
- Position
- Below the diagonal: ui.src.app.app_component uses a module listed above it, which is the healthy direction.
40→13 ui.src.app.app_component uses ui.src.app.sections.settings.settings_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.app_component uses a type in ui.src.app.sections.settings.settings_service.
- The types involved
ui.src.app.app_component.AppComponent→ui.src.app.sections.settings.settings_service.SettingsService
- Direction
- ui.src.app.app_component uses ui.src.app.sections.settings.settings_service, so a change to ui.src.app.sections.settings.settings_service can break ui.src.app.app_component, while a change to ui.src.app.app_component can't break ui.src.app.sections.settings.settings_service.
- Position
- Below the diagonal: ui.src.app.app_component uses a module listed above it, which is the healthy direction.
40→15 ui.src.app.app_component uses ui.src.app.services.transitions_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.app_component uses a type in ui.src.app.services.transitions_service.
- The types involved
ui.src.app.app_component.AppComponent→ui.src.app.services.transitions_service.TransitionService
- Direction
- ui.src.app.app_component uses ui.src.app.services.transitions_service, so a change to ui.src.app.services.transitions_service can break ui.src.app.app_component, while a change to ui.src.app.app_component can't break ui.src.app.services.transitions_service.
- Position
- Below the diagonal: ui.src.app.app_component uses a module listed above it, which is the healthy direction.
40→16 ui.src.app.app_component uses ui.src.app.services.ui_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.app_component uses a type in ui.src.app.services.ui_service.
- The types involved
ui.src.app.app_component.AppComponent→ui.src.app.services.ui_service.UIService
- Direction
- ui.src.app.app_component uses ui.src.app.services.ui_service, so a change to ui.src.app.services.ui_service can break ui.src.app.app_component, while a change to ui.src.app.app_component can't break ui.src.app.services.ui_service.
- Position
- Below the diagonal: ui.src.app.app_component uses a module listed above it, which is the healthy direction.
40→19 ui.src.app.app_component uses ui.src.app.services.app_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.app_component uses a type in ui.src.app.services.app_service.
- The types involved
ui.src.app.app_component.AppComponent→ui.src.app.services.app_service.ApplicationService
- Direction
- ui.src.app.app_component uses ui.src.app.services.app_service, so a change to ui.src.app.services.app_service can break ui.src.app.app_component, while a change to ui.src.app.app_component can't break ui.src.app.services.app_service.
- Position
- Below the diagonal: ui.src.app.app_component uses a module listed above it, which is the healthy direction.
40→22 ui.src.app.app_component uses ui.src.app.sections.header.header_component✕
- Connections
- 1 pair of types, where a type in ui.src.app.app_component uses a type in ui.src.app.sections.header.header_component.
- The types involved
ui.src.app.app_component.AppComponent→ui.src.app.sections.header.header_component.HeaderComponent
- Direction
- ui.src.app.app_component uses ui.src.app.sections.header.header_component, so a change to ui.src.app.sections.header.header_component can break ui.src.app.app_component, while a change to ui.src.app.app_component can't break ui.src.app.sections.header.header_component.
- Position
- Below the diagonal: ui.src.app.app_component uses a module listed above it, which is the healthy direction.
40→23 ui.src.app.app_component uses ui.src.app.sections.outputs.outputs_component✕
- Connections
- 1 pair of types, where a type in ui.src.app.app_component uses a type in ui.src.app.sections.outputs.outputs_component.
- The types involved
ui.src.app.app_component.AppComponent→ui.src.app.sections.outputs.outputs_component.OutputsComponent
- Direction
- ui.src.app.app_component uses ui.src.app.sections.outputs.outputs_component, so a change to ui.src.app.sections.outputs.outputs_component can break ui.src.app.app_component, while a change to ui.src.app.app_component can't break ui.src.app.sections.outputs.outputs_component.
- Position
- Below the diagonal: ui.src.app.app_component uses a module listed above it, which is the healthy direction.
40→27 ui.src.app.app_component uses ui.src.app.services.analytics_service✕
- Connections
- 1 pair of types, where a type in ui.src.app.app_component uses a type in ui.src.app.services.analytics_service.
- The types involved
ui.src.app.app_component.AppComponent→ui.src.app.services.analytics_service.AnalyticsService
- Direction
- ui.src.app.app_component uses ui.src.app.services.analytics_service, so a change to ui.src.app.services.analytics_service can break ui.src.app.app_component, while a change to ui.src.app.app_component can't break ui.src.app.services.analytics_service.
- Position
- Below the diagonal: ui.src.app.app_component uses a module listed above it, which is the healthy direction.
40→39 ui.src.app.app_component uses ui.src.app.sections.effects.equalizers.equalizers_component✕
- Connections
- 1 pair of types, where a type in ui.src.app.app_component uses a type in ui.src.app.sections.effects.equalizers.equalizers_component.
- The types involved
ui.src.app.app_component.AppComponent→ui.src.app.sections.effects.equalizers.equalizers_component.EqualizersComponent
- Direction
- ui.src.app.app_component uses ui.src.app.sections.effects.equalizers.equalizers_component, so a change to ui.src.app.sections.effects.equalizers.equalizers_component can break ui.src.app.app_component, while a change to ui.src.app.app_component can't break ui.src.app.sections.effects.equalizers.equalizers_component.
- Position
- Below the diagonal: ui.src.app.app_component 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 — Accessibility
At a glance — Performance
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj; Resolve the 61 Orphaned file finding(s) in Knowledge Freshness — start with utilities.service.ts (2), Constants.swift (2), Application.swift; Add a CI workflow that builds and runs the test suite on every push/PR.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj. | +4.9 pts | Low | ADR Quality |
| Resolve the 61 Orphaned file finding(s) in Knowledge Freshness — start with utilities.service.ts (2), Constants.swift (2), Application.swift. | +4.7 pts | Medium | Knowledge Freshness |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +4.0 pts | Medium | CI/CD gates |
| Add tests that import the unreached modules (directly or through their public entry). | +4.0 pts | Medium | Test Coverage |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.4 pts | Medium | Architecture documentation |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +3.1 pts | Medium | Keyboard semantics |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +2.5 pts | Medium | Forms & labels |
| Add a test runner (vitest / jest / playwright) and `tsc --noEmit` as package.json scripts and run them in CI. | +1.8 pts | Medium | Tooling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| native/app/Source/Application.swift | 6.0 | Mixed | Explicit Debt: TodoComment |
| native/driver/Source/EQMDevice.swift | 7.1 | Mixed | Cyclomatic Complexity: EQMDevice.getPropertyData (cyclomatic 42) |
| native/driver/Source/EQMControl.swift | 7.1 | Mixed | Cyclomatic Complexity: EQMControl.getPropertyData (cyclomatic 40) |
| native/app/Source/Audio/Effects/Equalizers/Advanced/AdvancedEqualizer.swift | 7.2 | Mixed | Code Duplication: Edited copy of a member (11 corresponding lines) |
| native/app/Source/UI/UIDataBus.swift | 7.4 | Mixed | Cyclomatic Complexity: UIDataBus.init (cyclomatic 17) |
| native/app/Source/Audio/Effects/Equalizers/Advanced/AdvancedEqualizerDataBus.swift | 7.8 | Mixed | Cyclomatic Complexity: AdvancedEqualizerDataBus.init (cyclomatic 19) |
| native/app/Source/ApplicationDataBus.swift | 7.8 | Mixed | Cyclomatic Complexity: ApplicationDataBus.init (cyclomatic 17) |
| native/app/Source/Audio/Volume/Volume.swift | 7.8 | Mixed | Cognitive Complexity: Volume.gain (cognitive 17) |
| native/shared/Source/CircularBuffer.swift | 7.8 | Mixed | Code Duplication: Edited copy of a member (30 corresponding lines) |
| .nvmrc | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: Node.js 14 |
| ui/src/app/sections/effects/equalizers/basic-equalizer/basic-equalizer.component.ts | 8.2 | Near-clean | Explicit Debt: TodoComment |
| ui/src/app/sections/effects/equalizers/advanced-equalizer/advanced-equalizer.component.ts | 8.2 | Near-clean | Explicit Debt: TodoComment |
| native/driver/Source/EQMStream.swift | 8.5 | Near-clean | Cyclomatic Complexity: EQMStream.getPropertyData (cyclomatic 17) |
| modules/components/src/components/knob/knob.component.ts | 8.5 | Near-clean | Cognitive Complexity: KnobComponent.mousemove (cognitive 30) |
| native/app/Source/EventInterceptor.swift | 8.5 | Near-clean | Cognitive Complexity: EventInterceptor.sendEvent (cognitive 17) |
| modules/components/src/components/flat-slider/flat-slider.component.ts | 8.5 | Near-clean | Cognitive Complexity: FlatSliderComponent.mouseWheel (cognitive 17) |
| ui/src/app/services/ui.service.ts | 8.5 | Near-clean | God Classes: TooManyMethods: UIService |
| native/app/Source/Audio/AudioDeviceEvents.swift | 8.5 | Near-clean | Code Duplication: Edited copy of a member (7 corresponding lines) |
| native/app/Source/AppDelegate.swift | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: AppDelegate (LCOM4 8) |
| native/app/Source/UI/Window.swift | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: Window (LCOM4 6) |
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 51 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 — 51 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, 174 of 201 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: test source is present (.swift) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.swift) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
- 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 (15 contributor(s) across 615 commit(s) sampled, automation and bot accounts excluded). One of them holds 96% of the history; the other 14 hold 0.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — 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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their 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 — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- 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 428 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.
- D30 Dependency Vulnerabilities — 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 scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies.
- 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. `native/driver/Source/EQMDriver.swift` 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.
- D43 Malicious Dependencies — 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 scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies.
- 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.
- 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 (start). the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / 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, c, objectivec is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Swift, c, objectivec is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Objective-C is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
- 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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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
7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was EQMDevice.getPropertyData at 42. A further 3 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 EQMDevice.getPropertyDataSize at 38 — 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: native/app/Source/Audio/AudioDeviceEvents.swift (AudioDeviceEvents.getEventEmitterFromEventType at 17), native/driver/Source/EQMObject.swift (EQMObjectProperty.write at 17). 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 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with EQMDevice.getPropertyData (cyclomatic 42), EQMControl.getPropertyData (cyclomatic 40), EQMControl.getPropertyDataSize (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 7 together lifts Cyclomatic Complexity from 8.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
15 method(s) exceeded the cognitive complexity threshold of 15; the worst was EQMControl.getPropertyData at 44.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with EQMControl.getPropertyData (cognitive 44), AdvancedEqualizerDataBus.init (cognitive 37). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 7.7 to about 8.1/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
5 god class(es) detected.
What to do
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with EQMDevice.swift, UIDataBus.swift. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with ui.service.ts, Application.swift. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with Application.swift. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
4 duplicated block group(s) detected. 1.3 % of the production lines (198 of 15,323) are in a reported copy. A further 6 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 (40% 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 2 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with AdvancedEqualizer.swift (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (30 corresponding lines) finding(s) in Code Duplication — start with CircularBuffer.swift. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with AudioDeviceEvents.swift. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
2 production modules (npm+SwiftPM), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
3 of 22 classes have LCOM4 above 3.
What to do
- Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with AppDelegate.swift, Window.swift, StringExtensions.swift. — One of this dimension's main actionable groups (3 warning-level).
D12 · Dependency Hygiene
4 outdated direct SwiftPM dependencies, 0 pinning defect(s). 10 of 11 direct dependencies had their releases listed (0 naming no readable repository, 1 pinned to a branch or a revision rather than a version). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question. 10 third-party CocoaPods resolved by a committed Podfile.lock were graded against the CocoaPods trunk (cdn.cocoapods.org): a pod is behind only when the trunk lists a newer release on the same major, which `pod update` reaches under a `~>` requirement. A pod sourced from a path, git URL or local podspec has no trunk release to compare and is not asked about. Carthage dependencies are not graded.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
5 deducted task-comment markers across 15323 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 5 TodoComment finding(s) in Explicit Debt — start with Application.swift (3), basic-equalizer.component.ts, advanced-equalizer.component.ts. — One of this dimension's main actionable groups (5 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 5 build units (SwiftPM, Xcode, npm) flagged as possibly oversized/incoherent.
D27 · Navigability
48 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated. 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.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D34 · Knowledge Freshness
64 of 64 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is modules/components/src/components/icon/icons.ts. Counted over 64 of the 192 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 61 Orphaned file finding(s) in Knowledge Freshness — start with utilities.service.ts (2), Constants.swift (2), Application.swift. — One of this dimension's main actionable groups (61 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with icons.ts, EQMDevice.swift, EQMInterface.swift. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 12 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with .nvmrc. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AC1 · Text alternatives
AC2 · Forms & labels
- This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×9) — modules/components/src/components/dropdown/dropdown.component.html:9, modules/components/src/components/dropdown/dropdown.component.html:12, modules/components/src/components/toggle/toggle.component.html:1, …
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — modules/components/src/components/input-field/input-field.component.html:2
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — ui/src/index.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×13) — modules/components/src/components/button/button.component.html:1, modules/components/src/components/dropdown/dropdown.component.html:9, modules/components/src/components/dropdown/dropdown.component.html:12, …
- This <div> binds double-click and nothing else. No click, no key handler, and no tabindex="0", so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabindex="0" + a key handler alongside the double-click. (×3) — modules/components/src/components/flat-slider/flat-slider.component.html:11, modules/components/src/components/knob/knob.component.html:1, modules/components/src/components/skeuomorph-slider/skeuomorph-slider.component.html:3
- This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus. — ui/src/app/sections/header/header.component.html:2
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC6 · Visual & motion safety
- `.loader #loader-wave` moves (`animation: animateWave 2400ms linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — ui/src/index.html:34
- `.container .input-field:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — modules/components/src/components/input-field/input-field.component.scss:26
- `.loader #wave` moves (`animation: animateWave 2400ms linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — modules/components/src/components/loading/loading.component.scss:15
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- 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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `native/app`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `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`. — package.json:29
What to do
- Run what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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
- 5 duplicated blocks under ui/src/app/sections/ have copies in at least two of the sibling directories effects, outputs, source — 3 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — ui/src/app/sections/effects/equalizers/equalizers.component.ts:106
- modules/components/src/components/flat-slider/flat-slider.component.ts:103 · modules/components/src/components/skeuomorph-slider/skeuomorph-slider.component.ts:63 — the two spans are one implementation copied and then locally edited — 678 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. — modules/components/src/components/flat-slider/flat-slider.component.ts:103
- ui/src/app/sections/effects/equalizers/advanced-equalizer/advanced-equalizer.component.ts:63 · ui/src/app/sections/effects/equalizers/basic-equalizer/basic-equalizer.component.ts:31 — the two spans are one implementation copied and then locally edited — 285 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. — ui/src/app/sections/effects/equalizers/advanced-equalizer/advanced-equalizer.component.ts:63
- ui/src/app/sections/effects/equalizers/advanced-equalizer/advanced-equalizer.service.ts:22 · ui/src/app/sections/effects/equalizers/basic-equalizer/basic-equalizer.service.ts:28 — the two spans are one implementation copied and then locally edited — 264 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. — ui/src/app/sections/effects/equalizers/advanced-equalizer/advanced-equalizer.service.ts:22
- ui/src/app/app.component.ts:76 · ui/src/app/app.component.ts:104 — 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. — ui/src/app/app.component.ts:76
- ui/src/app/sections/source/input/input.service.ts:14 · ui/src/app/sections/source/source.service.ts:12 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — ui/src/app/sections/source/input/input.service.ts:14
- ui/src/app/sections/settings/settings.component.ts:254 · ui/src/app/sections/settings/settings.component.ts:272 — 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. — ui/src/app/sections/settings/settings.component.ts:254
- ui/src/app/sections/effects/effect.service.ts:4 · ui/src/app/sections/source/file/file.service.ts:4 — 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. — ui/src/app/sections/effects/effect.service.ts:4
- ui/src/app/components/confirm-dialog/confirm-dialog.component.ts:21 · ui/src/app/components/options-dialog/options-dialog.component.ts:18 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — ui/src/app/components/confirm-dialog/confirm-dialog.component.ts:21
- ui/src/app/sections/outputs/outputs.service.ts:25 · ui/src/app/sections/source/input/input.service.ts:4 — 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. — ui/src/app/sections/outputs/outputs.service.ts:25
- modules/components/src/components/knob/knob.component.ts:223 · modules/components/src/components/skeuomorph-slider/skeuomorph-slider.component.ts:188 — 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. — modules/components/src/components/knob/knob.component.ts:223
- modules/components/src/services/utilities.service.ts:67 · ui/src/app/services/utilities.service.ts:67 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — modules/components/src/services/utilities.service.ts:67
- ui/src/app/sections/effects/equalizers/equalizers.service.ts:19 · ui/src/app/sections/source/input/input.service.ts:14 · ui/src/app/sections/source/source.service.ts:12 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — ui/src/app/sections/effects/equalizers/equalizers.service.ts:19
- ui/src/app/sections/settings/settings.service.ts:23 · ui/src/app/sections/volume/booster-balance/booster/booster.service.ts:15 · ui/src/app/services/ui.service.ts:112 · ui/src/app/services/ui.service.ts:153 — the 4 copies are spread across 3 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. — ui/src/app/sections/settings/settings.service.ts:23
- ui/src/app/services/ui.service.ts:106 · ui/src/app/services/ui.service.ts:121 — 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. — ui/src/app/services/ui.service.ts:106
- ui/src/app/sections/settings/settings.service.ts:33 · ui/src/app/sections/settings/settings.service.ts:42 · ui/src/app/sections/settings/settings.service.ts:51 · ui/src/app/sections/settings/settings.service.ts:60 — all 4 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. — ui/src/app/sections/settings/settings.service.ts:33
- ui/src/app/services/ui.service.ts:218 · ui/src/app/services/ui.service.ts:227 — 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. — ui/src/app/services/ui.service.ts:218
- modules/components/src/components/knob/knob.component.ts:305 · modules/components/src/components/knob/knob.component.ts:313 — 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. — modules/components/src/components/knob/knob.component.ts:305
- ui/src/app/services/data.service.ts:44 · ui/src/app/services/data.service.ts:51 — 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. — ui/src/app/services/data.service.ts:44
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
- mousemove has cyclomatic complexity 12 and cognitive complexity 26; 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. — modules/components/src/components/knob/knob.component.ts:154
R3 · Large Files
R4 · Test Coverage
- 0% of 88 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
- test ✗ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add a test runner (vitest / jest / playwright) and `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 2 application, 5 tooling and 0 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (2 application, 5 tooling, 0 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 (×3) — ui/src/app/services/context.service.ts, ui/src/app/services/logger.service.ts, ui/src/app/services/types.service.ts
- Nothing imports this binding — it is safe to review for removal. — ui/src/app/services/ui.service.ts:23
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
- Declared in the root 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. (×12)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- ui/src/app/sections/effects/equalizers/equalizers.component.ts → ui/src/app/sections/effects/equalizers/advanced-equalizer/advanced-equalizer.component.ts → ui/src/app/sections/effects/equalizers/advanced-equalizer/advanced-equalizer.service.ts → ui/src/app/sections/effects/equalizers/equalizers.service.ts → ui/src/app/sections/effects/equalizers/equalizers.component.ts (one verified cycle inside a mutually-dependent group of 11 files) — ui/src/app/sections/effects/equalizers/equalizers.component.ts:4
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — ui/src/app/sections/source/file/file.component.ts:93
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
- 0/4 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
- ~2.3 `!` null assertions per 1k TypeScript source lines — 17 assertion(s) across the 7449 source line(s) of the 94 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: modules/components/src/components/carousel/carousel.component.ts (4), modules/components/src/components/dropdown/dropdown.component.ts (3), modules/components/src/components/knob/knob.component.ts (2). 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 `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 60% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 91% | Exemplary | Solid. |
| Maturity | 41% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 21% | Critical — gated by R4, R6, P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 90% | Exemplary | Solid. |
| Accessibility | 36% | Weak — gated by AC2, AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 3 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 — 73 check(s) not relevant to this codebase
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — Not applicable: Angular's root injector cannot see a component-level provider, so a root service asking for one fails with NullInjectorError instead of capturing it.
- 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 42% of this repository's production lines — swift (8,883 lines), c (25 lines), objectivec (12 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
- AX8 Test isolation — no test/production split to check
- 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 start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / 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.
- D10 Test Quality — ~0 lines of test source are present (.swift) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — no .swift test runner
- D14 License Compliance — Package licences not graded — dependencies declared to CocoaPods
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency does not read html yet; not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Swift surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .swift source were not judged.
- D25 ADR Conformance — no ADRs to check
- 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) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- 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.
- 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 included — suite not readable by the collector
- 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 2 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (command argument 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — no CI workflow found
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the 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 — no package-lock.json — dependency freshness not measured (would require an npm lockfile); 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.
- X1 Async correctness — X1 reached only 42% of this repository's production lines — swift (8,883 lines), c (25 lines), objectivec (12 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 42% of this repository's production lines — swift (8,883 lines), c (25 lines), objectivec (12 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 42% of this repository's production lines — swift (8,883 lines), c (25 lines), objectivec (12 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 42% of this repository's production lines — swift (8,883 lines), c (25 lines), objectivec (12 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 42% of this repository's production lines — swift (8,883 lines), c (25 lines), objectivec (12 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — 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 — 28 finding(s)
- Click handler on a non-interactive <div> modules/components/src/components/button/button.component.html:1
- Click handler on a non-interactive <div> modules/components/src/components/dropdown/dropdown.component.html:9
- Click handler on a non-interactive <div> modules/components/src/components/dropdown/dropdown.component.html:12
- Click handler on a non-interactive <div> modules/components/src/components/select-box/select-box.component.html:3
- Click handler on a non-interactive <div> modules/components/src/components/toggle/toggle.component.html:1
- Click handler on a non-interactive <div> ui/src/app/components/options/options.component.html:5
- Click handler on a non-interactive <div> ui/src/app/components/options/options.component.html:43
- Click handler on a non-interactive <div> ui/src/app/sections/header/header.component.html:6
- Click handler on a non-interactive <div> ui/src/app/sections/header/header.component.html:9
- Click handler on a non-interactive <div> ui/src/app/sections/header/header.component.html:12
- Click handler on a non-interactive <div> ui/src/app/sections/header/header.component.html:30
- Click handler on a non-interactive <div> ui/src/app/sections/header/header.component.html:36
- Click handler on a non-interactive <div> ui/src/app/sections/header/header.component.html:42
- Custom control with no accessible name on <div> modules/components/src/components/dropdown/dropdown.component.html:9
- Custom control with no accessible name on <div> modules/components/src/components/dropdown/dropdown.component.html:12
- Custom control with no accessible name on <div> modules/components/src/components/toggle/toggle.component.html:1
- Custom control with no accessible name on <div> ui/src/app/sections/header/header.component.html:6
- Custom control with no accessible name on <div> ui/src/app/sections/header/header.component.html:9
- Custom control with no accessible name on <div> ui/src/app/sections/header/header.component.html:12
- Custom control with no accessible name on <div> ui/src/app/sections/header/header.component.html:30
- Custom control with no accessible name on <div> ui/src/app/sections/header/header.component.html:36
- Custom control with no accessible name on <div> ui/src/app/sections/header/header.component.html:42
- Double-click handler on a non-interactive <div> modules/components/src/components/flat-slider/flat-slider.component.html:11
- Double-click handler on a non-interactive <div> modules/components/src/components/knob/knob.component.html:1
- Double-click handler on a non-interactive <div> modules/components/src/components/skeuomorph-slider/skeuomorph-slider.component.html:3
- <input> without a programmatic label modules/components/src/components/input-field/input-field.component.html:2
- Hover-only interaction on <div> ui/src/app/sections/header/header.component.html:2
- Import cycle (4 files) ui/src/app/sections/effects/equalizers/equalizers.component.ts:4
Serious — 90 finding(s)
- TodoComment ui/src/app/sections/effects/equalizers/basic-equalizer/basic-equalizer.component.ts:114
- TodoComment ui/src/app/sections/effects/equalizers/advanced-equalizer/advanced-equalizer.component.ts:92
- TodoComment native/app/Source/Application.swift:170
- TodoComment native/app/Source/Application.swift:320
- TodoComment native/app/Source/Application.swift:626
- Low cohesion: AppDelegate (LCOM4 8) native/app/Source/AppDelegate.swift:17
- Low cohesion: Window (LCOM4 6) native/app/Source/UI/Window.swift:13
- Low cohesion: String (LCOM4 4) native/shared/Source/StringExtensions.swift:11
- Animation without a prefers-reduced-motion guard ui/src/index.html:34
- Animation without a prefers-reduced-motion guard modules/components/src/components/loading/loading.component.scss:15
- MethodTooLong: EQMDevice.getPropertyData native/driver/Source/EQMDevice.swift:168
- MethodTooLong: UIDataBus.init native/app/Source/UI/UIDataBus.swift:21
- TooManyMethods: UIService ui/src/app/services/ui.service.ts:37
- TooManyMethods: Application native/app/Source/Application.swift:28
- Edited copy of a member (11 corresponding lines) native/app/Source/Audio/Effects/Equalizers/Advanced/AdvancedEqualizer.swift:80
- Edited copy of a member (11 corresponding lines) native/app/Source/Audio/Effects/Equalizers/Advanced/AdvancedEqualizer.swift:128
- Duplicated block (11 lines × 2 locations) ui/src/app/components/confirm-dialog/confirm-dialog.component.ts:21
- Duplicated block (11 lines × 2 locations) ui/src/app/sections/outputs/outputs.service.ts:25
- Duplicated block (9 lines × 2 locations) modules/components/src/components/knob/knob.component.ts:223
- Duplicated block (9 lines × 2 locations) modules/components/src/services/utilities.service.ts:67
- Duplicated block (6 lines × 2 locations) modules/components/src/components/knob/knob.component.ts:305
- Duplicated block (6 lines × 2 locations) ui/src/app/services/data.service.ts:44
- Page without a main landmark ui/src/index.html:2
- Focus outline removed in CSS without a :focus replacement modules/components/src/components/input-field/input-field.component.scss:26
- EQMDevice.getPropertyData (cyclomatic 42) native/driver/Source/EQMDevice.swift:168
- EQMControl.getPropertyData (cyclomatic 40) native/driver/Source/EQMControl.swift:141
- EQMControl.getPropertyDataSize (cyclomatic 31) native/driver/Source/EQMControl.swift:92
- AdvancedEqualizerDataBus.init (cyclomatic 19) native/app/Source/Audio/Effects/Equalizers/Advanced/AdvancedEqualizerDataBus.swift:21
- ApplicationDataBus.init (cyclomatic 17) native/app/Source/ApplicationDataBus.swift:18
- UIDataBus.init (cyclomatic 17) native/app/Source/UI/UIDataBus.swift:21
- EQMStream.getPropertyData (cyclomatic 17) native/driver/Source/EQMStream.swift:69
- EQMControl.getPropertyData (cognitive 44) native/driver/Source/EQMControl.swift:141
- AdvancedEqualizerDataBus.init (cognitive 37) native/app/Source/Audio/Effects/Equalizers/Advanced/AdvancedEqualizerDataBus.swift:21
- KnobComponent.mousemove (cognitive 30) modules/components/src/components/knob/knob.component.ts:153
- EQMDevice.doIO (cognitive 26) native/driver/Source/EQMDevice.swift:584
- EQMDevice.getPropertyData (cognitive 22) native/driver/Source/EQMDevice.swift:168
- Application.volumeChangeButtonPressed (cognitive 21) native/app/Source/Application.swift:423
- EQMDevice.setPropertyData (cognitive 21) native/driver/Source/EQMDevice.swift:417
- Application.setupDeviceEvents (cognitive 20) native/app/Source/Application.swift:158
- EQMControl.setPropertyData (cognitive 20) native/driver/Source/EQMControl.swift:305
- ApplicationDataBus.init (cognitive 19) native/app/Source/ApplicationDataBus.swift:18
- EventInterceptor.sendEvent (cognitive 17) native/app/Source/EventInterceptor.swift:15
- Volume.gain (cognitive 17) native/app/Source/Audio/Volume/Volume.swift:30
- UIDataBus.init (cognitive 17) native/app/Source/UI/UIDataBus.swift:21
- FlatSliderComponent.mouseWheel (cognitive 17) modules/components/src/components/flat-slider/flat-slider.component.ts:160
- Volume.newState (cognitive 16) native/app/Source/Audio/Volume/Volume.swift:134
- ClassTooLong: Application native/app/Source/Application.swift:28
- Edited copy of a member (30 corresponding lines) native/shared/Source/CircularBuffer.swift:99
- Edited copy of a member (7 corresponding lines) native/app/Source/Audio/AudioDeviceEvents.swift:203
- Edited copy of a member (5 corresponding lines) native/app/Source/Audio/Effects/Equalizers/Advanced/AdvancedEqualizer.swift:143
- Edited copy of a member (3 corresponding lines) native/app/Source/Audio/Effects/Equalizers/Advanced/AdvancedEqualizer.swift:64
- Duplicated block (22–23 lines × 2) native/driver/Source/EQMControl.swift:315
- Duplicated block (14 lines × 2) native/shared/Source/CircularBuffer.swift:109
- Duplicated block (7 lines × 3) native/driver/Source/EQMControl.swift:95
- Duplicated block (5 lines × 3) native/driver/Source/EQMDevice.swift:108
- End-of-life runtime: Node.js 14 .nvmrc:1
- No CI pipeline
- Duplication concentrated across 3 sibling directories (5 clone groups) ui/src/app/sections/effects/equalizers/equalizers.component.ts:106
- Duplicated block with local edits (110 matched lines × 2 locations) modules/components/src/components/flat-slider/flat-slider.component.ts:103
- Duplicated block with local edits (39 matched lines × 2 locations) ui/src/app/sections/effects/equalizers/advanced-equalizer/advanced-equalizer.component.ts:63
- Duplicated block with local edits (38 matched lines × 2 locations) ui/src/app/sections/effects/equalizers/advanced-equalizer/advanced-equalizer.service.ts:22
- Duplicated block (23 lines × 2 locations) ui/src/app/app.component.ts:76
- Duplicated block (15 lines × 2 locations) ui/src/app/sections/source/input/input.service.ts:14
- Duplicated block (14 lines × 2 locations) ui/src/app/sections/settings/settings.component.ts:254
- Duplicated block (13 lines × 2 locations) ui/src/app/sections/effects/effect.service.ts:4
- Duplicated block (8 lines × 3 locations) ui/src/app/sections/effects/equalizers/equalizers.service.ts:19
- Duplicated block (8 lines × 4 locations) ui/src/app/sections/settings/settings.service.ts:23
- Duplicated block (8 lines × 2 locations) ui/src/app/services/ui.service.ts:106
- Duplicated block (7 lines × 4 locations) ui/src/app/sections/settings/settings.service.ts:33
- Duplicated block (7 lines × 2 locations) ui/src/app/services/ui.service.ts:218
- Complex function mousemove (cyclomatic 12, cognitive 26) modules/components/src/components/knob/knob.component.ts:154
- Test Coverage
- No test or typecheck script
- Dead file (~26 LoC) ui/src/app/services/context.service.ts
- Dead file (~13 LoC) ui/src/app/services/logger.service.ts
- Dead file (~6 LoC) ui/src/app/services/types.service.ts
- Unused dependency '@angular-devkit/core'
- Unused dependency '@angular/cli'
- Unused dependency '@angular/compiler'
- Unused dependency '@angular/compiler-cli'
- Unused dependency '@angular/language-service'
- Unused dependency 'cloudflare'
- Unused dependency 'core-js'
- Unused dependency 'dayjs'
- Unused dependency 'dotenv'
- Unused dependency 'ng-packagr'
- Unused dependency 'tslib'
- Unused dependency 'tslint'
- JavaScript dependencies are not locked package.json:29
- Swallowed exception (empty catch) ui/src/app/sections/source/file/file.component.ts:93
Minor — 79 finding(s)
- Orphaned file native/app/Source/Application.swift:1
- Orphaned file native/driver/Source/EQMControl.swift:1
- Orphaned file modules/components/src/components/flat-slider/flat-slider.component.ts:1
- Orphaned file native/app/Source/UI/UI.swift:1
- Orphaned file ui/src/app/sections/settings/settings.component.ts:1
- Orphaned file native/shared/Source/CircularBuffer.swift:1
- Orphaned file ui/src/app/app.component.ts:1
- Orphaned file modules/components/src/components/knob/knob.component.ts:1
- Orphaned file native/app/Source/Audio/AudioDeviceEvents.swift:1
- Orphaned file native/driver/Source/EQMStream.swift:1
- Orphaned file native/app/Source/Helpers/Sysctl.swift:1
- Orphaned file ui/src/app/sections/effects/equalizers/advanced-equalizer/advanced-equalizer.component.ts:1
- Orphaned file native/driver/Source/Helpers.swift:1
- Orphaned file native/app/Source/Extensions/AudioDevice.swift:1
- Orphaned file native/app/Source/Audio/Outputs/Output.swift:1
- Orphaned file modules/components/src/components/skeuomorph-slider/skeuomorph-slider.component.ts:1
- Orphaned file ui/src/app/services/ui.service.ts:1
- Orphaned file native/app/Source/Audio/Effects/Equalizers/Advanced/AdvancedEqualizerDataBus.swift:1
- Orphaned file native/app/Source/UI/UIDataBus.swift:1
- Orphaned file ui/src/app/sections/effects/equalizers/equalizers.component.ts:1
- Orphaned file ui/src/app/sections/effects/equalizers/basic-equalizer/basic-equalizer.component.ts:1
- Orphaned file native/app/Source/Audio/Effects/Equalizers/Basic/BasicEqualizer.swift:1
- Orphaned file native/driver/Source/EQMObject.swift:1
- Orphaned file native/app/Source/Audio/Sources/System/Driver.swift:1
- Orphaned file native/app/Source/Audio/Volume/Volume.swift:1
- Most significant orphaned file modules/components/src/components/icon/icons.ts:1
- Most significant orphaned file native/driver/Source/EQMDevice.swift:1
- Most significant orphaned file native/driver/Source/EQMInterface.swift:1
- Duplicated predicate modules/components/src/components/flat-slider/flat-slider.component.ts:124
- Duplicated predicate modules/components/src/components/flat-slider/flat-slider.component.ts:122
- Duplicated predicate modules/components/src/components/flat-slider/flat-slider.component.ts:270
- No ADRs found native/app/eqMac.xcodeproj/project.pbxproj:1
- Pass-through layer ui/src/app/services/context.service.ts:8
- Dormant codebase
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No SAST
- No dependency-update automation package.json:29
- No changelog
- Unused export 'UIDimensions' ui/src/app/services/ui.service.ts:23
- Strict null checking is not enabled everywhere the repository type-checks
- Null assertions (`!`) override strict null checking
Minor — 4 finding(s)
- Outdated: ReSwift
- Outdated: Sentry
- Outdated: Sparkle
- Outdated: SwiftLint
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-9a860d967a804becb7c27f20d92a6789/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9a860d967a804becb7c27f20d92a6789/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |
| D30 · Dependency Vulnerabilities | 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 |
| 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 1 file(s) — `native/driver/Source/EQMDriver.swift` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 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 |