Executive summary
alexpasmantier/television falls short of our standard for a preview release, held back most by its Code Health lens, the quality of the code itself. It scores 62 out of 100 and is rated Adequate, and 58 of its 59 critical findings are security problems in the build pipeline and in its automatic dependency updates.
Code Health, at 57, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 4 points. Turning on missing-value checks would lift Code Health itself, also worth about 4. Raising Code Health to 67 would lift the score to about 65.
Forty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Nine secrets can leak from the build pipeline, and four pipeline steps run downloads nobody checks. Pinning each tool to an exact version, limiting each secret to its own step and checking each download against a checksum would close these risks. Passing outside input through environment variables would fix the two pipeline steps that put outside input straight into a shell command, and the two pipeline steps that install packages without pinning their versions need the packages they install pinned to exact versions. The set of files in separate parts that keep changing together needs that dependency made explicit.
The product code is 23,265 lines, about €31,000 to rebuild.
If Code Health rose from 57 to 67, the lowest score rated Strong, the score would rise from 62 to about 65.
New since the last survey: 10 findings
- Dependency Hygiene · Yanked release: clipboard-win
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 8 findings
- Churn × Complexity Hotspots · Hotspot: television/television.rs television/television.rs
- Churn × Complexity Hotspots · Hotspot: television/action.rs television/action.rs
- Churn × Complexity Hotspots · Hotspot: television/screen/help_panel.rs television/screen/help_panel.rs
- Churn × Complexity Hotspots · Hotspot: television/screen/layout.rs television/screen/layout.rs
- Churn × Complexity Hotspots · Hotspot: television/screen/input.rs television/screen/input.rs
- Churn × Complexity Hotspots · Hotspot: television/screen/status_bar.rs television/screen/status_bar.rs
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €31,000 · Estimate
| Cost to rebuild | €10,000 to €51,000, for 170 to 538 hours of work, about 0.2 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.8 at a score of 62. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 23,265 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 action | 2 cli.args | 3 config.keybindings | 4 event | 5 matcher.injector | 6 matcher.matched_item | 7 utils.input | 8 cli | 9 config.shell_integration | 10 input | 11 matcher | 12 picker | 13 render | 14 screen.colors | 15 config | 16 config.themes | 17 screen.result_item | 18 channels.action_picker | 19 channels.entry | 20 channels.remote_control | 21 previewer | 22 previewer.state | 23 draw | 24 television | 25 keymap | 26 config.layers | 27 screen.action_picker | 28 screen.help_panel | 29 screen.input | 30 screen.layout | 31 screen.preview | 32 config.ui | 33 mouse | 34 channels.prototypes | 35 screen.results | 36 cable | 37 channels.channel | 38 channels.entry_processor | 39 television.television | 40 app |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 action | ||||||||||||||||||||||||||||||||||||||||
| 2 cli.args | ||||||||||||||||||||||||||||||||||||||||
| 3 config.keybindings | ||||||||||||||||||||||||||||||||||||||||
| 4 event | ||||||||||||||||||||||||||||||||||||||||
| 5 matcher.injector | ||||||||||||||||||||||||||||||||||||||||
| 6 matcher.matched_item | ||||||||||||||||||||||||||||||||||||||||
| 7 utils.input | ||||||||||||||||||||||||||||||||||||||||
| 8 cli | 4 | 1 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 9 config.shell_integration | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 input | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 matcher | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 12 picker | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 render | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 screen.colors | 6 | |||||||||||||||||||||||||||||||||||||||
| 15 config | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 16 config.themes | 7 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 screen.result_item | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 channels.action_picker | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 19 channels.entry | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 channels.remote_control | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 21 previewer | 1 | 3 | 4 | |||||||||||||||||||||||||||||||||||||
| 22 previewer.state | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 draw | 1 | 1 | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 24 television | 1 | 2 | 1 | 1 | 2 | 1 | 2 | 1 | 1 | 1 | 2 | 3 | 1 | |||||||||||||||||||||||||||
| 25 keymap | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 config.layers | 3 | 3 | 1 | 1 | 1 | 1 | 2 | 4 | ||||||||||||||||||||||||||||||||
| 27 screen.action_picker | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 screen.help_panel | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 screen.input | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 screen.layout | 4 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 31 screen.preview | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 32 config.ui | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 mouse | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 channels.prototypes | 1 | 1 | 1 | 1 | 8 | |||||||||||||||||||||||||||||||||||
| 35 screen.results | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 cable | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 37 channels.channel | 1 | 3 | 1 | 5 | ||||||||||||||||||||||||||||||||||||
| 38 channels.entry_processor | 4 | 4 | 4 | |||||||||||||||||||||||||||||||||||||
| 39 television.television | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 40 app | 1 | 2 | 1 | 1 | 1 | 1 |
8→2 cli uses cli.args✕
- Connections
- 4 pairs of types, where a type in cli uses a type in cli.args.
- The types involved
television.television.cli.ChannelCli→television.television.cli.args.BorderTypetelevision.television.cli.ChannelCli→television.television.cli.args.InputPositiontelevision.television.cli.GlobalCli→television.television.cli.args.Commandtelevision.television.cli.cli$module→television.television.cli.args.Cli
- Direction
- cli uses cli.args, so a change to cli.args can break cli, while a change to cli can't break cli.args.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
8→3 cli uses config.keybindings✕
- Connections
- 1 pair of types, where a type in cli uses a type in config.keybindings.
- The types involved
television.television.cli.ChannelCli→television.television.config.keybindings.Keybindings
- Direction
- cli uses config.keybindings, so a change to config.keybindings can break cli, while a change to cli can't break config.keybindings.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
8→30 cli uses screen.layout part of a loop✕
- Connections
- 1 pair of types, where a type in cli uses a type in screen.layout.
- The types involved
television.television.cli.ChannelCli→television.television.screen.layout.Orientation
- Direction
- cli uses screen.layout, so a change to screen.layout can break cli, while a change to cli can't break screen.layout.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→32 cli uses config.ui part of a loop✕
- Connections
- 1 pair of types, where a type in cli uses a type in config.ui.
- The types involved
television.television.cli.ChannelCli→television.television.config.ui.Padding
- Direction
- cli uses config.ui, so a change to config.ui can break cli, while a change to cli can't break config.ui.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→34 cli uses channels.prototypes part of a loop✕
- Connections
- 2 pairs of types, where a type in cli uses a type in channels.prototypes.
- The types involved
television.television.cli.ChannelCli→television.television.channels.prototypes.Templatetelevision.television.cli.cli$module→television.television.channels.prototypes.ChannelPrototype
- Direction
- cli uses channels.prototypes, so a change to channels.prototypes can break cli, while a change to cli can't break channels.prototypes.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→36 cli uses cable part of a loop✕
- Connections
- 1 pair of types, where a type in cli uses a type in cable.
- The types involved
television.television.cli.cli$module→television.television.cable.Cable
- Direction
- cli uses cable, so a change to cable can break cli, while a change to cli can't break cable.
- Position
- Above the diagonal, so 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→4 config.shell_integration uses event✕
- Connections
- 1 pair of types, where a type in config.shell_integration uses a type in event.
- The types involved
television.television.config.shell_integration.shell_integration$module→television.television.event.Key
- Direction
- config.shell_integration uses event, so a change to event can break config.shell_integration, while a change to config.shell_integration can't break event.
- Position
- Below the diagonal: config.shell_integration uses a module listed above it, which is the healthy direction.
10→1 input uses action✕
- Connections
- 1 pair of types, where a type in input uses a type in action.
- The types involved
television.television.input.input$module→television.television.action.Action
- Direction
- input uses action, so a change to action can break input, while a change to input can't break action.
- Position
- Below the diagonal: input uses a module listed above it, which is the healthy direction.
10→7 input uses utils.input✕
- Connections
- 1 pair of types, where a type in input uses a type in utils.input.
- The types involved
television.television.input.input$module→television.television.utils.input.InputRequest
- Direction
- input uses utils.input, so a change to utils.input can break input, while a change to input can't break utils.input.
- Position
- Below the diagonal: input uses a module listed above it, which is the healthy direction.
11→5 matcher uses matcher.injector✕
- Connections
- 1 pair of types, where a type in matcher uses a type in matcher.injector.
- The types involved
television.television.matcher.Matcher→television.television.matcher.injector.Injector
- Direction
- matcher uses matcher.injector, so a change to matcher.injector can break matcher, while a change to matcher can't break matcher.injector.
- Position
- Below the diagonal: matcher uses a module listed above it, which is the healthy direction.
11→6 matcher uses matcher.matched_item✕
- Connections
- 2 pairs of types, where a type in matcher uses a type in matcher.matched_item.
- The types involved
television.television.matcher.Matcher→television.television.matcher.matched_item.MatchedItemtelevision.television.matcher.matcher$module→television.television.matcher.matched_item.MatchedItem
- Direction
- matcher uses matcher.matched_item, so a change to matcher.matched_item can break matcher, while a change to matcher can't break matcher.matched_item.
- Position
- Below the diagonal: matcher uses a module listed above it, which is the healthy direction.
12→7 picker uses utils.input✕
- Connections
- 1 pair of types, where a type in picker uses a type in utils.input.
- The types involved
television.television.picker.Picker→television.television.utils.input.Input
- Direction
- picker uses utils.input, so a change to utils.input can break picker, while a change to picker can't break utils.input.
- Position
- Below the diagonal: picker uses a module listed above it, which is the healthy direction.
13→30 render uses screen.layout part of a loop✕
- Connections
- 1 pair of types, where a type in render uses a type in screen.layout.
- The types involved
television.television.render.UiState→television.television.screen.layout.Layout
- Direction
- render uses screen.layout, so a change to screen.layout can break render, while a change to render can't break screen.layout.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→16 screen.colors uses config.themes part of a loop✕
- Connections
- 6 pairs of types, where a type in screen.colors uses a type in config.themes.
- The types involved
television.television.screen.colors.GeneralColorscheme→television.television.config.themes.Colortelevision.television.screen.colors.HelpColorscheme→television.television.config.themes.Colortelevision.television.screen.colors.InputColorscheme→television.television.config.themes.Colortelevision.television.screen.colors.ModeColorscheme→television.television.config.themes.Colortelevision.television.screen.colors.PreviewColorscheme→television.television.config.themes.Colortelevision.television.screen.colors.ResultsColorscheme→television.television.config.themes.Color
- Direction
- screen.colors uses config.themes, so a change to config.themes can break screen.colors, while a change to screen.colors can't break config.themes.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→2 config uses cli.args✕
- Connections
- 1 pair of types, where a type in config uses a type in cli.args.
- The types involved
television.television.config.AppConfig→television.television.cli.args.Shell
- Direction
- config uses cli.args, so a change to cli.args can break config, while a change to config can't break cli.args.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
15→3 config uses config.keybindings✕
- Connections
- 1 pair of types, where a type in config uses a type in config.keybindings.
- The types involved
television.television.config.Config→television.television.config.keybindings.Keybindings
- Direction
- config uses config.keybindings, so a change to config.keybindings can break config, while a change to config can't break config.keybindings.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
15→9 config uses config.shell_integration✕
- Connections
- 1 pair of types, where a type in config uses a type in config.shell_integration.
- The types involved
television.television.config.Config→television.television.config.shell_integration.ShellIntegrationConfig
- Direction
- config uses config.shell_integration, so a change to config.shell_integration can break config, while a change to config can't break config.shell_integration.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
15→32 config uses config.ui part of a loop✕
- Connections
- 1 pair of types, where a type in config uses a type in config.ui.
- The types involved
television.television.config.Config→television.television.config.ui.UiConfig
- Direction
- config uses config.ui, so a change to config.ui can break config, while a change to config can't break config.ui.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→14 config.themes uses screen.colors✕
- Connections
- 7 pairs of types, where a type in config.themes uses a type in screen.colors.
- The types involved
television.television.config.themes.Theme→television.television.screen.colors.Colorschemetelevision.television.config.themes.Theme→television.television.screen.colors.GeneralColorschemetelevision.television.config.themes.Theme→television.television.screen.colors.HelpColorschemetelevision.television.config.themes.Theme→television.television.screen.colors.InputColorschemetelevision.television.config.themes.Theme→television.television.screen.colors.ModeColorschemetelevision.television.config.themes.Theme→television.television.screen.colors.PreviewColorschemetelevision.television.config.themes.Theme→television.television.screen.colors.ResultsColorscheme
- Direction
- config.themes uses screen.colors, so a change to screen.colors can break config.themes, while a change to config.themes can't break screen.colors.
- Position
- Below the diagonal: config.themes uses a module listed above it, which is the healthy direction.
16→32 config.themes uses config.ui part of a loop✕
- Connections
- 1 pair of types, where a type in config.themes uses a type in config.ui.
- The types involved
television.television.config.themes.Theme→television.television.config.ui.ThemeOverrides
- Direction
- config.themes uses config.ui, so a change to config.ui can break config.themes, while a change to config.themes can't break config.ui.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→4 screen.result_item uses event✕
- Connections
- 1 pair of types, where a type in screen.result_item uses a type in event.
- The types involved
television.television.screen.result_item.ResultItem→television.television.event.Key
- Direction
- screen.result_item uses event, so a change to event can break screen.result_item, while a change to screen.result_item can't break event.
- Position
- Below the diagonal: screen.result_item uses a module listed above it, which is the healthy direction.
17→14 screen.result_item uses screen.colors✕
- Connections
- 1 pair of types, where a type in screen.result_item uses a type in screen.colors.
- The types involved
television.television.screen.result_item.result_item$module→television.television.screen.colors.ResultsColorscheme
- Direction
- screen.result_item uses screen.colors, so a change to screen.colors can break screen.result_item, while a change to screen.result_item can't break screen.colors.
- Position
- Below the diagonal: screen.result_item uses a module listed above it, which is the healthy direction.
17→16 screen.result_item uses config.themes✕
- Connections
- 1 pair of types, where a type in screen.result_item uses a type in config.themes.
- The types involved
television.television.screen.result_item.result_item$module→television.television.config.themes.Color
- Direction
- screen.result_item uses config.themes, so a change to config.themes can break screen.result_item, while a change to screen.result_item can't break config.themes.
- Position
- Below the diagonal: screen.result_item uses a module listed above it, which is the healthy direction.
18→4 channels.action_picker uses event✕
- Connections
- 1 pair of types, where a type in channels.action_picker uses a type in event.
- The types involved
television.television.channels.action_picker.ActionEntry→television.television.event.Key
- Direction
- channels.action_picker uses event, so a change to event can break channels.action_picker, while a change to channels.action_picker can't break event.
- Position
- Below the diagonal: channels.action_picker uses a module listed above it, which is the healthy direction.
18→11 channels.action_picker uses matcher✕
- Connections
- 1 pair of types, where a type in channels.action_picker uses a type in matcher.
- The types involved
television.television.channels.action_picker.ActionPicker→television.television.matcher.Matcher
- Direction
- channels.action_picker uses matcher, so a change to matcher can break channels.action_picker, while a change to channels.action_picker can't break matcher.
- Position
- Below the diagonal: channels.action_picker uses a module listed above it, which is the healthy direction.
18→17 channels.action_picker uses screen.result_item✕
- Connections
- 1 pair of types, where a type in channels.action_picker uses a type in screen.result_item.
- The types involved
television.television.channels.action_picker.ActionEntry→television.television.screen.result_item.ResultItem
- Direction
- channels.action_picker uses screen.result_item, so a change to screen.result_item can break channels.action_picker, while a change to channels.action_picker can't break screen.result_item.
- Position
- Below the diagonal: channels.action_picker uses a module listed above it, which is the healthy direction.
18→34 channels.action_picker uses channels.prototypes part of a loop✕
- Connections
- 1 pair of types, where a type in channels.action_picker uses a type in channels.prototypes.
- The types involved
television.television.channels.action_picker.ActionEntry→television.television.channels.prototypes.ActionSpec
- Direction
- channels.action_picker uses channels.prototypes, so a change to channels.prototypes can break channels.action_picker, while a change to channels.action_picker can't break channels.prototypes.
- Position
- Above the diagonal, so 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→4 channels.entry uses event✕
- Connections
- 1 pair of types, where a type in channels.entry uses a type in event.
- The types involved
television.television.channels.entry.Entry→television.television.event.Key
- Direction
- channels.entry uses event, so a change to event can break channels.entry, while a change to channels.entry can't break event.
- Position
- Below the diagonal: channels.entry uses a module listed above it, which is the healthy direction.
19→17 channels.entry uses screen.result_item✕
- Connections
- 1 pair of types, where a type in channels.entry uses a type in screen.result_item.
- The types involved
television.television.channels.entry.Entry→television.television.screen.result_item.ResultItem
- Direction
- channels.entry uses screen.result_item, so a change to screen.result_item can break channels.entry, while a change to channels.entry can't break screen.result_item.
- Position
- Below the diagonal: channels.entry uses a module listed above it, which is the healthy direction.
19→34 channels.entry uses channels.prototypes part of a loop✕
- Connections
- 1 pair of types, where a type in channels.entry uses a type in channels.prototypes.
- The types involved
television.television.channels.entry.Entry→television.television.channels.prototypes.Template
- Direction
- channels.entry uses channels.prototypes, so a change to channels.prototypes can break channels.entry, while a change to channels.entry can't break channels.prototypes.
- Position
- Above the diagonal, so 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→4 channels.remote_control uses event✕
- Connections
- 1 pair of types, where a type in channels.remote_control uses a type in event.
- The types involved
television.television.channels.remote_control.CableEntry→television.television.event.Key
- Direction
- channels.remote_control uses event, so a change to event can break channels.remote_control, while a change to channels.remote_control can't break event.
- Position
- Below the diagonal: channels.remote_control uses a module listed above it, which is the healthy direction.
20→11 channels.remote_control uses matcher✕
- Connections
- 1 pair of types, where a type in channels.remote_control uses a type in matcher.
- The types involved
television.television.channels.remote_control.RemoteControl→television.television.matcher.Matcher
- Direction
- channels.remote_control uses matcher, so a change to matcher can break channels.remote_control, while a change to channels.remote_control can't break matcher.
- Position
- Below the diagonal: channels.remote_control uses a module listed above it, which is the healthy direction.
20→17 channels.remote_control uses screen.result_item✕
- Connections
- 1 pair of types, where a type in channels.remote_control uses a type in screen.result_item.
- The types involved
television.television.channels.remote_control.CableEntry→television.television.screen.result_item.ResultItem
- Direction
- channels.remote_control uses screen.result_item, so a change to screen.result_item can break channels.remote_control, while a change to channels.remote_control can't break screen.result_item.
- Position
- Below the diagonal: channels.remote_control uses a module listed above it, which is the healthy direction.
20→34 channels.remote_control uses channels.prototypes part of a loop✕
- Connections
- 2 pairs of types, where a type in channels.remote_control uses a type in channels.prototypes.
- The types involved
television.television.channels.remote_control.CableEntry→television.television.channels.prototypes.BinaryRequirementtelevision.television.channels.remote_control.RemoteControl→television.television.channels.prototypes.ChannelPrototype
- Direction
- channels.remote_control uses channels.prototypes, so a change to channels.prototypes can break channels.remote_control, while a change to channels.remote_control can't break channels.prototypes.
- Position
- Above the diagonal, so 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→36 channels.remote_control uses cable part of a loop✕
- Connections
- 1 pair of types, where a type in channels.remote_control uses a type in cable.
- The types involved
television.television.channels.remote_control.RemoteControl→television.television.cable.Cable
- Direction
- channels.remote_control uses cable, so a change to cable can break channels.remote_control, while a change to channels.remote_control can't break cable.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→15 previewer uses config✕
- Connections
- 1 pair of types, where a type in previewer uses a type in config.
- The types involved
television.television.previewer.Previewer→television.television.config.Config
- Direction
- previewer uses config, so a change to config can break previewer, while a change to previewer can't break config.
- Position
- Below the diagonal: previewer uses a module listed above it, which is the healthy direction.
21→19 previewer uses channels.entry✕
- Connections
- 3 pairs of types, where a type in previewer uses a type in channels.entry.
- The types involved
television.television.previewer.Previewer→television.television.channels.entry.Entrytelevision.television.previewer.Ticket→television.television.channels.entry.Entrytelevision.television.previewer.previewer$module→television.television.channels.entry.Entry
- Direction
- previewer uses channels.entry, so a change to channels.entry can break previewer, while a change to previewer can't break channels.entry.
- Position
- Below the diagonal: previewer uses a module listed above it, which is the healthy direction.
21→34 previewer uses channels.prototypes part of a loop✕
- Connections
- 4 pairs of types, where a type in previewer uses a type in channels.prototypes.
- The types involved
television.television.previewer.Previewer→television.television.channels.prototypes.CommandSpectelevision.television.previewer.Previewer→television.television.channels.prototypes.Templatetelevision.television.previewer.previewer$module→television.television.channels.prototypes.CommandSpectelevision.television.previewer.previewer$module→television.television.channels.prototypes.Template
- Direction
- previewer uses channels.prototypes, so a change to channels.prototypes can break previewer, while a change to previewer can't break channels.prototypes.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→21 previewer.state uses previewer✕
- Connections
- 1 pair of types, where a type in previewer.state uses a type in previewer.
- The types involved
television.television.previewer.state.PreviewState→television.television.previewer.Preview
- Direction
- previewer.state uses previewer, so a change to previewer can break previewer.state, while a change to previewer.state can't break previewer.
- Position
- Below the diagonal: previewer.state uses a module listed above it, which is the healthy direction.
23→12 draw uses picker✕
- Connections
- 1 pair of types, where a type in draw uses a type in picker.
- The types involved
television.television.draw.TvState→television.television.picker.Picker
- Direction
- draw uses picker, so a change to picker can break draw, while a change to draw can't break picker.
- Position
- Below the diagonal: draw uses a module listed above it, which is the healthy direction.
23→14 draw uses screen.colors✕
- Connections
- 1 pair of types, where a type in draw uses a type in screen.colors.
- The types involved
television.television.draw.Ctx→television.television.screen.colors.Colorscheme
- Direction
- draw uses screen.colors, so a change to screen.colors can break draw, while a change to draw can't break screen.colors.
- Position
- Below the diagonal: draw uses a module listed above it, which is the healthy direction.
23→19 draw uses channels.entry✕
- Connections
- 1 pair of types, where a type in draw uses a type in channels.entry.
- The types involved
television.television.draw.TvState→television.television.channels.entry.Entry
- Direction
- draw uses channels.entry, so a change to channels.entry can break draw, while a change to draw can't break channels.entry.
- Position
- Below the diagonal: draw uses a module listed above it, which is the healthy direction.
23→22 draw uses previewer.state✕
- Connections
- 1 pair of types, where a type in draw uses a type in previewer.state.
- The types involved
television.television.draw.TvState→television.television.previewer.state.PreviewState
- Direction
- draw uses previewer.state, so a change to previewer.state can break draw, while a change to draw can't break previewer.state.
- Position
- Below the diagonal: draw uses a module listed above it, which is the healthy direction.
23→24 draw uses television part of a loop✕
- Connections
- 2 pairs of types, where a type in draw uses a type in television.
- The types involved
television.television.draw.TvState→television.television.television.MissingRequirementsPopuptelevision.television.draw.TvState→television.television.television.Mode
- Direction
- draw uses television, so a change to television can break draw, while a change to draw can't break television.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→26 draw uses config.layers part of a loop✕
- Connections
- 1 pair of types, where a type in draw uses a type in config.layers.
- The types involved
television.television.draw.Ctx→television.television.config.layers.MergedConfig
- Direction
- draw uses config.layers, so a change to config.layers can break draw, while a change to draw can't break config.layers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→30 draw uses screen.layout part of a loop✕
- Connections
- 1 pair of types, where a type in draw uses a type in screen.layout.
- The types involved
television.television.draw.Ctx→television.television.screen.layout.Layout
- Direction
- draw uses screen.layout, so a change to screen.layout can break draw, while a change to draw can't break screen.layout.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→1 television uses action✕
- Connections
- 1 pair of types, where a type in television uses a type in action.
- The types involved
television.television.television.Television→television.television.action.Action
- Direction
- television uses action, so a change to action can break television, while a change to television can't break action.
- Position
- Below the diagonal: television uses a module listed above it, which is the healthy direction.
24→12 television uses picker✕
- Connections
- 2 pairs of types, where a type in television uses a type in picker.
- The types involved
television.television.television.Television→television.television.picker.Movementtelevision.television.television.Television→television.television.picker.Picker
- Direction
- television uses picker, so a change to picker can break television, while a change to television can't break picker.
- Position
- Below the diagonal: television uses a module listed above it, which is the healthy direction.
24→13 television uses render✕
- Connections
- 1 pair of types, where a type in television uses a type in render.
- The types involved
television.television.television.Television→television.television.render.UiState
- Direction
- television uses render, so a change to render can break television, while a change to television can't break render.
- Position
- Below the diagonal: television uses a module listed above it, which is the healthy direction.
24→14 television uses screen.colors✕
- Connections
- 1 pair of types, where a type in television uses a type in screen.colors.
- The types involved
television.television.television.Television→television.television.screen.colors.Colorscheme
- Direction
- television uses screen.colors, so a change to screen.colors can break television, while a change to television can't break screen.colors.
- Position
- Below the diagonal: television uses a module listed above it, which is the healthy direction.
24→18 television uses channels.action_picker✕
- Connections
- 2 pairs of types, where a type in television uses a type in channels.action_picker.
- The types involved
television.television.television.Television→television.television.channels.action_picker.ActionEntrytelevision.television.television.Television→television.television.channels.action_picker.ActionPicker
- Direction
- television uses channels.action_picker, so a change to channels.action_picker can break television, while a change to television can't break channels.action_picker.
- Position
- Below the diagonal: television uses a module listed above it, which is the healthy direction.
24→19 television uses channels.entry✕
- Connections
- 1 pair of types, where a type in television uses a type in channels.entry.
- The types involved
television.television.television.Television→television.television.channels.entry.Entry
- Direction
- television uses channels.entry, so a change to channels.entry can break television, while a change to television can't break channels.entry.
- Position
- Below the diagonal: television uses a module listed above it, which is the healthy direction.
24→20 television uses channels.remote_control✕
- Connections
- 2 pairs of types, where a type in television uses a type in channels.remote_control.
- The types involved
television.television.television.Television→television.television.channels.remote_control.CableEntrytelevision.television.television.Television→television.television.channels.remote_control.RemoteControl
- Direction
- television uses channels.remote_control, so a change to channels.remote_control can break television, while a change to television can't break channels.remote_control.
- Position
- Below the diagonal: television uses a module listed above it, which is the healthy direction.
24→21 television uses previewer✕
- Connections
- 1 pair of types, where a type in television uses a type in previewer.
- The types involved
television.television.television.Television→television.television.previewer.Preview
- Direction
- television uses previewer, so a change to previewer can break television, while a change to television can't break previewer.
- Position
- Below the diagonal: television uses a module listed above it, which is the healthy direction.
24→22 television uses previewer.state✕
- Connections
- 1 pair of types, where a type in television uses a type in previewer.state.
- The types involved
television.television.television.Television→television.television.previewer.state.PreviewState
- Direction
- television uses previewer.state, so a change to previewer.state can break television, while a change to television can't break previewer.state.
- Position
- Below the diagonal: television uses a module listed above it, which is the healthy direction.
24→23 television uses draw✕
- Connections
- 1 pair of types, where a type in television uses a type in draw.
- The types involved
television.television.television.Television→television.television.draw.Ctx
- Direction
- television uses draw, so a change to draw can break television, while a change to television can't break draw.
- Position
- Below the diagonal: television uses a module listed above it, which is the healthy direction.
24→26 television uses config.layers part of a loop✕
- Connections
- 2 pairs of types, where a type in television uses a type in config.layers.
- The types involved
television.television.television.Television→television.television.config.layers.ConfigLayerstelevision.television.television.Television→television.television.config.layers.MergedConfig
- Direction
- television uses config.layers, so a change to config.layers can break television, while a change to television can't break config.layers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→34 television uses channels.prototypes part of a loop✕
- Connections
- 3 pairs of types, where a type in television uses a type in channels.prototypes.
- The types involved
television.television.television.Television→television.television.channels.prototypes.ChannelPrototypetelevision.television.television.Television→television.television.channels.prototypes.CommandSpectelevision.television.television.Television→television.television.channels.prototypes.Template
- Direction
- television uses channels.prototypes, so a change to channels.prototypes can break television, while a change to television can't break channels.prototypes.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→36 television uses cable part of a loop✕
- Connections
- 1 pair of types, where a type in television uses a type in cable.
- The types involved
television.television.television.Television→television.television.cable.Cable
- Direction
- television uses cable, so a change to cable can break television, while a change to television can't break cable.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→1 keymap uses action✕
- Connections
- 2 pairs of types, where a type in keymap uses a type in action.
- The types involved
television.television.keymap.InputMap→television.television.action.Actiontelevision.television.keymap.InputMap→television.television.action.Actions
- Direction
- keymap uses action, so a change to action can break keymap, while a change to keymap can't break action.
- Position
- Below the diagonal: keymap uses a module listed above it, which is the healthy direction.
25→3 keymap uses config.keybindings✕
- Connections
- 1 pair of types, where a type in keymap uses a type in config.keybindings.
- The types involved
television.television.keymap.InputMap→television.television.config.keybindings.Keybindings
- Direction
- keymap uses config.keybindings, so a change to config.keybindings can break keymap, while a change to keymap can't break config.keybindings.
- Position
- Below the diagonal: keymap uses a module listed above it, which is the healthy direction.
25→4 keymap uses event✕
- Connections
- 1 pair of types, where a type in keymap uses a type in event.
- The types involved
television.television.keymap.InputMap→television.television.event.Key
- Direction
- keymap uses event, so a change to event can break keymap, while a change to keymap can't break event.
- Position
- Below the diagonal: keymap uses a module listed above it, which is the healthy direction.
25→24 keymap uses television✕
- Connections
- 1 pair of types, where a type in keymap uses a type in television.
- The types involved
television.television.keymap.InputMap→television.television.television.Mode
- Direction
- keymap uses television, so a change to television can break keymap, while a change to keymap can't break television.
- Position
- Below the diagonal: keymap uses a module listed above it, which is the healthy direction.
26→2 config.layers uses cli.args✕
- Connections
- 3 pairs of types, where a type in config.layers uses a type in cli.args.
- The types involved
television.television.config.layers.MergedConfig→television.television.cli.args.BorderTypetelevision.television.config.layers.MergedConfig→television.television.cli.args.InputPositiontelevision.television.config.layers.MergedConfig→television.television.cli.args.Shell
- Direction
- config.layers uses cli.args, so a change to cli.args can break config.layers, while a change to config.layers can't break cli.args.
- Position
- Below the diagonal: config.layers uses a module listed above it, which is the healthy direction.
26→8 config.layers uses cli✕
- Connections
- 3 pairs of types, where a type in config.layers uses a type in cli.
- The types involved
television.television.config.layers.ConfigLayers→television.television.cli.ChannelClitelevision.television.config.layers.ConfigLayers→television.television.cli.GlobalClitelevision.television.config.layers.ConfigLayers→television.television.cli.PostProcessedCli
- Direction
- config.layers uses cli, so a change to cli can break config.layers, while a change to config.layers can't break cli.
- Position
- Below the diagonal: config.layers uses a module listed above it, which is the healthy direction.
26→11 config.layers uses matcher✕
- Connections
- 1 pair of types, where a type in config.layers uses a type in matcher.
- The types involved
television.television.config.layers.MergedConfig→television.television.matcher.MatcherConfig
- Direction
- config.layers uses matcher, so a change to matcher can break config.layers, while a change to config.layers can't break matcher.
- Position
- Below the diagonal: config.layers uses a module listed above it, which is the healthy direction.
26→15 config.layers uses config✕
- Connections
- 1 pair of types, where a type in config.layers uses a type in config.
- The types involved
television.television.config.layers.ConfigLayers→television.television.config.Config
- Direction
- config.layers uses config, so a change to config can break config.layers, while a change to config.layers can't break config.
- Position
- Below the diagonal: config.layers uses a module listed above it, which is the healthy direction.
26→25 config.layers uses keymap✕
- Connections
- 1 pair of types, where a type in config.layers uses a type in keymap.
- The types involved
television.television.config.layers.MergedConfig→television.television.keymap.InputMap
- Direction
- config.layers uses keymap, so a change to keymap can break config.layers, while a change to config.layers can't break keymap.
- Position
- Below the diagonal: config.layers uses a module listed above it, which is the healthy direction.
26→30 config.layers uses screen.layout part of a loop✕
- Connections
- 1 pair of types, where a type in config.layers uses a type in screen.layout.
- The types involved
television.television.config.layers.MergedConfig→television.television.screen.layout.Orientation
- Direction
- config.layers uses screen.layout, so a change to screen.layout can break config.layers, while a change to config.layers can't break screen.layout.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→32 config.layers uses config.ui part of a loop✕
- Connections
- 2 pairs of types, where a type in config.layers uses a type in config.ui.
- The types involved
television.television.config.layers.MergedConfig→television.television.config.ui.Paddingtelevision.television.config.layers.MergedConfig→television.television.config.ui.ThemeOverrides
- Direction
- config.layers uses config.ui, so a change to config.ui can break config.layers, while a change to config.layers can't break config.ui.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→34 config.layers uses channels.prototypes part of a loop✕
- Connections
- 4 pairs of types, where a type in config.layers uses a type in channels.prototypes.
- The types involved
television.television.config.layers.ConfigLayers→television.television.channels.prototypes.ChannelPrototypetelevision.television.config.layers.MergedConfig→television.television.channels.prototypes.BinaryRequirementtelevision.television.config.layers.MergedConfig→television.television.channels.prototypes.CommandSpectelevision.television.config.layers.MergedConfig→television.television.channels.prototypes.Template
- Direction
- config.layers uses channels.prototypes, so a change to channels.prototypes can break config.layers, while a change to config.layers can't break channels.prototypes.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→7 screen.action_picker uses utils.input✕
- Connections
- 1 pair of types, where a type in screen.action_picker uses a type in utils.input.
- The types involved
television.television.screen.action_picker.action_picker$module→television.television.utils.input.Input
- Direction
- screen.action_picker uses utils.input, so a change to utils.input can break screen.action_picker, while a change to screen.action_picker can't break utils.input.
- Position
- Below the diagonal: screen.action_picker uses a module listed above it, which is the healthy direction.
27→14 screen.action_picker uses screen.colors✕
- Connections
- 1 pair of types, where a type in screen.action_picker uses a type in screen.colors.
- The types involved
television.television.screen.action_picker.action_picker$module→television.television.screen.colors.Colorscheme
- Direction
- screen.action_picker uses screen.colors, so a change to screen.colors can break screen.action_picker, while a change to screen.action_picker can't break screen.colors.
- Position
- Below the diagonal: screen.action_picker uses a module listed above it, which is the healthy direction.
27→26 screen.action_picker uses config.layers✕
- Connections
- 1 pair of types, where a type in screen.action_picker uses a type in config.layers.
- The types involved
television.television.screen.action_picker.action_picker$module→television.television.config.layers.MergedConfig
- Direction
- screen.action_picker uses config.layers, so a change to config.layers can break screen.action_picker, while a change to screen.action_picker can't break config.layers.
- Position
- Below the diagonal: screen.action_picker uses a module listed above it, which is the healthy direction.
28→1 screen.help_panel uses action✕
- Connections
- 1 pair of types, where a type in screen.help_panel uses a type in action.
- The types involved
television.television.screen.help_panel.help_panel$module→television.television.action.Action
- Direction
- screen.help_panel uses action, so a change to action can break screen.help_panel, while a change to screen.help_panel can't break action.
- Position
- Below the diagonal: screen.help_panel uses a module listed above it, which is the healthy direction.
28→14 screen.help_panel uses screen.colors✕
- Connections
- 1 pair of types, where a type in screen.help_panel uses a type in screen.colors.
- The types involved
television.television.screen.help_panel.help_panel$module→television.television.screen.colors.Colorscheme
- Direction
- screen.help_panel uses screen.colors, so a change to screen.colors can break screen.help_panel, while a change to screen.help_panel can't break screen.colors.
- Position
- Below the diagonal: screen.help_panel uses a module listed above it, which is the healthy direction.
28→24 screen.help_panel uses television✕
- Connections
- 1 pair of types, where a type in screen.help_panel uses a type in television.
- The types involved
television.television.screen.help_panel.help_panel$module→television.television.television.Mode
- Direction
- screen.help_panel uses television, so a change to television can break screen.help_panel, while a change to screen.help_panel can't break television.
- Position
- Below the diagonal: screen.help_panel uses a module listed above it, which is the healthy direction.
28→26 screen.help_panel uses config.layers✕
- Connections
- 1 pair of types, where a type in screen.help_panel uses a type in config.layers.
- The types involved
television.television.screen.help_panel.help_panel$module→television.television.config.layers.MergedConfig
- Direction
- screen.help_panel uses config.layers, so a change to config.layers can break screen.help_panel, while a change to screen.help_panel can't break config.layers.
- Position
- Below the diagonal: screen.help_panel uses a module listed above it, which is the healthy direction.
29→7 screen.input uses utils.input✕
- Connections
- 1 pair of types, where a type in screen.input uses a type in utils.input.
- The types involved
television.television.screen.input.input$module→television.television.utils.input.Input
- Direction
- screen.input uses utils.input, so a change to utils.input can break screen.input, while a change to screen.input can't break utils.input.
- Position
- Below the diagonal: screen.input uses a module listed above it, which is the healthy direction.
29→14 screen.input uses screen.colors✕
- Connections
- 1 pair of types, where a type in screen.input uses a type in screen.colors.
- The types involved
television.television.screen.input.input$module→television.television.screen.colors.Colorscheme
- Direction
- screen.input uses screen.colors, so a change to screen.colors can break screen.input, while a change to screen.input can't break screen.colors.
- Position
- Below the diagonal: screen.input uses a module listed above it, which is the healthy direction.
29→26 screen.input uses config.layers✕
- Connections
- 1 pair of types, where a type in screen.input uses a type in config.layers.
- The types involved
television.television.screen.input.input$module→television.television.config.layers.MergedConfig
- Direction
- screen.input uses config.layers, so a change to config.layers can break screen.input, while a change to screen.input can't break config.layers.
- Position
- Below the diagonal: screen.input uses a module listed above it, which is the healthy direction.
30→2 screen.layout uses cli.args✕
- Connections
- 4 pairs of types, where a type in screen.layout uses a type in cli.args.
- The types involved
television.television.screen.layout.InputPosition→television.television.cli.args.InputPositiontelevision.television.screen.layout.Orientation→television.television.cli.args.LayoutOrientationtelevision.television.screen.layout.layout$module→television.television.cli.args.BorderTypetelevision.television.screen.layout.layout$module→television.television.cli.args.InputPosition
- Direction
- screen.layout uses cli.args, so a change to cli.args can break screen.layout, while a change to screen.layout can't break cli.args.
- Position
- Below the diagonal: screen.layout uses a module listed above it, which is the healthy direction.
30→14 screen.layout uses screen.colors✕
- Connections
- 1 pair of types, where a type in screen.layout uses a type in screen.colors.
- The types involved
television.television.screen.layout.layout$module→television.television.screen.colors.Colorscheme
- Direction
- screen.layout uses screen.colors, so a change to screen.colors can break screen.layout, while a change to screen.layout can't break screen.colors.
- Position
- Below the diagonal: screen.layout uses a module listed above it, which is the healthy direction.
30→24 screen.layout uses television✕
- Connections
- 1 pair of types, where a type in screen.layout uses a type in television.
- The types involved
television.television.screen.layout.Layout→television.television.television.Mode
- Direction
- screen.layout uses television, so a change to television can break screen.layout, while a change to screen.layout can't break television.
- Position
- Below the diagonal: screen.layout uses a module listed above it, which is the healthy direction.
30→26 screen.layout uses config.layers✕
- Connections
- 2 pairs of types, where a type in screen.layout uses a type in config.layers.
- The types involved
television.television.screen.layout.Layout→television.television.config.layers.MergedConfigtelevision.television.screen.layout.layout$module→television.television.config.layers.MergedConfig
- Direction
- screen.layout uses config.layers, so a change to config.layers can break screen.layout, while a change to screen.layout can't break config.layers.
- Position
- Below the diagonal: screen.layout uses a module listed above it, which is the healthy direction.
30→32 screen.layout uses config.ui part of a loop✕
- Connections
- 1 pair of types, where a type in screen.layout uses a type in config.ui.
- The types involved
television.television.screen.layout.layout$module→television.television.config.ui.Padding
- Direction
- screen.layout uses config.ui, so a change to config.ui can break screen.layout, while a change to screen.layout can't break config.ui.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→4 screen.preview uses event✕
- Connections
- 1 pair of types, where a type in screen.preview uses a type in event.
- The types involved
television.television.screen.preview.preview$module→television.television.event.Key
- Direction
- screen.preview uses event, so a change to event can break screen.preview, while a change to screen.preview can't break event.
- Position
- Below the diagonal: screen.preview uses a module listed above it, which is the healthy direction.
31→14 screen.preview uses screen.colors✕
- Connections
- 1 pair of types, where a type in screen.preview uses a type in screen.colors.
- The types involved
television.television.screen.preview.preview$module→television.television.screen.colors.Colorscheme
- Direction
- screen.preview uses screen.colors, so a change to screen.colors can break screen.preview, while a change to screen.preview can't break screen.colors.
- Position
- Below the diagonal: screen.preview uses a module listed above it, which is the healthy direction.
31→16 screen.preview uses config.themes✕
- Connections
- 1 pair of types, where a type in screen.preview uses a type in config.themes.
- The types involved
television.television.screen.preview.preview$module→television.television.config.themes.Color
- Direction
- screen.preview uses config.themes, so a change to config.themes can break screen.preview, while a change to screen.preview can't break config.themes.
- Position
- Below the diagonal: screen.preview uses a module listed above it, which is the healthy direction.
31→22 screen.preview uses previewer.state✕
- Connections
- 1 pair of types, where a type in screen.preview uses a type in previewer.state.
- The types involved
television.television.screen.preview.preview$module→television.television.previewer.state.PreviewState
- Direction
- screen.preview uses previewer.state, so a change to previewer.state can break screen.preview, while a change to screen.preview can't break previewer.state.
- Position
- Below the diagonal: screen.preview uses a module listed above it, which is the healthy direction.
31→26 screen.preview uses config.layers✕
- Connections
- 1 pair of types, where a type in screen.preview uses a type in config.layers.
- The types involved
television.television.screen.preview.preview$module→television.television.config.layers.MergedConfig
- Direction
- screen.preview uses config.layers, so a change to config.layers can break screen.preview, while a change to screen.preview can't break config.layers.
- Position
- Below the diagonal: screen.preview uses a module listed above it, which is the healthy direction.
32→2 config.ui uses cli.args✕
- Connections
- 5 pairs of types, where a type in config.ui uses a type in cli.args.
- The types involved
television.television.config.ui.BorderType→television.television.cli.args.BorderTypetelevision.television.config.ui.InputBarConfig→television.television.cli.args.BorderTypetelevision.television.config.ui.InputBarConfig→television.television.cli.args.InputPositiontelevision.television.config.ui.PreviewPanelConfig→television.television.cli.args.BorderTypetelevision.television.config.ui.ResultsPanelConfig→television.television.cli.args.BorderType
- Direction
- config.ui uses cli.args, so a change to cli.args can break config.ui, while a change to config.ui can't break cli.args.
- Position
- Below the diagonal: config.ui uses a module listed above it, which is the healthy direction.
32→30 config.ui uses screen.layout✕
- Connections
- 1 pair of types, where a type in config.ui uses a type in screen.layout.
- The types involved
television.television.config.ui.UiConfig→television.television.screen.layout.Orientation
- Direction
- config.ui uses screen.layout, so a change to screen.layout can break config.ui, while a change to config.ui can't break screen.layout.
- Position
- Below the diagonal: config.ui uses a module listed above it, which is the healthy direction.
32→34 config.ui uses channels.prototypes part of a loop✕
- Connections
- 1 pair of types, where a type in config.ui uses a type in channels.prototypes.
- The types involved
television.television.config.ui.PreviewPanelConfig→television.television.channels.prototypes.Template
- Direction
- config.ui uses channels.prototypes, so a change to channels.prototypes can break config.ui, while a change to config.ui can't break channels.prototypes.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→1 mouse uses action✕
- Connections
- 1 pair of types, where a type in mouse uses a type in action.
- The types involved
television.television.mouse.mouse$module→television.television.action.Action
- Direction
- mouse uses action, so a change to action can break mouse, while a change to mouse can't break action.
- Position
- Below the diagonal: mouse uses a module listed above it, which is the healthy direction.
33→24 mouse uses television✕
- Connections
- 1 pair of types, where a type in mouse uses a type in television.
- The types involved
television.television.mouse.mouse$module→television.television.television.Mode
- Direction
- mouse uses television, so a change to television can break mouse, while a change to mouse can't break television.
- Position
- Below the diagonal: mouse uses a module listed above it, which is the healthy direction.
33→30 mouse uses screen.layout✕
- Connections
- 1 pair of types, where a type in mouse uses a type in screen.layout.
- The types involved
television.television.mouse.mouse$module→television.television.screen.layout.Layout
- Direction
- mouse uses screen.layout, so a change to screen.layout can break mouse, while a change to mouse can't break screen.layout.
- Position
- Below the diagonal: mouse uses a module listed above it, which is the healthy direction.
34→2 channels.prototypes uses cli.args✕
- Connections
- 1 pair of types, where a type in channels.prototypes uses a type in cli.args.
- The types involved
television.television.channels.prototypes.CommandSpec→television.television.cli.args.Shell
- Direction
- channels.prototypes uses cli.args, so a change to cli.args can break channels.prototypes, while a change to channels.prototypes can't break cli.args.
- Position
- Below the diagonal: channels.prototypes uses a module listed above it, which is the healthy direction.
34→3 channels.prototypes uses config.keybindings✕
- Connections
- 1 pair of types, where a type in channels.prototypes uses a type in config.keybindings.
- The types involved
television.television.channels.prototypes.ChannelKeyBindings→television.television.config.keybindings.Keybindings
- Direction
- channels.prototypes uses config.keybindings, so a change to config.keybindings can break channels.prototypes, while a change to channels.prototypes can't break config.keybindings.
- Position
- Below the diagonal: channels.prototypes uses a module listed above it, which is the healthy direction.
34→4 channels.prototypes uses event✕
- Connections
- 1 pair of types, where a type in channels.prototypes uses a type in event.
- The types involved
television.television.channels.prototypes.ChannelKeyBindings→television.television.event.Key
- Direction
- channels.prototypes uses event, so a change to event can break channels.prototypes, while a change to channels.prototypes can't break event.
- Position
- Below the diagonal: channels.prototypes uses a module listed above it, which is the healthy direction.
34→30 channels.prototypes uses screen.layout✕
- Connections
- 1 pair of types, where a type in channels.prototypes uses a type in screen.layout.
- The types involved
television.television.channels.prototypes.UiSpec→television.television.screen.layout.Orientation
- Direction
- channels.prototypes uses screen.layout, so a change to screen.layout can break channels.prototypes, while a change to channels.prototypes can't break screen.layout.
- Position
- Below the diagonal: channels.prototypes uses a module listed above it, which is the healthy direction.
34→32 channels.prototypes uses config.ui✕
- Connections
- 8 pairs of types, where a type in channels.prototypes uses a type in config.ui.
- The types involved
television.television.channels.prototypes.UiSpec→television.television.config.ui.HelpPanelConfigtelevision.television.channels.prototypes.UiSpec→television.television.config.ui.InputBarConfigtelevision.television.channels.prototypes.UiSpec→television.television.config.ui.PreviewPanelConfigtelevision.television.channels.prototypes.UiSpec→television.television.config.ui.RemoteControlConfigtelevision.television.channels.prototypes.UiSpec→television.television.config.ui.ResultsPanelConfigtelevision.television.channels.prototypes.UiSpec→television.television.config.ui.StatusBarConfigtelevision.television.channels.prototypes.UiSpec→television.television.config.ui.ThemeOverridestelevision.television.channels.prototypes.UiSpec→television.television.config.ui.UiConfig
- Direction
- channels.prototypes uses config.ui, so a change to config.ui can break channels.prototypes, while a change to channels.prototypes can't break config.ui.
- Position
- Below the diagonal: channels.prototypes uses a module listed above it, which is the healthy direction.
35→2 screen.results uses cli.args✕
- Connections
- 2 pairs of types, where a type in screen.results uses a type in cli.args.
- The types involved
television.television.screen.results.results$module→television.television.cli.args.BorderTypetelevision.television.screen.results.results$module→television.television.cli.args.InputPosition
- Direction
- screen.results uses cli.args, so a change to cli.args can break screen.results, while a change to screen.results can't break cli.args.
- Position
- Below the diagonal: screen.results uses a module listed above it, which is the healthy direction.
35→4 screen.results uses event✕
- Connections
- 1 pair of types, where a type in screen.results uses a type in event.
- The types involved
television.television.screen.results.results$module→television.television.event.Key
- Direction
- screen.results uses event, so a change to event can break screen.results, while a change to screen.results can't break event.
- Position
- Below the diagonal: screen.results uses a module listed above it, which is the healthy direction.
35→14 screen.results uses screen.colors✕
- Connections
- 1 pair of types, where a type in screen.results uses a type in screen.colors.
- The types involved
television.television.screen.results.results$module→television.television.screen.colors.Colorscheme
- Direction
- screen.results uses screen.colors, so a change to screen.colors can break screen.results, while a change to screen.results can't break screen.colors.
- Position
- Below the diagonal: screen.results uses a module listed above it, which is the healthy direction.
35→32 screen.results uses config.ui✕
- Connections
- 1 pair of types, where a type in screen.results uses a type in config.ui.
- The types involved
television.television.screen.results.results$module→television.television.config.ui.Padding
- Direction
- screen.results uses config.ui, so a change to config.ui can break screen.results, while a change to screen.results can't break config.ui.
- Position
- Below the diagonal: screen.results uses a module listed above it, which is the healthy direction.
36→3 cable uses config.keybindings✕
- Connections
- 1 pair of types, where a type in cable uses a type in config.keybindings.
- The types involved
television.television.cable.Cable→television.television.config.keybindings.Keybindings
- Direction
- cable uses config.keybindings, so a change to config.keybindings can break cable, while a change to cable can't break config.keybindings.
- Position
- Below the diagonal: cable uses a module listed above it, which is the healthy direction.
36→4 cable uses event✕
- Connections
- 1 pair of types, where a type in cable uses a type in event.
- The types involved
television.television.cable.Cable→television.television.event.Key
- Direction
- cable uses event, so a change to event can break cable, while a change to cable can't break event.
- Position
- Below the diagonal: cable uses a module listed above it, which is the healthy direction.
36→34 cable uses channels.prototypes✕
- Connections
- 3 pairs of types, where a type in cable uses a type in channels.prototypes.
- The types involved
television.television.cable.Cable→television.television.channels.prototypes.ChannelPrototypetelevision.television.cable.CableSpec→television.television.channels.prototypes.ChannelPrototypetelevision.television.cable.cable$module→television.television.channels.prototypes.ChannelPrototype
- Direction
- cable uses channels.prototypes, so a change to channels.prototypes can break cable, while a change to cable can't break channels.prototypes.
- Position
- Below the diagonal: cable uses a module listed above it, which is the healthy direction.
37→5 channels.channel uses matcher.injector✕
- Connections
- 1 pair of types, where a type in channels.channel uses a type in matcher.injector.
- The types involved
television.television.channels.channel.channel$module→television.television.matcher.injector.Injector
- Direction
- channels.channel uses matcher.injector, so a change to matcher.injector can break channels.channel, while a change to channels.channel can't break matcher.injector.
- Position
- Below the diagonal: channels.channel uses a module listed above it, which is the healthy direction.
37→11 channels.channel uses matcher✕
- Connections
- 3 pairs of types, where a type in channels.channel uses a type in matcher.
- The types involved
television.television.channels.channel.Channel→television.television.matcher.Matchertelevision.television.channels.channel.Channel→television.television.matcher.MatcherConfigtelevision.television.channels.channel.ChannelKind→television.television.matcher.MatcherConfig
- Direction
- channels.channel uses matcher, so a change to matcher can break channels.channel, while a change to channels.channel can't break matcher.
- Position
- Below the diagonal: channels.channel uses a module listed above it, which is the healthy direction.
37→19 channels.channel uses channels.entry✕
- Connections
- 1 pair of types, where a type in channels.channel uses a type in channels.entry.
- The types involved
television.television.channels.channel.Channel→television.television.channels.entry.Entry
- Direction
- channels.channel uses channels.entry, so a change to channels.entry can break channels.channel, while a change to channels.channel can't break channels.entry.
- Position
- Below the diagonal: channels.channel uses a module listed above it, which is the healthy direction.
37→34 channels.channel uses channels.prototypes✕
- Connections
- 5 pairs of types, where a type in channels.channel uses a type in channels.prototypes.
- The types involved
television.television.channels.channel.Channel→television.television.channels.prototypes.CommandSpectelevision.television.channels.channel.Channel→television.television.channels.prototypes.Templatetelevision.television.channels.channel.ChannelKind→television.television.channels.prototypes.CommandSpectelevision.television.channels.channel.ChannelKind→television.television.channels.prototypes.Templatetelevision.television.channels.channel.channel$module→television.television.channels.prototypes.CommandSpec
- Direction
- channels.channel uses channels.prototypes, so a change to channels.prototypes can break channels.channel, while a change to channels.channel can't break channels.prototypes.
- Position
- Below the diagonal: channels.channel uses a module listed above it, which is the healthy direction.
38→6 channels.entry_processor uses matcher.matched_item✕
- Connections
- 4 pairs of types, where a type in channels.entry_processor uses a type in matcher.matched_item.
- The types involved
television.television.channels.entry_processor.AnsiProcessor→television.television.matcher.matched_item.MatchedItemtelevision.television.channels.entry_processor.DisplayProcessor→television.television.matcher.matched_item.MatchedItemtelevision.television.channels.entry_processor.EntryProcessor→television.television.matcher.matched_item.MatchedItemtelevision.television.channels.entry_processor.PlainProcessor→television.television.matcher.matched_item.MatchedItem
- Direction
- channels.entry_processor uses matcher.matched_item, so a change to matcher.matched_item can break channels.entry_processor, while a change to channels.entry_processor can't break matcher.matched_item.
- Position
- Below the diagonal: channels.entry_processor uses a module listed above it, which is the healthy direction.
38→19 channels.entry_processor uses channels.entry✕
- Connections
- 4 pairs of types, where a type in channels.entry_processor uses a type in channels.entry.
- The types involved
television.television.channels.entry_processor.AnsiProcessor→television.television.channels.entry.Entrytelevision.television.channels.entry_processor.DisplayProcessor→television.television.channels.entry.Entrytelevision.television.channels.entry_processor.EntryProcessor→television.television.channels.entry.Entrytelevision.television.channels.entry_processor.PlainProcessor→television.television.channels.entry.Entry
- Direction
- channels.entry_processor uses channels.entry, so a change to channels.entry can break channels.entry_processor, while a change to channels.entry_processor can't break channels.entry.
- Position
- Below the diagonal: channels.entry_processor uses a module listed above it, which is the healthy direction.
38→34 channels.entry_processor uses channels.prototypes✕
- Connections
- 4 pairs of types, where a type in channels.entry_processor uses a type in channels.prototypes.
- The types involved
television.television.channels.entry_processor.AnsiProcessor→television.television.channels.prototypes.Templatetelevision.television.channels.entry_processor.DisplayProcessor→television.television.channels.prototypes.Templatetelevision.television.channels.entry_processor.EntryProcessor→television.television.channels.prototypes.Templatetelevision.television.channels.entry_processor.PlainProcessor→television.television.channels.prototypes.Template
- Direction
- channels.entry_processor uses channels.prototypes, so a change to channels.prototypes can break channels.entry_processor, while a change to channels.entry_processor can't break channels.prototypes.
- Position
- Below the diagonal: channels.entry_processor uses a module listed above it, which is the healthy direction.
39→2 television.television uses cli.args✕
- Connections
- 1 pair of types, where a type in television.television uses a type in cli.args.
- The types involved
television.television.television$module→television.television.cli.args.Command
- Direction
- television.television uses cli.args, so a change to cli.args can break television.television, while a change to television.television can't break cli.args.
- Position
- Below the diagonal: television.television uses a module listed above it, which is the healthy direction.
39→8 television.television uses cli✕
- Connections
- 1 pair of types, where a type in television.television uses a type in cli.
- The types involved
television.television.television$module→television.television.cli.ChannelCli
- Direction
- television.television uses cli, so a change to cli can break television.television, while a change to television.television can't break cli.
- Position
- Below the diagonal: television.television uses a module listed above it, which is the healthy direction.
39→9 television.television uses config.shell_integration✕
- Connections
- 1 pair of types, where a type in television.television uses a type in config.shell_integration.
- The types involved
television.television.television$module→television.television.config.shell_integration.ShellIntegrationConfig
- Direction
- television.television uses config.shell_integration, so a change to config.shell_integration can break television.television, while a change to television.television can't break config.shell_integration.
- Position
- Below the diagonal: television.television uses a module listed above it, which is the healthy direction.
39→15 television.television uses config✕
- Connections
- 1 pair of types, where a type in television.television uses a type in config.
- The types involved
television.television.television$module→television.television.config.Config
- Direction
- television.television uses config, so a change to config can break television.television, while a change to television.television can't break config.
- Position
- Below the diagonal: television.television uses a module listed above it, which is the healthy direction.
39→34 television.television uses channels.prototypes✕
- Connections
- 1 pair of types, where a type in television.television uses a type in channels.prototypes.
- The types involved
television.television.television$module→television.television.channels.prototypes.ChannelPrototype
- Direction
- television.television uses channels.prototypes, so a change to channels.prototypes can break television.television, while a change to television.television can't break channels.prototypes.
- Position
- Below the diagonal: television.television uses a module listed above it, which is the healthy direction.
39→36 television.television uses cable✕
- Connections
- 1 pair of types, where a type in television.television uses a type in cable.
- The types involved
television.television.television$module→television.television.cable.Cable
- Direction
- television.television uses cable, so a change to cable can break television.television, while a change to television.television can't break cable.
- Position
- Below the diagonal: television.television uses a module listed above it, which is the healthy direction.
40→1 app uses action✕
- Connections
- 1 pair of types, where a type in app uses a type in action.
- The types involved
television.television.app.App→television.television.action.Action
- Direction
- app uses action, so a change to action can break app, while a change to app can't break action.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
40→4 app uses event✕
- Connections
- 2 pairs of types, where a type in app uses a type in event.
- The types involved
television.television.app.App→television.television.event.Eventtelevision.television.app.AppOutput→television.television.event.Key
- Direction
- app uses event, so a change to event can break app, while a change to app can't break event.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
40→24 app uses television✕
- Connections
- 1 pair of types, where a type in app uses a type in television.
- The types involved
television.television.app.App→television.television.television.Television
- Direction
- app uses television, so a change to television can break app, while a change to app can't break television.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
40→26 app uses config.layers✕
- Connections
- 1 pair of types, where a type in app uses a type in config.layers.
- The types involved
television.television.app.App→television.television.config.layers.ConfigLayers
- Direction
- app uses config.layers, so a change to config.layers can break app, while a change to app can't break config.layers.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
40→34 app uses channels.prototypes✕
- Connections
- 1 pair of types, where a type in app uses a type in channels.prototypes.
- The types involved
television.television.app.App→television.television.channels.prototypes.ActionSpec
- Direction
- app uses channels.prototypes, so a change to channels.prototypes can break app, while a change to app can't break channels.prototypes.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
40→36 app uses cable✕
- Connections
- 1 pair of types, where a type in app uses a type in cable.
- The types involved
television.television.app.App→television.television.cable.Cable
- Direction
- app uses cable, so a change to cable can break app, while a change to app can't break cable.
- Position
- Below the diagonal: app 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 — Event Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 60 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 13 | Medium |
Roadmap
First, establish architectural clarity by documenting significant design decisions in a dedicated ADR folder. Next, strengthen type safety by enabling strict null checking in the base TypeScript configuration and resolving existing assertions to prevent runtime errors. Then, improve observability by replacing interpolated log messages with structured logging to ensure consistent data parsing. Finally, reduce code complexity by refactoring the most intricate functions to lower their cognitive load and improve maintainability.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +4.0 pts | Low | ADR Quality |
| 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.8 pts | Medium | Architecture documentation |
| 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 `?`). | +3.8 pts | Medium | Nullable reference types |
| Interpolated log message defeats structured logging | +3.5 pts | Medium | Structured logging |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.2 pts | Low | Bus Factor |
| Bring the 16 bodies over 15 down to 15 or less in Cognitive Complexity — start with App::handle_actions (cognitive 67), ConfigLayers::merge (cognitive 63), Television::handle_action (cognitive 52). | +2.2 pts | High | Cognitive Complexity |
| Resolve the 1 Yanked release finding(s) in Dependency Hygiene. | +1.0 pts | Low | Dependency Hygiene |
| Bring the 11 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ConfigLayers::merge (cyclomatic 49), Television::handle_action (cyclomatic 49), App::handle_actions (cyclomatic 33). | +1.8 pts | High | Cyclomatic Complexity |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| television/television.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| television/app.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| television/channels/channel.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| benches/main/ui.rs | 6.2 | Mixed | Change Coupling: Boundary-crossing change coupling: ui.rs ↔ main.rs |
| website/src/theme/SearchBar/index.tsx | 6.9 | Mixed | Explicit Debt: TodoComment |
| television/config/layers.rs | 7.1 | Near-clean | Cyclomatic Complexity: ConfigLayers::merge (cyclomatic 49) |
| television/utils/input.rs | 7.2 | Near-clean | Cyclomatic Complexity: Input::handle (cyclomatic 27) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 63 of 63 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 63 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, 184 of 205 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) 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. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not included — the Rust suite (repository root, 46 test files) did not finish re-running within its budget: the Cargo suite did not finish re-running within its tier budget.
- D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `website/docusaurus.config.ts` 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.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Python, Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Python, Rust 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.
- X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 49 further occurrence(s) are not listed individually; the score already reflects all 89.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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
11 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ConfigLayers::merge at 49. A further 4 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Action::description at 50 — 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 functions was excluded, so the exclusion is disclosed nowhere in the file itself: television/action.rs (Action::description at 50), television/screen/help_panel.rs (television::television::screen::help_panel::help_section at 34). 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 11 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ConfigLayers::merge (cyclomatic 49), Television::handle_action (cyclomatic 49), App::handle_actions (cyclomatic 33). — 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 11 together lifts Cyclomatic Complexity from 7.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
16 method(s) exceeded the cognitive complexity threshold of 15; the worst was App::handle_actions at 67.
What to do
- Bring the 16 bodies over 15 down to 15 or less in Cognitive Complexity — start with App::handle_actions (cognitive 67), ConfigLayers::merge (cognitive 63), Television::handle_action (cognitive 52). — 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 16 together lifts Cognitive Complexity from 7.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
17 god class(es) detected.
What to do
- Resolve the 6 MethodTooLong finding(s) in God Classes — start with layers.rs, input.rs, layout.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 3 TooManyFields finding(s) in God Classes — start with layers.rs, args.rs, mod.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 ClassTooLong finding(s) in God Classes — start with television.rs, layers.rs, app.rs. — One of this dimension's main actionable groups (3 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
7 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with app.rs, input.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with result_item.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with action_picker.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 34 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with entry.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
387 test methods: 238 unit, 149 integration, 0 BDD, 0 e2e. The Rust suite contributes 387 `#[test]` function(s) across 46 file(s) declaring at least one; its unit/integration split is Cargo's own — 14 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D12 · Dependency Hygiene
10 outdated, 1 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
What to do
- Resolve the 1 Yanked release finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 351 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: television/config/layers.rs (7×49=343); television/app.rs (5×28=140) Repeated repair below the complexity floor: television/tui.rs (5 of 6 changes were fixes)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with layers.rs, app.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with tui.rs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
8 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is television/previewer/mod.rs. Counted over 54 of the 72 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 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
13 deducted task-comment markers across 23265 LoC (0.1/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 8 FixmeComment finding(s) in Explicit Debt — start with layout.rs (2), remote_control.rs, app.rs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 5 TodoComment finding(s) in Explicit Debt — start with index.tsx (3), main.rs, prototypes.rs. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 26 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (Cargo, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
60 finding(s): 0 critical, 58 high, 2 medium, 0 low. 40 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `docs/community/channels-unix.md`, `television/utils/strings.rs` (line 498), `website/docusaurus.config.ts` (line 64, line 124) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- No action in Static Analysis (SAST) — all 40 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (40 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
5 finding(s): 0 critical, 0 high, 5 medium, 0 low.
What to do
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 54 of the 72 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: channel.rs↔remote_control.rs 56%; ui.rs↔draw.rs 53%; ui.rs↔television.rs 53%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with ui.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with channel.rs (2), ui.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with television.rs. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 0 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.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
ES1 · Fold determinism
ES2 · Immutable events
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
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
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
What to do
- Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `error!` at line 143 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/app.rs:143
- `error!` at line 160 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/app.rs:160
- `debug!` at line 200 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/app.rs:200
- `debug!` at line 249 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/app.rs:249
- `debug!` at line 376 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/app.rs:376
- `error!` at line 417 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/app.rs:417
- `error!` at line 421 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/app.rs:421
- `debug!` at line 467 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/app.rs:467
- `trace!` at line 494 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/app.rs:494
- `trace!` at line 529 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/app.rs:529
- `debug!` at line 615 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/app.rs:615
- `error!` at line 690 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/app.rs:690
- `error!` at line 696 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/app.rs:696
- `error!` at line 726 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/app.rs:726
- `error!` at line 730 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/app.rs:730
- `error!` at line 734 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/app.rs:734
- `error!` at line 111 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/cable.rs:111
- `debug!` at line 131 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/cable.rs:131
- `debug!` at line 172 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/cable.rs:172
- `debug!` at line 174 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/cable.rs:174
- `error!` at line 189 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/cable.rs:189
- `debug!` at line 202 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/cable.rs:202
- `error!` at line 13 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/errors.rs:13
- `debug!` at line 285 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/event.rs:285
- `warn!` at line 363 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/event.rs:363
- `trace!` at line 413 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/event.rs:413
- `debug!` at line 145 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/frecency.rs:145
- `debug!` at line 158 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/frecency.rs:158
- `debug!` at line 179 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/frecency.rs:179
- `debug!` at line 210 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/frecency.rs:210
- `debug!` at line 219 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/frecency.rs:219
- `debug!` at line 304 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/frecency.rs:304
- `debug!` at line 56 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/gh.rs:56
- `debug!` at line 171 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/history.rs:171
- `debug!` at line 177 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/history.rs:177
- `debug!` at line 67 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/main.rs:67
- `info!` at line 116 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/main.rs:116
- `debug!` at line 199 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/main.rs:199
- `debug!` at line 223 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/main.rs:223
- `debug!` at line 230 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — television/main.rs:230
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- This repository commits no tsconfig, so whatever type-checks it uses tsc's own defaults, in which `strict` and `strictNullChecks` are OFF: `string` admits `null` and `undefined`, and a value that is null is compiled through to the property access that throws. If the build passes `--strict` on a command line instead, put it in a committed tsconfig — this check reads configuration, and configuration is all it can read.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 57% | Adequate — gated by X4, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 82% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 59% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 67% | Strong | Solid. |
| Security | 70% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| Performance | 91% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 58 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. 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 — no exported interface declares behaviour
- 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 did not expose a crawlable HTTP endpoint in time — no runtime evidence 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 — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source 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 field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~4299 lines of test source are present (.rs) 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
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Python, Rust, TypeScript not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .py, .rs, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this Cargo build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- 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 — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 1 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- 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 26 current-state document(s) make no claim of a kind M4 checks. 7 claim(s) of kinds M4 does not check were not checked (command argument 1, environment variable 6); M4 checks only links and versions.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- S1 Web-Security Posture — No web surface: 72 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 59 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: ui.rs ↔ main.rs benches/main/ui.rs:1
Serious — 86 finding(s)
- FixmeComment tests/pty/layout.rs:42
- FixmeComment tests/pty/layout.rs:334
- FixmeComment tests/pty/remote_control.rs:16
- FixmeComment television/app.rs:454
- FixmeComment television/television.rs:656
- FixmeComment television/previewer/state.rs:56
- FixmeComment television/channels/channel.rs:394
- FixmeComment benches/main/ui.rs:34
- television::television::screen::input::draw_input_box (cognitive 38) television/screen/input.rs:34
- television::television::render::render (cognitive 29) television/render.rs:55
- television::television::screen::status_bar::draw_status_bar (cognitive 24) television/screen/status_bar.rs:19
- television::television::screen::preview::draw_content_outer_block (cognitive 18) television/screen/preview.rs:134
- television::television::screen::results::draw_results_list (cognitive 17) television/screen/results.rs:21
- television::television::screen::result_item::build_entry_spans (cognitive 16) television/screen/result_item.rs:123
- television::television::screen::result_item::build_entry_spans_styled (cognitive 16) television/screen/result_item.rs:194
- MethodTooLong: ConfigLayers.merge television/config/layers.rs:57
- MethodTooLong: Input.handle television/utils/input.rs:94
- MethodTooLong: Layout.build television/screen/layout.rs:190
- MethodTooLong: Television.handle_action television/television.rs:955
- MethodTooLong: Theme.deserialize television/config/themes.rs:260
- MethodTooLong: App.handle_actions television/app.rs:516
- TodoComment website/src/theme/SearchBar/index.tsx:194
- TodoComment website/src/theme/SearchBar/index.tsx:270
- TodoComment website/src/theme/SearchBar/index.tsx:290
- TodoComment television/main.rs:99
- TodoComment television/channels/prototypes.rs:218
- television::television::utils::ansi::apply_sgr (cyclomatic 29) television/utils/ansi.rs:160
- television::television::screen::input::draw_input_box (cyclomatic 20) television/screen/input.rs:34
- television::television::screen::status_bar::draw_status_bar (cyclomatic 18) television/screen/status_bar.rs:19
- TooManyFields: MergedConfig television/config/layers.rs:635
- TooManyFields: Cli television/cli/args.rs:11
- TooManyFields: ChannelCli television/cli/mod.rs:65
- ClassTooLong: Television television/television.rs:74
- ClassTooLong: ConfigLayers television/config/layers.rs:21
- ClassTooLong: App television/app.rs:27
- Change coupling: channel.rs ↔ remote_control.rs television/channels/channel.rs:1
- Change coupling: ui.rs ↔ draw.rs television/config/ui.rs:1
- Change coupling: channel.rs ↔ worker.rs television/channels/channel.rs:1
- REDACTED
- REDACTED
- REDACTED
- App::handle_actions (cyclomatic 33) television/app.rs:516
- App::run (cyclomatic 28) television/app.rs:278
- Hotspot: television/config/layers.rs television/config/layers.rs:57
- Hotspot: television/app.rs television/app.rs:278
- App::handle_actions (cognitive 67) television/app.rs:516
- App::run (cognitive 46) television/app.rs:278
- REDACTED
- REDACTED
- FileTooLong: television/television.rs television/television.rs
- FileTooLong: config/layers.rs television/config/layers.rs
- FunctionTooLong: television::television::screen::input::draw_input_box television/screen/input.rs:34
- FunctionTooLong: television::television::draw::draw television/draw.rs:198
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (8 lines × 2) television/app.rs:551
- Duplicated block (8 lines × 2) television/utils/input.rs:190
- ConfigLayers::merge (cyclomatic 49) television/config/layers.rs:57
- Television::handle_action (cyclomatic 49) television/television.rs:955
- Layout::build (cyclomatic 27) television/screen/layout.rs:190
- Input::handle (cyclomatic 27) television/utils/input.rs:94
- Theme::merge_with_overrides (cyclomatic 20) television/config/themes.rs:157
- EventLoop::new (cyclomatic 16) television/event.rs:299
- Yanked release: clipboard-win
- Repeated repair: television/tui.rs television/tui.rs:244
- ConfigLayers::merge (cognitive 63) television/config/layers.rs:57
- Television::handle_action (cognitive 52) television/television.rs:955
- Layout::build (cognitive 50) television/screen/layout.rs:190
- Input::handle (cognitive 40) television/utils/input.rs:94
- Theme::merge_with_overrides (cognitive 19) television/config/themes.rs:157
- EventLoop::new (cognitive 18) television/event.rs:299
- Worker::run (cognitive 16) television/matcher/worker.rs:243
- TooManyMethods: Television television/television.rs:74
- REDACTED
- Change-coupling hub: television.rs → ui.rs, preview.rs, results.rs television/television.rs
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (6 lines × 2) television/screen/result_item.rs:152
- Duplicated block (7 lines × 2) television/channels/action_picker.rs:125
- Duplicated block (10 lines × 2) television/cli/mod.rs:199
- Duplicated block (9 lines × 2) television/config/mod.rs:284
- Duplicated block (7 lines × 5) television/cli/mod.rs:202
- Low cohesion: Entry (LCOM4 4) television/channels/entry.rs:11
Minor — 50 finding(s)
- Interpolated log message defeats structured logging television/app.rs:143
- Interpolated log message defeats structured logging television/app.rs:160
- Interpolated log message defeats structured logging television/app.rs:200
- Interpolated log message defeats structured logging television/app.rs:249
- Interpolated log message defeats structured logging television/app.rs:376
- Interpolated log message defeats structured logging television/app.rs:417
- Interpolated log message defeats structured logging television/app.rs:421
- Interpolated log message defeats structured logging television/app.rs:467
- Interpolated log message defeats structured logging television/app.rs:494
- Interpolated log message defeats structured logging television/app.rs:529
- Interpolated log message defeats structured logging television/app.rs:615
- Interpolated log message defeats structured logging television/app.rs:690
- Interpolated log message defeats structured logging television/app.rs:696
- Interpolated log message defeats structured logging television/app.rs:726
- Interpolated log message defeats structured logging television/app.rs:730
- Interpolated log message defeats structured logging television/app.rs:734
- Interpolated log message defeats structured logging television/cable.rs:111
- Interpolated log message defeats structured logging television/cable.rs:131
- Interpolated log message defeats structured logging television/cable.rs:172
- Interpolated log message defeats structured logging television/cable.rs:174
- Interpolated log message defeats structured logging television/cable.rs:189
- Interpolated log message defeats structured logging television/cable.rs:202
- Interpolated log message defeats structured logging television/errors.rs:13
- Interpolated log message defeats structured logging television/event.rs:285
- Interpolated log message defeats structured logging television/event.rs:363
- Off-boarding risk: anonymized user #1
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No release approval gate
- Strict null checking is not enabled everywhere the repository type-checks
- Silent fallback default on Err television/config/themes.rs:133
Minor — 10 finding(s)
- Outdated: clap
- Outdated: clap_complete
- Outdated: lazy-regex
- Outdated: libc
- Outdated: serde_json
- Outdated: serde_with
- Outdated: signal-hook
- Outdated: smallvec
- Outdated: tokio
- Outdated: ureq
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-620ef632e7a3470fb753afe7df518f87/history.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-620ef632e7a3470fb753afe7df518f87/tree.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 60 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 5 | 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) — `website/docusaurus.config.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |