Executive summary
Canop/broot falls short of our standard for production, in part because we found no recorded design decisions and no architecture document or diagram. It scores 65 out of 100 and is rated Adequate, and two of its nine critical findings are security problems in the build pipeline.
Maturity, at 57, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 9 points. Having someone learn and document the file no active contributor knows is another step, worth about 3 points. Raising Maturity to 70 would lift the score to about 69.
Two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Six sets of files in separate parts keep changing together, which points to hidden dependencies, and one part of the code is no longer understood by anyone working on it. Having someone learn the forgotten files, pinning each tool to an exact version and making the hidden dependencies explicit would close these risks.
The product code is 38,678 lines, about €46,000 to rebuild.
If Maturity rose from 57 to 70, the lowest score rated Strong, the score would rise from 65 to about 69.
New since the last survey: 6 findings
- Cyclomatic Complexity · Server::new (cyclomatic 16) src/net/server.rs
- Cognitive Complexity · ExecutionBuilder::expand_tokens (cognitive 21) src/verb/execution_builder.rs
- Churn × Complexity Hotspots · Hotspot: src/browser/browser_state.rs src/browser/browser_state.rs
- Churn × Complexity Hotspots · Hotspot: src/verb/execution_builder.rs src/verb/execution_builder.rs
- Change Coupling · Change coupling: app_context.rs ↔ col.rs src/app/app_context.rs
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 4 findings
- Cognitive Complexity · ExecutionBuilder::exec_token (cognitive 21) src/verb/execution_builder.rs
- Churn × Complexity Hotspots · Hotspot: src/image/source_image.rs src/image/source_image.rs
- Churn × Complexity Hotspots · Hotspot: src/kitty/detect_support.rs src/kitty/detect_support.rs
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €46,000 · Estimate
| Cost to rebuild | €15,000 to €78,000, for 257 to 816 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 65. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 38,678 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 app.app_state | 2 app.cmd_result | 3 app.mode | 4 app.state_type | 5 command.scroll | 6 command.trigger_type | 7 pattern.pattern | 8 skin.style_map | 9 task_sync | 10 verb.internal_execution | 11 verb.verb_invocation | 12 app.selection | 13 conf.conf | 14 pattern.input_pattern | 15 skin.panel_skin | 16 verb.invocation_parser | 17 app.sel_info | 18 tree.tree_options | 19 verb.verb | 20 verb.verb_store | 21 app.app_context | 22 command.command | 23 command.panel_input | 24 display.screen | 25 tree.tree_line | 26 verb.execution_builder | 27 app.cmd_context | 28 app.display_context | 29 tree.tree | 30 app.panel | 31 app.panel_state | 32 preview.preview | 33 verb.internal_focus | 34 app.app_panels | 35 browser.browser_state | 36 filesystems.filesystems_state | 37 help.help_state | 38 preview.preview_state | 39 stage.stage_state | 40 trash.trash_state |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 app.app_state | ||||||||||||||||||||||||||||||||||||||||
| 2 app.cmd_result | ||||||||||||||||||||||||||||||||||||||||
| 3 app.mode | ||||||||||||||||||||||||||||||||||||||||
| 4 app.state_type | ||||||||||||||||||||||||||||||||||||||||
| 5 command.scroll | ||||||||||||||||||||||||||||||||||||||||
| 6 command.trigger_type | ||||||||||||||||||||||||||||||||||||||||
| 7 pattern.pattern | ||||||||||||||||||||||||||||||||||||||||
| 8 skin.style_map | ||||||||||||||||||||||||||||||||||||||||
| 9 task_sync | ||||||||||||||||||||||||||||||||||||||||
| 10 verb.internal_execution | ||||||||||||||||||||||||||||||||||||||||
| 11 verb.verb_invocation | ||||||||||||||||||||||||||||||||||||||||
| 12 app.selection | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 conf.conf | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 pattern.input_pattern | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 skin.panel_skin | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 verb.invocation_parser | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 app.sel_info | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 tree.tree_options | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 verb.verb | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 20 verb.verb_store | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 21 app.app_context | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 22 command.command | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 23 command.panel_input | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||
| 24 display.screen | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 tree.tree_line | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 verb.execution_builder | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 27 app.cmd_context | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 app.display_context | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 tree.tree | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 app.panel | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 31 app.panel_state | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||
| 32 preview.preview | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 33 verb.internal_focus | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||
| 34 app.app_panels | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 2 | ||||||||||||||||||||||||||||
| 35 browser.browser_state | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||
| 36 filesystems.filesystems_state | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||
| 37 help.help_state | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||
| 38 preview.preview_state | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||
| 39 stage.stage_state | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||
| 40 trash.trash_state | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
12→21 app.selection uses app.app_context part of a loop✕
- Connections
- 1 pair of types, where a type in app.selection uses a type in app.app_context.
- The types involved
broot.app.selection.Selection→broot.app.app_context.AppContext
- Direction
- app.selection uses app.app_context, so a change to app.app_context can break app.selection, while a change to app.selection can't break app.app_context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→3 conf.conf uses app.mode✕
- Connections
- 1 pair of types, where a type in conf.conf uses a type in app.mode.
- The types involved
broot.conf.conf.Conf→broot.app.mode.Mode
- Direction
- conf.conf uses app.mode, so a change to app.mode can break conf.conf, while a change to conf.conf can't break app.mode.
- Position
- Below the diagonal: conf.conf uses a module listed above it, which is the healthy direction.
14→7 pattern.input_pattern uses pattern.pattern✕
- Connections
- 1 pair of types, where a type in pattern.input_pattern uses a type in pattern.pattern.
- The types involved
broot.pattern.input_pattern.InputPattern→broot.pattern.pattern.Pattern
- Direction
- pattern.input_pattern uses pattern.pattern, so a change to pattern.pattern can break pattern.input_pattern, while a change to pattern.input_pattern can't break pattern.pattern.
- Position
- Below the diagonal: pattern.input_pattern uses a module listed above it, which is the healthy direction.
14→21 pattern.input_pattern uses app.app_context part of a loop✕
- Connections
- 1 pair of types, where a type in pattern.input_pattern uses a type in app.app_context.
- The types involved
broot.pattern.input_pattern.InputPattern→broot.app.app_context.AppContext
- Direction
- pattern.input_pattern uses app.app_context, so a change to app.app_context can break pattern.input_pattern, while a change to pattern.input_pattern can't break app.app_context.
- Position
- Above the diagonal, so 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→8 skin.panel_skin uses skin.style_map✕
- Connections
- 1 pair of types, where a type in skin.panel_skin uses a type in skin.style_map.
- The types involved
broot.skin.panel_skin.PanelSkin→broot.skin.style_map.StyleMap
- Direction
- skin.panel_skin uses skin.style_map, so a change to skin.style_map can break skin.panel_skin, while a change to skin.panel_skin can't break skin.style_map.
- Position
- Below the diagonal: skin.panel_skin uses a module listed above it, which is the healthy direction.
16→11 verb.invocation_parser uses verb.verb_invocation✕
- Connections
- 1 pair of types, where a type in verb.invocation_parser uses a type in verb.verb_invocation.
- The types involved
broot.verb.invocation_parser.InvocationParser→broot.verb.verb_invocation.VerbInvocation
- Direction
- verb.invocation_parser uses verb.verb_invocation, so a change to verb.verb_invocation can break verb.invocation_parser, while a change to verb.invocation_parser can't break verb.verb_invocation.
- Position
- Below the diagonal: verb.invocation_parser uses a module listed above it, which is the healthy direction.
17→12 app.sel_info uses app.selection✕
- Connections
- 2 pairs of types, where a type in app.sel_info uses a type in app.selection.
- The types involved
broot.app.sel_info.SelInfo→broot.app.selection.Selectionbroot.app.sel_info.SelInfo→broot.app.selection.SelectionType
- Direction
- app.sel_info uses app.selection, so a change to app.selection can break app.sel_info, while a change to app.sel_info can't break app.selection.
- Position
- Below the diagonal: app.sel_info uses a module listed above it, which is the healthy direction.
18→13 tree.tree_options uses conf.conf✕
- Connections
- 1 pair of types, where a type in tree.tree_options uses a type in conf.conf.
- The types involved
broot.tree.tree_options.TreeOptions→broot.conf.conf.Conf
- Direction
- tree.tree_options uses conf.conf, so a change to conf.conf can break tree.tree_options, while a change to tree.tree_options can't break conf.conf.
- Position
- Below the diagonal: tree.tree_options uses a module listed above it, which is the healthy direction.
18→14 tree.tree_options uses pattern.input_pattern✕
- Connections
- 1 pair of types, where a type in tree.tree_options uses a type in pattern.input_pattern.
- The types involved
broot.tree.tree_options.TreeOptions→broot.pattern.input_pattern.InputPattern
- Direction
- tree.tree_options uses pattern.input_pattern, so a change to pattern.input_pattern can break tree.tree_options, while a change to tree.tree_options can't break pattern.input_pattern.
- Position
- Below the diagonal: tree.tree_options uses a module listed above it, which is the healthy direction.
19→1 verb.verb uses app.app_state✕
- Connections
- 1 pair of types, where a type in verb.verb uses a type in app.app_state.
- The types involved
broot.verb.verb.Verb→broot.app.app_state.AppState
- Direction
- verb.verb uses app.app_state, so a change to app.app_state can break verb.verb, while a change to verb.verb can't break app.app_state.
- Position
- Below the diagonal: verb.verb uses a module listed above it, which is the healthy direction.
19→4 verb.verb uses app.state_type✕
- Connections
- 1 pair of types, where a type in verb.verb uses a type in app.state_type.
- The types involved
broot.verb.verb.Verb→broot.app.state_type.PanelStateType
- Direction
- verb.verb uses app.state_type, so a change to app.state_type can break verb.verb, while a change to verb.verb can't break app.state_type.
- Position
- Below the diagonal: verb.verb uses a module listed above it, which is the healthy direction.
19→11 verb.verb uses verb.verb_invocation✕
- Connections
- 1 pair of types, where a type in verb.verb uses a type in verb.verb_invocation.
- The types involved
broot.verb.verb.Verb→broot.verb.verb_invocation.VerbInvocation
- Direction
- verb.verb uses verb.verb_invocation, so a change to verb.verb_invocation can break verb.verb, while a change to verb.verb can't break verb.verb_invocation.
- Position
- Below the diagonal: verb.verb uses a module listed above it, which is the healthy direction.
19→12 verb.verb uses app.selection✕
- Connections
- 1 pair of types, where a type in verb.verb uses a type in app.selection.
- The types involved
broot.verb.verb.Verb→broot.app.selection.Selection
- Direction
- verb.verb uses app.selection, so a change to app.selection can break verb.verb, while a change to verb.verb can't break app.selection.
- Position
- Below the diagonal: verb.verb uses a module listed above it, which is the healthy direction.
19→16 verb.verb uses verb.invocation_parser✕
- Connections
- 1 pair of types, where a type in verb.verb uses a type in verb.invocation_parser.
- The types involved
broot.verb.verb.Verb→broot.verb.invocation_parser.InvocationParser
- Direction
- verb.verb uses verb.invocation_parser, so a change to verb.invocation_parser can break verb.verb, while a change to verb.verb can't break verb.invocation_parser.
- Position
- Below the diagonal: verb.verb uses a module listed above it, which is the healthy direction.
19→17 verb.verb uses app.sel_info✕
- Connections
- 1 pair of types, where a type in verb.verb uses a type in app.sel_info.
- The types involved
broot.verb.verb.Verb→broot.app.sel_info.SelInfo
- Direction
- verb.verb uses app.sel_info, so a change to app.sel_info can break verb.verb, while a change to verb.verb can't break app.sel_info.
- Position
- Below the diagonal: verb.verb uses a module listed above it, which is the healthy direction.
19→21 verb.verb uses app.app_context part of a loop✕
- Connections
- 1 pair of types, where a type in verb.verb uses a type in app.app_context.
- The types involved
broot.verb.verb.Verb→broot.app.app_context.AppContext
- Direction
- verb.verb uses app.app_context, so a change to app.app_context can break verb.verb, while a change to verb.verb can't break app.app_context.
- Position
- Above the diagonal, so 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 verb.verb_store uses app.state_type✕
- Connections
- 1 pair of types, where a type in verb.verb_store uses a type in app.state_type.
- The types involved
broot.verb.verb_store.VerbStore→broot.app.state_type.PanelStateType
- Direction
- verb.verb_store uses app.state_type, so a change to app.state_type can break verb.verb_store, while a change to verb.verb_store can't break app.state_type.
- Position
- Below the diagonal: verb.verb_store uses a module listed above it, which is the healthy direction.
20→12 verb.verb_store uses app.selection✕
- Connections
- 1 pair of types, where a type in verb.verb_store uses a type in app.selection.
- The types involved
broot.verb.verb_store.VerbStore→broot.app.selection.SelectionType
- Direction
- verb.verb_store uses app.selection, so a change to app.selection can break verb.verb_store, while a change to verb.verb_store can't break app.selection.
- Position
- Below the diagonal: verb.verb_store uses a module listed above it, which is the healthy direction.
20→13 verb.verb_store uses conf.conf✕
- Connections
- 1 pair of types, where a type in verb.verb_store uses a type in conf.conf.
- The types involved
broot.verb.verb_store.VerbStore→broot.conf.conf.Conf
- Direction
- verb.verb_store uses conf.conf, so a change to conf.conf can break verb.verb_store, while a change to verb.verb_store can't break conf.conf.
- Position
- Below the diagonal: verb.verb_store uses a module listed above it, which is the healthy direction.
20→17 verb.verb_store uses app.sel_info✕
- Connections
- 1 pair of types, where a type in verb.verb_store uses a type in app.sel_info.
- The types involved
broot.verb.verb_store.VerbStore→broot.app.sel_info.SelInfo
- Direction
- verb.verb_store uses app.sel_info, so a change to app.sel_info can break verb.verb_store, while a change to verb.verb_store can't break app.sel_info.
- Position
- Below the diagonal: verb.verb_store uses a module listed above it, which is the healthy direction.
20→19 verb.verb_store uses verb.verb✕
- Connections
- 1 pair of types, where a type in verb.verb_store uses a type in verb.verb.
- The types involved
broot.verb.verb_store.VerbStore→broot.verb.verb.Verb
- Direction
- verb.verb_store uses verb.verb, so a change to verb.verb can break verb.verb_store, while a change to verb.verb_store can't break verb.verb.
- Position
- Below the diagonal: verb.verb_store uses a module listed above it, which is the healthy direction.
21→3 app.app_context uses app.mode✕
- Connections
- 1 pair of types, where a type in app.app_context uses a type in app.mode.
- The types involved
broot.app.app_context.AppContext→broot.app.mode.Mode
- Direction
- app.app_context uses app.mode, so a change to app.mode can break app.app_context, while a change to app.app_context can't break app.mode.
- Position
- Below the diagonal: app.app_context uses a module listed above it, which is the healthy direction.
21→13 app.app_context uses conf.conf✕
- Connections
- 1 pair of types, where a type in app.app_context uses a type in conf.conf.
- The types involved
broot.app.app_context.AppContext→broot.conf.conf.Conf
- Direction
- app.app_context uses conf.conf, so a change to conf.conf can break app.app_context, while a change to app.app_context can't break conf.conf.
- Position
- Below the diagonal: app.app_context uses a module listed above it, which is the healthy direction.
21→18 app.app_context uses tree.tree_options✕
- Connections
- 1 pair of types, where a type in app.app_context uses a type in tree.tree_options.
- The types involved
broot.app.app_context.AppContext→broot.tree.tree_options.TreeOptions
- Direction
- app.app_context uses tree.tree_options, so a change to tree.tree_options can break app.app_context, while a change to app.app_context can't break tree.tree_options.
- Position
- Below the diagonal: app.app_context uses a module listed above it, which is the healthy direction.
21→20 app.app_context uses verb.verb_store✕
- Connections
- 1 pair of types, where a type in app.app_context uses a type in verb.verb_store.
- The types involved
broot.app.app_context.AppContext→broot.verb.verb_store.VerbStore
- Direction
- app.app_context uses verb.verb_store, so a change to verb.verb_store can break app.app_context, while a change to app.app_context can't break verb.verb_store.
- Position
- Below the diagonal: app.app_context uses a module listed above it, which is the healthy direction.
22→11 command.command uses verb.verb_invocation✕
- Connections
- 1 pair of types, where a type in command.command uses a type in verb.verb_invocation.
- The types involved
broot.command.command.Command→broot.verb.verb_invocation.VerbInvocation
- Direction
- command.command uses verb.verb_invocation, so a change to verb.verb_invocation can break command.command, while a change to command.command can't break verb.verb_invocation.
- Position
- Below the diagonal: command.command uses a module listed above it, which is the healthy direction.
22→14 command.command uses pattern.input_pattern✕
- Connections
- 1 pair of types, where a type in command.command uses a type in pattern.input_pattern.
- The types involved
broot.command.command.Command→broot.pattern.input_pattern.InputPattern
- Direction
- command.command uses pattern.input_pattern, so a change to pattern.input_pattern can break command.command, while a change to command.command can't break pattern.input_pattern.
- Position
- Below the diagonal: command.command uses a module listed above it, which is the healthy direction.
22→19 command.command uses verb.verb✕
- Connections
- 1 pair of types, where a type in command.command uses a type in verb.verb.
- The types involved
broot.command.command.Command→broot.verb.verb.Verb
- Direction
- command.command uses verb.verb, so a change to verb.verb can break command.command, while a change to command.command can't break verb.verb.
- Position
- Below the diagonal: command.command uses a module listed above it, which is the healthy direction.
22→20 command.command uses verb.verb_store✕
- Connections
- 1 pair of types, where a type in command.command uses a type in verb.verb_store.
- The types involved
broot.command.command.Command→broot.verb.verb_store.VerbStore
- Direction
- command.command uses verb.verb_store, so a change to verb.verb_store can break command.command, while a change to command.command can't break verb.verb_store.
- Position
- Below the diagonal: command.command uses a module listed above it, which is the healthy direction.
23→1 command.panel_input uses app.app_state✕
- Connections
- 1 pair of types, where a type in command.panel_input uses a type in app.app_state.
- The types involved
broot.command.panel_input.PanelInput→broot.app.app_state.AppState
- Direction
- command.panel_input uses app.app_state, so a change to app.app_state can break command.panel_input, while a change to command.panel_input can't break app.app_state.
- Position
- Below the diagonal: command.panel_input uses a module listed above it, which is the healthy direction.
23→3 command.panel_input uses app.mode✕
- Connections
- 1 pair of types, where a type in command.panel_input uses a type in app.mode.
- The types involved
broot.command.panel_input.PanelInput→broot.app.mode.Mode
- Direction
- command.panel_input uses app.mode, so a change to app.mode can break command.panel_input, while a change to command.panel_input can't break app.mode.
- Position
- Below the diagonal: command.panel_input uses a module listed above it, which is the healthy direction.
23→4 command.panel_input uses app.state_type✕
- Connections
- 1 pair of types, where a type in command.panel_input uses a type in app.state_type.
- The types involved
broot.command.panel_input.PanelInput→broot.app.state_type.PanelStateType
- Direction
- command.panel_input uses app.state_type, so a change to app.state_type can break command.panel_input, while a change to command.panel_input can't break app.state_type.
- Position
- Below the diagonal: command.panel_input uses a module listed above it, which is the healthy direction.
23→15 command.panel_input uses skin.panel_skin✕
- Connections
- 1 pair of types, where a type in command.panel_input uses a type in skin.panel_skin.
- The types involved
broot.command.panel_input.PanelInput→broot.skin.panel_skin.PanelSkin
- Direction
- command.panel_input uses skin.panel_skin, so a change to skin.panel_skin can break command.panel_input, while a change to command.panel_input can't break skin.panel_skin.
- Position
- Below the diagonal: command.panel_input uses a module listed above it, which is the healthy direction.
23→17 command.panel_input uses app.sel_info✕
- Connections
- 1 pair of types, where a type in command.panel_input uses a type in app.sel_info.
- The types involved
broot.command.panel_input.PanelInput→broot.app.sel_info.SelInfo
- Direction
- command.panel_input uses app.sel_info, so a change to app.sel_info can break command.panel_input, while a change to command.panel_input can't break app.sel_info.
- Position
- Below the diagonal: command.panel_input uses a module listed above it, which is the healthy direction.
23→19 command.panel_input uses verb.verb✕
- Connections
- 1 pair of types, where a type in command.panel_input uses a type in verb.verb.
- The types involved
broot.command.panel_input.PanelInput→broot.verb.verb.Verb
- Direction
- command.panel_input uses verb.verb, so a change to verb.verb can break command.panel_input, while a change to command.panel_input can't break verb.verb.
- Position
- Below the diagonal: command.panel_input uses a module listed above it, which is the healthy direction.
23→21 command.panel_input uses app.app_context✕
- Connections
- 1 pair of types, where a type in command.panel_input uses a type in app.app_context.
- The types involved
broot.command.panel_input.PanelInput→broot.app.app_context.AppContext
- Direction
- command.panel_input uses app.app_context, so a change to app.app_context can break command.panel_input, while a change to command.panel_input can't break app.app_context.
- Position
- Below the diagonal: command.panel_input uses a module listed above it, which is the healthy direction.
23→22 command.panel_input uses command.command✕
- Connections
- 1 pair of types, where a type in command.panel_input uses a type in command.command.
- The types involved
broot.command.panel_input.PanelInput→broot.command.command.Command
- Direction
- command.panel_input uses command.command, so a change to command.command can break command.panel_input, while a change to command.panel_input can't break command.command.
- Position
- Below the diagonal: command.panel_input uses a module listed above it, which is the healthy direction.
23→34 command.panel_input uses app.app_panels part of a loop✕
- Connections
- 1 pair of types, where a type in command.panel_input uses a type in app.app_panels.
- The types involved
broot.command.panel_input.PanelInput→broot.app.app_panels.AppPanels
- Direction
- command.panel_input uses app.app_panels, so a change to app.app_panels can break command.panel_input, while a change to command.panel_input can't break app.app_panels.
- Position
- Above the diagonal, so 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→15 display.screen uses skin.panel_skin✕
- Connections
- 1 pair of types, where a type in display.screen uses a type in skin.panel_skin.
- The types involved
broot.display.screen.Screen→broot.skin.panel_skin.PanelSkin
- Direction
- display.screen uses skin.panel_skin, so a change to skin.panel_skin can break display.screen, while a change to display.screen can't break skin.panel_skin.
- Position
- Below the diagonal: display.screen uses a module listed above it, which is the healthy direction.
24→21 display.screen uses app.app_context✕
- Connections
- 1 pair of types, where a type in display.screen uses a type in app.app_context.
- The types involved
broot.display.screen.Screen→broot.app.app_context.AppContext
- Direction
- display.screen uses app.app_context, so a change to app.app_context can break display.screen, while a change to display.screen can't break app.app_context.
- Position
- Below the diagonal: display.screen uses a module listed above it, which is the healthy direction.
25→3 tree.tree_line uses app.mode✕
- Connections
- 1 pair of types, where a type in tree.tree_line uses a type in app.mode.
- The types involved
broot.tree.tree_line.TreeLine→broot.app.mode.Mode
- Direction
- tree.tree_line uses app.mode, so a change to app.mode can break tree.tree_line, while a change to tree.tree_line can't break app.mode.
- Position
- Below the diagonal: tree.tree_line uses a module listed above it, which is the healthy direction.
25→12 tree.tree_line uses app.selection✕
- Connections
- 2 pairs of types, where a type in tree.tree_line uses a type in app.selection.
- The types involved
broot.tree.tree_line.TreeLine→broot.app.selection.Selectionbroot.tree.tree_line.TreeLine→broot.app.selection.SelectionType
- Direction
- tree.tree_line uses app.selection, so a change to app.selection can break tree.tree_line, while a change to tree.tree_line can't break app.selection.
- Position
- Below the diagonal: tree.tree_line uses a module listed above it, which is the healthy direction.
25→21 tree.tree_line uses app.app_context✕
- Connections
- 1 pair of types, where a type in tree.tree_line uses a type in app.app_context.
- The types involved
broot.tree.tree_line.TreeLineBuilder→broot.app.app_context.AppContext
- Direction
- tree.tree_line uses app.app_context, so a change to app.app_context can break tree.tree_line, while a change to tree.tree_line can't break app.app_context.
- Position
- Below the diagonal: tree.tree_line uses a module listed above it, which is the healthy direction.
26→1 verb.execution_builder uses app.app_state✕
- Connections
- 1 pair of types, where a type in verb.execution_builder uses a type in app.app_state.
- The types involved
broot.verb.execution_builder.ExecutionBuilder→broot.app.app_state.AppState
- Direction
- verb.execution_builder uses app.app_state, so a change to app.app_state can break verb.execution_builder, while a change to verb.execution_builder can't break app.app_state.
- Position
- Below the diagonal: verb.execution_builder uses a module listed above it, which is the healthy direction.
26→4 verb.execution_builder uses app.state_type✕
- Connections
- 1 pair of types, where a type in verb.execution_builder uses a type in app.state_type.
- The types involved
broot.verb.execution_builder.ExecutionBuilder→broot.app.state_type.PanelStateType
- Direction
- verb.execution_builder uses app.state_type, so a change to app.state_type can break verb.execution_builder, while a change to verb.execution_builder can't break app.state_type.
- Position
- Below the diagonal: verb.execution_builder uses a module listed above it, which is the healthy direction.
26→11 verb.execution_builder uses verb.verb_invocation✕
- Connections
- 1 pair of types, where a type in verb.execution_builder uses a type in verb.verb_invocation.
- The types involved
broot.verb.execution_builder.ExecutionBuilder→broot.verb.verb_invocation.VerbInvocation
- Direction
- verb.execution_builder uses verb.verb_invocation, so a change to verb.verb_invocation can break verb.execution_builder, while a change to verb.execution_builder can't break verb.verb_invocation.
- Position
- Below the diagonal: verb.execution_builder uses a module listed above it, which is the healthy direction.
26→12 verb.execution_builder uses app.selection✕
- Connections
- 1 pair of types, where a type in verb.execution_builder uses a type in app.selection.
- The types involved
broot.verb.execution_builder.ExecutionBuilder→broot.app.selection.Selection
- Direction
- verb.execution_builder uses app.selection, so a change to app.selection can break verb.execution_builder, while a change to verb.execution_builder can't break app.selection.
- Position
- Below the diagonal: verb.execution_builder uses a module listed above it, which is the healthy direction.
26→16 verb.execution_builder uses verb.invocation_parser✕
- Connections
- 1 pair of types, where a type in verb.execution_builder uses a type in verb.invocation_parser.
- The types involved
broot.verb.execution_builder.ExecutionBuilder→broot.verb.invocation_parser.InvocationParser
- Direction
- verb.execution_builder uses verb.invocation_parser, so a change to verb.invocation_parser can break verb.execution_builder, while a change to verb.execution_builder can't break verb.invocation_parser.
- Position
- Below the diagonal: verb.execution_builder uses a module listed above it, which is the healthy direction.
26→17 verb.execution_builder uses app.sel_info✕
- Connections
- 1 pair of types, where a type in verb.execution_builder uses a type in app.sel_info.
- The types involved
broot.verb.execution_builder.ExecutionBuilder→broot.app.sel_info.SelInfo
- Direction
- verb.execution_builder uses app.sel_info, so a change to app.sel_info can break verb.execution_builder, while a change to verb.execution_builder can't break app.sel_info.
- Position
- Below the diagonal: verb.execution_builder uses a module listed above it, which is the healthy direction.
26→20 verb.execution_builder uses verb.verb_store✕
- Connections
- 1 pair of types, where a type in verb.execution_builder uses a type in verb.verb_store.
- The types involved
broot.verb.execution_builder.ExecutionBuilder→broot.verb.verb_store.VerbStore
- Direction
- verb.execution_builder uses verb.verb_store, so a change to verb.verb_store can break verb.execution_builder, while a change to verb.execution_builder can't break verb.verb_store.
- Position
- Below the diagonal: verb.execution_builder uses a module listed above it, which is the healthy direction.
26→21 verb.execution_builder uses app.app_context✕
- Connections
- 1 pair of types, where a type in verb.execution_builder uses a type in app.app_context.
- The types involved
broot.verb.execution_builder.ExecutionBuilder→broot.app.app_context.AppContext
- Direction
- verb.execution_builder uses app.app_context, so a change to app.app_context can break verb.execution_builder, while a change to verb.execution_builder can't break app.app_context.
- Position
- Below the diagonal: verb.execution_builder uses a module listed above it, which is the healthy direction.
27→15 app.cmd_context uses skin.panel_skin✕
- Connections
- 1 pair of types, where a type in app.cmd_context uses a type in skin.panel_skin.
- The types involved
broot.app.cmd_context.AppCmdContext→broot.skin.panel_skin.PanelSkin
- Direction
- app.cmd_context uses skin.panel_skin, so a change to skin.panel_skin can break app.cmd_context, while a change to app.cmd_context can't break skin.panel_skin.
- Position
- Below the diagonal: app.cmd_context uses a module listed above it, which is the healthy direction.
27→21 app.cmd_context uses app.app_context✕
- Connections
- 1 pair of types, where a type in app.cmd_context uses a type in app.app_context.
- The types involved
broot.app.cmd_context.AppCmdContext→broot.app.app_context.AppContext
- Direction
- app.cmd_context uses app.app_context, so a change to app.app_context can break app.cmd_context, while a change to app.cmd_context can't break app.app_context.
- Position
- Below the diagonal: app.cmd_context uses a module listed above it, which is the healthy direction.
27→22 app.cmd_context uses command.command✕
- Connections
- 1 pair of types, where a type in app.cmd_context uses a type in command.command.
- The types involved
broot.app.cmd_context.CmdContext→broot.command.command.Command
- Direction
- app.cmd_context uses command.command, so a change to command.command can break app.cmd_context, while a change to app.cmd_context can't break command.command.
- Position
- Below the diagonal: app.cmd_context uses a module listed above it, which is the healthy direction.
27→24 app.cmd_context uses display.screen✕
- Connections
- 1 pair of types, where a type in app.cmd_context uses a type in display.screen.
- The types involved
broot.app.cmd_context.AppCmdContext→broot.display.screen.Screen
- Direction
- app.cmd_context uses display.screen, so a change to display.screen can break app.cmd_context, while a change to app.cmd_context can't break display.screen.
- Position
- Below the diagonal: app.cmd_context uses a module listed above it, which is the healthy direction.
28→1 app.display_context uses app.app_state✕
- Connections
- 1 pair of types, where a type in app.display_context uses a type in app.app_state.
- The types involved
broot.app.display_context.DisplayContext→broot.app.app_state.AppState
- Direction
- app.display_context uses app.app_state, so a change to app.app_state can break app.display_context, while a change to app.display_context can't break app.app_state.
- Position
- Below the diagonal: app.display_context uses a module listed above it, which is the healthy direction.
28→15 app.display_context uses skin.panel_skin✕
- Connections
- 1 pair of types, where a type in app.display_context uses a type in skin.panel_skin.
- The types involved
broot.app.display_context.DisplayContext→broot.skin.panel_skin.PanelSkin
- Direction
- app.display_context uses skin.panel_skin, so a change to skin.panel_skin can break app.display_context, while a change to app.display_context can't break skin.panel_skin.
- Position
- Below the diagonal: app.display_context uses a module listed above it, which is the healthy direction.
28→21 app.display_context uses app.app_context✕
- Connections
- 1 pair of types, where a type in app.display_context uses a type in app.app_context.
- The types involved
broot.app.display_context.DisplayContext→broot.app.app_context.AppContext
- Direction
- app.display_context uses app.app_context, so a change to app.app_context can break app.display_context, while a change to app.display_context can't break app.app_context.
- Position
- Below the diagonal: app.display_context uses a module listed above it, which is the healthy direction.
28→24 app.display_context uses display.screen✕
- Connections
- 1 pair of types, where a type in app.display_context uses a type in display.screen.
- The types involved
broot.app.display_context.DisplayContext→broot.display.screen.Screen
- Direction
- app.display_context uses display.screen, so a change to display.screen can break app.display_context, while a change to app.display_context can't break display.screen.
- Position
- Below the diagonal: app.display_context uses a module listed above it, which is the healthy direction.
29→9 tree.tree uses task_sync✕
- Connections
- 2 pairs of types, where a type in tree.tree uses a type in task_sync.
- The types involved
broot.tree.tree.Tree→broot.task_sync.ComputationResultbroot.tree.tree.Tree→broot.task_sync.Dam
- Direction
- tree.tree uses task_sync, so a change to task_sync can break tree.tree, while a change to tree.tree can't break task_sync.
- Position
- Below the diagonal: tree.tree uses a module listed above it, which is the healthy direction.
29→18 tree.tree uses tree.tree_options✕
- Connections
- 1 pair of types, where a type in tree.tree uses a type in tree.tree_options.
- The types involved
broot.tree.tree.Tree→broot.tree.tree_options.TreeOptions
- Direction
- tree.tree uses tree.tree_options, so a change to tree.tree_options can break tree.tree, while a change to tree.tree can't break tree.tree_options.
- Position
- Below the diagonal: tree.tree uses a module listed above it, which is the healthy direction.
29→21 tree.tree uses app.app_context✕
- Connections
- 1 pair of types, where a type in tree.tree uses a type in app.app_context.
- The types involved
broot.tree.tree.Tree→broot.app.app_context.AppContext
- Direction
- tree.tree uses app.app_context, so a change to app.app_context can break tree.tree, while a change to tree.tree can't break app.app_context.
- Position
- Below the diagonal: tree.tree uses a module listed above it, which is the healthy direction.
29→25 tree.tree uses tree.tree_line✕
- Connections
- 1 pair of types, where a type in tree.tree uses a type in tree.tree_line.
- The types involved
broot.tree.tree.Tree→broot.tree.tree_line.TreeLine
- Direction
- tree.tree uses tree.tree_line, so a change to tree.tree_line can break tree.tree, while a change to tree.tree can't break tree.tree_line.
- Position
- Below the diagonal: tree.tree uses a module listed above it, which is the healthy direction.
30→1 app.panel uses app.app_state✕
- Connections
- 1 pair of types, where a type in app.panel uses a type in app.app_state.
- The types involved
broot.app.panel.Panel→broot.app.app_state.AppState
- Direction
- app.panel uses app.app_state, so a change to app.app_state can break app.panel, while a change to app.panel can't break app.app_state.
- Position
- Below the diagonal: app.panel uses a module listed above it, which is the healthy direction.
30→9 app.panel uses task_sync✕
- Connections
- 1 pair of types, where a type in app.panel uses a type in task_sync.
- The types involved
broot.app.panel.Panel→broot.task_sync.Dam
- Direction
- app.panel uses task_sync, so a change to task_sync can break app.panel, while a change to app.panel can't break task_sync.
- Position
- Below the diagonal: app.panel uses a module listed above it, which is the healthy direction.
30→15 app.panel uses skin.panel_skin✕
- Connections
- 1 pair of types, where a type in app.panel uses a type in skin.panel_skin.
- The types involved
broot.app.panel.Panel→broot.skin.panel_skin.PanelSkin
- Direction
- app.panel uses skin.panel_skin, so a change to skin.panel_skin can break app.panel, while a change to app.panel can't break skin.panel_skin.
- Position
- Below the diagonal: app.panel uses a module listed above it, which is the healthy direction.
30→21 app.panel uses app.app_context✕
- Connections
- 1 pair of types, where a type in app.panel uses a type in app.app_context.
- The types involved
broot.app.panel.Panel→broot.app.app_context.AppContext
- Direction
- app.panel uses app.app_context, so a change to app.app_context can break app.panel, while a change to app.panel can't break app.app_context.
- Position
- Below the diagonal: app.panel uses a module listed above it, which is the healthy direction.
30→22 app.panel uses command.command✕
- Connections
- 1 pair of types, where a type in app.panel uses a type in command.command.
- The types involved
broot.app.panel.Panel→broot.command.command.Command
- Direction
- app.panel uses command.command, so a change to command.command can break app.panel, while a change to app.panel can't break command.command.
- Position
- Below the diagonal: app.panel uses a module listed above it, which is the healthy direction.
30→24 app.panel uses display.screen✕
- Connections
- 1 pair of types, where a type in app.panel uses a type in display.screen.
- The types involved
broot.app.panel.Panel→broot.display.screen.Screen
- Direction
- app.panel uses display.screen, so a change to display.screen can break app.panel, while a change to app.panel can't break display.screen.
- Position
- Below the diagonal: app.panel uses a module listed above it, which is the healthy direction.
30→27 app.panel uses app.cmd_context✕
- Connections
- 1 pair of types, where a type in app.panel uses a type in app.cmd_context.
- The types involved
broot.app.panel.Panel→broot.app.cmd_context.AppCmdContext
- Direction
- app.panel uses app.cmd_context, so a change to app.cmd_context can break app.panel, while a change to app.panel can't break app.cmd_context.
- Position
- Below the diagonal: app.panel uses a module listed above it, which is the healthy direction.
31→1 app.panel_state uses app.app_state✕
- Connections
- 1 pair of types, where a type in app.panel_state uses a type in app.app_state.
- The types involved
broot.app.panel_state.PanelState→broot.app.app_state.AppState
- Direction
- app.panel_state uses app.app_state, so a change to app.app_state can break app.panel_state, while a change to app.panel_state can't break app.app_state.
- Position
- Below the diagonal: app.panel_state uses a module listed above it, which is the healthy direction.
31→2 app.panel_state uses app.cmd_result✕
- Connections
- 1 pair of types, where a type in app.panel_state uses a type in app.cmd_result.
- The types involved
broot.app.panel_state.PanelState→broot.app.cmd_result.CmdResult
- Direction
- app.panel_state uses app.cmd_result, so a change to app.cmd_result can break app.panel_state, while a change to app.panel_state can't break app.cmd_result.
- Position
- Below the diagonal: app.panel_state uses a module listed above it, which is the healthy direction.
31→3 app.panel_state uses app.mode✕
- Connections
- 1 pair of types, where a type in app.panel_state uses a type in app.mode.
- The types involved
broot.app.panel_state.PanelState→broot.app.mode.Mode
- Direction
- app.panel_state uses app.mode, so a change to app.mode can break app.panel_state, while a change to app.panel_state can't break app.mode.
- Position
- Below the diagonal: app.panel_state uses a module listed above it, which is the healthy direction.
31→4 app.panel_state uses app.state_type✕
- Connections
- 1 pair of types, where a type in app.panel_state uses a type in app.state_type.
- The types involved
broot.app.panel_state.PanelState→broot.app.state_type.PanelStateType
- Direction
- app.panel_state uses app.state_type, so a change to app.state_type can break app.panel_state, while a change to app.panel_state can't break app.state_type.
- Position
- Below the diagonal: app.panel_state uses a module listed above it, which is the healthy direction.
31→6 app.panel_state uses command.trigger_type✕
- Connections
- 1 pair of types, where a type in app.panel_state uses a type in command.trigger_type.
- The types involved
broot.app.panel_state.PanelState→broot.command.trigger_type.TriggerType
- Direction
- app.panel_state uses command.trigger_type, so a change to command.trigger_type can break app.panel_state, while a change to app.panel_state can't break command.trigger_type.
- Position
- Below the diagonal: app.panel_state uses a module listed above it, which is the healthy direction.
31→9 app.panel_state uses task_sync✕
- Connections
- 1 pair of types, where a type in app.panel_state uses a type in task_sync.
- The types involved
broot.app.panel_state.PanelState→broot.task_sync.Dam
- Direction
- app.panel_state uses task_sync, so a change to task_sync can break app.panel_state, while a change to app.panel_state can't break task_sync.
- Position
- Below the diagonal: app.panel_state uses a module listed above it, which is the healthy direction.
31→10 app.panel_state uses verb.internal_execution✕
- Connections
- 2 pairs of types, where a type in app.panel_state uses a type in verb.internal_execution.
- The types involved
broot.app.panel_state.PanelState→broot.verb.internal_execution.InternalExecutionbroot.app.panel_state.panel_state$module→broot.verb.internal_execution.InternalExecution
- Direction
- app.panel_state uses verb.internal_execution, so a change to verb.internal_execution can break app.panel_state, while a change to app.panel_state can't break verb.internal_execution.
- Position
- Below the diagonal: app.panel_state uses a module listed above it, which is the healthy direction.
31→11 app.panel_state uses verb.verb_invocation✕
- Connections
- 2 pairs of types, where a type in app.panel_state uses a type in verb.verb_invocation.
- The types involved
broot.app.panel_state.PanelState→broot.verb.verb_invocation.VerbInvocationbroot.app.panel_state.panel_state$module→broot.verb.verb_invocation.VerbInvocation
- Direction
- app.panel_state uses verb.verb_invocation, so a change to verb.verb_invocation can break app.panel_state, while a change to app.panel_state can't break verb.verb_invocation.
- Position
- Below the diagonal: app.panel_state uses a module listed above it, which is the healthy direction.
31→12 app.panel_state uses app.selection✕
- Connections
- 1 pair of types, where a type in app.panel_state uses a type in app.selection.
- The types involved
broot.app.panel_state.PanelState→broot.app.selection.Selection
- Direction
- app.panel_state uses app.selection, so a change to app.selection can break app.panel_state, while a change to app.panel_state can't break app.selection.
- Position
- Below the diagonal: app.panel_state uses a module listed above it, which is the healthy direction.
31→14 app.panel_state uses pattern.input_pattern✕
- Connections
- 1 pair of types, where a type in app.panel_state uses a type in pattern.input_pattern.
- The types involved
broot.app.panel_state.PanelState→broot.pattern.input_pattern.InputPattern
- Direction
- app.panel_state uses pattern.input_pattern, so a change to pattern.input_pattern can break app.panel_state, while a change to app.panel_state can't break pattern.input_pattern.
- Position
- Below the diagonal: app.panel_state uses a module listed above it, which is the healthy direction.
31→16 app.panel_state uses verb.invocation_parser✕
- Connections
- 1 pair of types, where a type in app.panel_state uses a type in verb.invocation_parser.
- The types involved
broot.app.panel_state.PanelState→broot.verb.invocation_parser.InvocationParser
- Direction
- app.panel_state uses verb.invocation_parser, so a change to verb.invocation_parser can break app.panel_state, while a change to app.panel_state can't break verb.invocation_parser.
- Position
- Below the diagonal: app.panel_state uses a module listed above it, which is the healthy direction.
31→17 app.panel_state uses app.sel_info✕
- Connections
- 1 pair of types, where a type in app.panel_state uses a type in app.sel_info.
- The types involved
broot.app.panel_state.PanelState→broot.app.sel_info.SelInfo
- Direction
- app.panel_state uses app.sel_info, so a change to app.sel_info can break app.panel_state, while a change to app.panel_state can't break app.sel_info.
- Position
- Below the diagonal: app.panel_state uses a module listed above it, which is the healthy direction.
31→18 app.panel_state uses tree.tree_options✕
- Connections
- 1 pair of types, where a type in app.panel_state uses a type in tree.tree_options.
- The types involved
broot.app.panel_state.PanelState→broot.tree.tree_options.TreeOptions
- Direction
- app.panel_state uses tree.tree_options, so a change to tree.tree_options can break app.panel_state, while a change to app.panel_state can't break tree.tree_options.
- Position
- Below the diagonal: app.panel_state uses a module listed above it, which is the healthy direction.
31→19 app.panel_state uses verb.verb✕
- Connections
- 1 pair of types, where a type in app.panel_state uses a type in verb.verb.
- The types involved
broot.app.panel_state.PanelState→broot.verb.verb.Verb
- Direction
- app.panel_state uses verb.verb, so a change to verb.verb can break app.panel_state, while a change to app.panel_state can't break verb.verb.
- Position
- Below the diagonal: app.panel_state uses a module listed above it, which is the healthy direction.
31→21 app.panel_state uses app.app_context✕
- Connections
- 1 pair of types, where a type in app.panel_state uses a type in app.app_context.
- The types involved
broot.app.panel_state.PanelState→broot.app.app_context.AppContext
- Direction
- app.panel_state uses app.app_context, so a change to app.app_context can break app.panel_state, while a change to app.panel_state can't break app.app_context.
- Position
- Below the diagonal: app.panel_state uses a module listed above it, which is the healthy direction.
31→22 app.panel_state uses command.command✕
- Connections
- 1 pair of types, where a type in app.panel_state uses a type in command.command.
- The types involved
broot.app.panel_state.PanelState→broot.command.command.Command
- Direction
- app.panel_state uses command.command, so a change to command.command can break app.panel_state, while a change to app.panel_state can't break command.command.
- Position
- Below the diagonal: app.panel_state uses a module listed above it, which is the healthy direction.
31→24 app.panel_state uses display.screen✕
- Connections
- 1 pair of types, where a type in app.panel_state uses a type in display.screen.
- The types involved
broot.app.panel_state.PanelState→broot.display.screen.Screen
- Direction
- app.panel_state uses display.screen, so a change to display.screen can break app.panel_state, while a change to app.panel_state can't break display.screen.
- Position
- Below the diagonal: app.panel_state uses a module listed above it, which is the healthy direction.
31→27 app.panel_state uses app.cmd_context✕
- Connections
- 1 pair of types, where a type in app.panel_state uses a type in app.cmd_context.
- The types involved
broot.app.panel_state.PanelState→broot.app.cmd_context.CmdContext
- Direction
- app.panel_state uses app.cmd_context, so a change to app.cmd_context can break app.panel_state, while a change to app.panel_state can't break app.cmd_context.
- Position
- Below the diagonal: app.panel_state uses a module listed above it, which is the healthy direction.
31→28 app.panel_state uses app.display_context✕
- Connections
- 1 pair of types, where a type in app.panel_state uses a type in app.display_context.
- The types involved
broot.app.panel_state.PanelState→broot.app.display_context.DisplayContext
- Direction
- app.panel_state uses app.display_context, so a change to app.display_context can break app.panel_state, while a change to app.panel_state can't break app.display_context.
- Position
- Below the diagonal: app.panel_state uses a module listed above it, which is the healthy direction.
32→5 preview.preview uses command.scroll✕
- Connections
- 1 pair of types, where a type in preview.preview uses a type in command.scroll.
- The types involved
broot.preview.preview.Preview→broot.command.scroll.ScrollCommand
- Direction
- preview.preview uses command.scroll, so a change to command.scroll can break preview.preview, while a change to preview.preview can't break command.scroll.
- Position
- Below the diagonal: preview.preview uses a module listed above it, which is the healthy direction.
32→9 preview.preview uses task_sync✕
- Connections
- 1 pair of types, where a type in preview.preview uses a type in task_sync.
- The types involved
broot.preview.preview.Preview→broot.task_sync.Dam
- Direction
- preview.preview uses task_sync, so a change to task_sync can break preview.preview, while a change to preview.preview can't break task_sync.
- Position
- Below the diagonal: preview.preview uses a module listed above it, which is the healthy direction.
32→14 preview.preview uses pattern.input_pattern✕
- Connections
- 1 pair of types, where a type in preview.preview uses a type in pattern.input_pattern.
- The types involved
broot.preview.preview.Preview→broot.pattern.input_pattern.InputPattern
- Direction
- preview.preview uses pattern.input_pattern, so a change to pattern.input_pattern can break preview.preview, while a change to preview.preview can't break pattern.input_pattern.
- Position
- Below the diagonal: preview.preview uses a module listed above it, which is the healthy direction.
32→15 preview.preview uses skin.panel_skin✕
- Connections
- 1 pair of types, where a type in preview.preview uses a type in skin.panel_skin.
- The types involved
broot.preview.preview.Preview→broot.skin.panel_skin.PanelSkin
- Direction
- preview.preview uses skin.panel_skin, so a change to skin.panel_skin can break preview.preview, while a change to preview.preview can't break skin.panel_skin.
- Position
- Below the diagonal: preview.preview uses a module listed above it, which is the healthy direction.
32→21 preview.preview uses app.app_context✕
- Connections
- 1 pair of types, where a type in preview.preview uses a type in app.app_context.
- The types involved
broot.preview.preview.Preview→broot.app.app_context.AppContext
- Direction
- preview.preview uses app.app_context, so a change to app.app_context can break preview.preview, while a change to preview.preview can't break app.app_context.
- Position
- Below the diagonal: preview.preview uses a module listed above it, which is the healthy direction.
32→24 preview.preview uses display.screen✕
- Connections
- 1 pair of types, where a type in preview.preview uses a type in display.screen.
- The types involved
broot.preview.preview.Preview→broot.display.screen.Screen
- Direction
- preview.preview uses display.screen, so a change to display.screen can break preview.preview, while a change to preview.preview can't break display.screen.
- Position
- Below the diagonal: preview.preview uses a module listed above it, which is the healthy direction.
32→28 preview.preview uses app.display_context✕
- Connections
- 1 pair of types, where a type in preview.preview uses a type in app.display_context.
- The types involved
broot.preview.preview.Preview→broot.app.display_context.DisplayContext
- Direction
- preview.preview uses app.display_context, so a change to app.display_context can break preview.preview, while a change to preview.preview can't break app.display_context.
- Position
- Below the diagonal: preview.preview uses a module listed above it, which is the healthy direction.
33→1 verb.internal_focus uses app.app_state✕
- Connections
- 1 pair of types, where a type in verb.internal_focus uses a type in app.app_state.
- The types involved
broot.verb.internal_focus.internal_focus$module→broot.app.app_state.AppState
- Direction
- verb.internal_focus uses app.app_state, so a change to app.app_state can break verb.internal_focus, while a change to verb.internal_focus can't break app.app_state.
- Position
- Below the diagonal: verb.internal_focus uses a module listed above it, which is the healthy direction.
33→2 verb.internal_focus uses app.cmd_result✕
- Connections
- 2 pairs of types, where a type in verb.internal_focus uses a type in app.cmd_result.
- The types involved
broot.verb.internal_focus.internal_focus$module→broot.app.cmd_result.CmdResultbroot.verb.internal_focus.internal_focus$module→broot.app.cmd_result.HDir
- Direction
- verb.internal_focus uses app.cmd_result, so a change to app.cmd_result can break verb.internal_focus, while a change to verb.internal_focus can't break app.cmd_result.
- Position
- Below the diagonal: verb.internal_focus uses a module listed above it, which is the healthy direction.
33→6 verb.internal_focus uses command.trigger_type✕
- Connections
- 1 pair of types, where a type in verb.internal_focus uses a type in command.trigger_type.
- The types involved
broot.verb.internal_focus.internal_focus$module→broot.command.trigger_type.TriggerType
- Direction
- verb.internal_focus uses command.trigger_type, so a change to command.trigger_type can break verb.internal_focus, while a change to verb.internal_focus can't break command.trigger_type.
- Position
- Below the diagonal: verb.internal_focus uses a module listed above it, which is the healthy direction.
33→10 verb.internal_focus uses verb.internal_execution✕
- Connections
- 1 pair of types, where a type in verb.internal_focus uses a type in verb.internal_execution.
- The types involved
broot.verb.internal_focus.internal_focus$module→broot.verb.internal_execution.InternalExecution
- Direction
- verb.internal_focus uses verb.internal_execution, so a change to verb.internal_execution can break verb.internal_focus, while a change to verb.internal_focus can't break verb.internal_execution.
- Position
- Below the diagonal: verb.internal_focus uses a module listed above it, which is the healthy direction.
33→11 verb.internal_focus uses verb.verb_invocation✕
- Connections
- 1 pair of types, where a type in verb.internal_focus uses a type in verb.verb_invocation.
- The types involved
broot.verb.internal_focus.internal_focus$module→broot.verb.verb_invocation.VerbInvocation
- Direction
- verb.internal_focus uses verb.verb_invocation, so a change to verb.verb_invocation can break verb.internal_focus, while a change to verb.internal_focus can't break verb.verb_invocation.
- Position
- Below the diagonal: verb.internal_focus uses a module listed above it, which is the healthy direction.
33→16 verb.internal_focus uses verb.invocation_parser✕
- Connections
- 1 pair of types, where a type in verb.internal_focus uses a type in verb.invocation_parser.
- The types involved
broot.verb.internal_focus.internal_focus$module→broot.verb.invocation_parser.InvocationParser
- Direction
- verb.internal_focus uses verb.invocation_parser, so a change to verb.invocation_parser can break verb.internal_focus, while a change to verb.internal_focus can't break verb.invocation_parser.
- Position
- Below the diagonal: verb.internal_focus uses a module listed above it, which is the healthy direction.
33→17 verb.internal_focus uses app.sel_info✕
- Connections
- 1 pair of types, where a type in verb.internal_focus uses a type in app.sel_info.
- The types involved
broot.verb.internal_focus.internal_focus$module→broot.app.sel_info.SelInfo
- Direction
- verb.internal_focus uses app.sel_info, so a change to app.sel_info can break verb.internal_focus, while a change to verb.internal_focus can't break app.sel_info.
- Position
- Below the diagonal: verb.internal_focus uses a module listed above it, which is the healthy direction.
33→18 verb.internal_focus uses tree.tree_options✕
- Connections
- 1 pair of types, where a type in verb.internal_focus uses a type in tree.tree_options.
- The types involved
broot.verb.internal_focus.internal_focus$module→broot.tree.tree_options.TreeOptions
- Direction
- verb.internal_focus uses tree.tree_options, so a change to tree.tree_options can break verb.internal_focus, while a change to verb.internal_focus can't break tree.tree_options.
- Position
- Below the diagonal: verb.internal_focus uses a module listed above it, which is the healthy direction.
33→19 verb.internal_focus uses verb.verb✕
- Connections
- 1 pair of types, where a type in verb.internal_focus uses a type in verb.verb.
- The types involved
broot.verb.internal_focus.internal_focus$module→broot.verb.verb.Verb
- Direction
- verb.internal_focus uses verb.verb, so a change to verb.verb can break verb.internal_focus, while a change to verb.internal_focus can't break verb.verb.
- Position
- Below the diagonal: verb.internal_focus uses a module listed above it, which is the healthy direction.
33→21 verb.internal_focus uses app.app_context✕
- Connections
- 1 pair of types, where a type in verb.internal_focus uses a type in app.app_context.
- The types involved
broot.verb.internal_focus.internal_focus$module→broot.app.app_context.AppContext
- Direction
- verb.internal_focus uses app.app_context, so a change to app.app_context can break verb.internal_focus, while a change to verb.internal_focus can't break app.app_context.
- Position
- Below the diagonal: verb.internal_focus uses a module listed above it, which is the healthy direction.
33→24 verb.internal_focus uses display.screen✕
- Connections
- 1 pair of types, where a type in verb.internal_focus uses a type in display.screen.
- The types involved
broot.verb.internal_focus.internal_focus$module→broot.display.screen.Screen
- Direction
- verb.internal_focus uses display.screen, so a change to display.screen can break verb.internal_focus, while a change to verb.internal_focus can't break display.screen.
- Position
- Below the diagonal: verb.internal_focus uses a module listed above it, which is the healthy direction.
33→27 verb.internal_focus uses app.cmd_context✕
- Connections
- 1 pair of types, where a type in verb.internal_focus uses a type in app.cmd_context.
- The types involved
broot.verb.internal_focus.internal_focus$module→broot.app.cmd_context.CmdContext
- Direction
- verb.internal_focus uses app.cmd_context, so a change to app.cmd_context can break verb.internal_focus, while a change to verb.internal_focus can't break app.cmd_context.
- Position
- Below the diagonal: verb.internal_focus uses a module listed above it, which is the healthy direction.
34→1 app.app_panels uses app.app_state✕
- Connections
- 1 pair of types, where a type in app.app_panels uses a type in app.app_state.
- The types involved
broot.app.app_panels.AppPanelsAndInputs→broot.app.app_state.AppState
- Direction
- app.app_panels uses app.app_state, so a change to app.app_state can break app.app_panels, while a change to app.app_panels can't break app.app_state.
- Position
- Below the diagonal: app.app_panels uses a module listed above it, which is the healthy direction.
34→2 app.app_panels uses app.cmd_result✕
- Connections
- 1 pair of types, where a type in app.app_panels uses a type in app.cmd_result.
- The types involved
broot.app.app_panels.AppPanelsAndInputs→broot.app.cmd_result.HDir
- Direction
- app.app_panels uses app.cmd_result, so a change to app.cmd_result can break app.app_panels, while a change to app.app_panels can't break app.cmd_result.
- Position
- Below the diagonal: app.app_panels uses a module listed above it, which is the healthy direction.
34→3 app.app_panels uses app.mode✕
- Connections
- 1 pair of types, where a type in app.app_panels uses a type in app.mode.
- The types involved
broot.app.app_panels.AppPanelsAndInputs→broot.app.mode.Mode
- Direction
- app.app_panels uses app.mode, so a change to app.mode can break app.app_panels, while a change to app.app_panels can't break app.mode.
- Position
- Below the diagonal: app.app_panels uses a module listed above it, which is the healthy direction.
34→4 app.app_panels uses app.state_type✕
- Connections
- 2 pairs of types, where a type in app.app_panels uses a type in app.state_type.
- The types involved
broot.app.app_panels.AppPanels→broot.app.state_type.PanelStateTypebroot.app.app_panels.AppPanelsAndInputs→broot.app.state_type.PanelStateType
- Direction
- app.app_panels uses app.state_type, so a change to app.state_type can break app.app_panels, while a change to app.app_panels can't break app.state_type.
- Position
- Below the diagonal: app.app_panels uses a module listed above it, which is the healthy direction.
34→9 app.app_panels uses task_sync✕
- Connections
- 1 pair of types, where a type in app.app_panels uses a type in task_sync.
- The types involved
broot.app.app_panels.AppPanelsAndInputs→broot.task_sync.Dam
- Direction
- app.app_panels uses task_sync, so a change to task_sync can break app.app_panels, while a change to app.app_panels can't break task_sync.
- Position
- Below the diagonal: app.app_panels uses a module listed above it, which is the healthy direction.
34→15 app.app_panels uses skin.panel_skin✕
- Connections
- 1 pair of types, where a type in app.app_panels uses a type in skin.panel_skin.
- The types involved
broot.app.app_panels.AppPanelsAndInputs→broot.skin.panel_skin.PanelSkin
- Direction
- app.app_panels uses skin.panel_skin, so a change to skin.panel_skin can break app.app_panels, while a change to app.app_panels can't break skin.panel_skin.
- Position
- Below the diagonal: app.app_panels uses a module listed above it, which is the healthy direction.
34→21 app.app_panels uses app.app_context✕
- Connections
- 1 pair of types, where a type in app.app_panels uses a type in app.app_context.
- The types involved
broot.app.app_panels.AppPanelsAndInputs→broot.app.app_context.AppContext
- Direction
- app.app_panels uses app.app_context, so a change to app.app_context can break app.app_panels, while a change to app.app_panels can't break app.app_context.
- Position
- Below the diagonal: app.app_panels uses a module listed above it, which is the healthy direction.
34→22 app.app_panels uses command.command✕
- Connections
- 1 pair of types, where a type in app.app_panels uses a type in command.command.
- The types involved
broot.app.app_panels.AppPanelsAndInputs→broot.command.command.Command
- Direction
- app.app_panels uses command.command, so a change to command.command can break app.app_panels, while a change to app.app_panels can't break command.command.
- Position
- Below the diagonal: app.app_panels uses a module listed above it, which is the healthy direction.
34→23 app.app_panels uses command.panel_input✕
- Connections
- 1 pair of types, where a type in app.app_panels uses a type in command.panel_input.
- The types involved
broot.app.app_panels.AppPanelsAndInputs→broot.command.panel_input.PanelInput
- Direction
- app.app_panels uses command.panel_input, so a change to command.panel_input can break app.app_panels, while a change to app.app_panels can't break command.panel_input.
- Position
- Below the diagonal: app.app_panels uses a module listed above it, which is the healthy direction.
34→24 app.app_panels uses display.screen✕
- Connections
- 2 pairs of types, where a type in app.app_panels uses a type in display.screen.
- The types involved
broot.app.app_panels.AppPanels→broot.display.screen.Screenbroot.app.app_panels.AppPanelsAndInputs→broot.display.screen.Screen
- Direction
- app.app_panels uses display.screen, so a change to display.screen can break app.app_panels, while a change to app.app_panels can't break display.screen.
- Position
- Below the diagonal: app.app_panels uses a module listed above it, which is the healthy direction.
34→27 app.app_panels uses app.cmd_context✕
- Connections
- 1 pair of types, where a type in app.app_panels uses a type in app.cmd_context.
- The types involved
broot.app.app_panels.AppPanelsAndInputs→broot.app.cmd_context.AppCmdContext
- Direction
- app.app_panels uses app.cmd_context, so a change to app.cmd_context can break app.app_panels, while a change to app.app_panels can't break app.cmd_context.
- Position
- Below the diagonal: app.app_panels uses a module listed above it, which is the healthy direction.
34→30 app.app_panels uses app.panel✕
- Connections
- 2 pairs of types, where a type in app.app_panels uses a type in app.panel.
- The types involved
broot.app.app_panels.AppPanels→broot.app.panel.Panelbroot.app.app_panels.AppPanelsAndInputs→broot.app.panel.Panel
- Direction
- app.app_panels uses app.panel, so a change to app.panel can break app.app_panels, while a change to app.app_panels can't break app.panel.
- Position
- Below the diagonal: app.app_panels uses a module listed above it, which is the healthy direction.
35→1 browser.browser_state uses app.app_state✕
- Connections
- 1 pair of types, where a type in browser.browser_state uses a type in app.app_state.
- The types involved
broot.browser.browser_state.BrowserState→broot.app.app_state.AppState
- Direction
- browser.browser_state uses app.app_state, so a change to app.app_state can break browser.browser_state, while a change to browser.browser_state can't break app.app_state.
- Position
- Below the diagonal: browser.browser_state uses a module listed above it, which is the healthy direction.
35→2 browser.browser_state uses app.cmd_result✕
- Connections
- 1 pair of types, where a type in browser.browser_state uses a type in app.cmd_result.
- The types involved
broot.browser.browser_state.BrowserState→broot.app.cmd_result.CmdResult
- Direction
- browser.browser_state uses app.cmd_result, so a change to app.cmd_result can break browser.browser_state, while a change to browser.browser_state can't break app.cmd_result.
- Position
- Below the diagonal: browser.browser_state uses a module listed above it, which is the healthy direction.
35→3 browser.browser_state uses app.mode✕
- Connections
- 1 pair of types, where a type in browser.browser_state uses a type in app.mode.
- The types involved
broot.browser.browser_state.BrowserState→broot.app.mode.Mode
- Direction
- browser.browser_state uses app.mode, so a change to app.mode can break browser.browser_state, while a change to browser.browser_state can't break app.mode.
- Position
- Below the diagonal: browser.browser_state uses a module listed above it, which is the healthy direction.
35→4 browser.browser_state uses app.state_type✕
- Connections
- 1 pair of types, where a type in browser.browser_state uses a type in app.state_type.
- The types involved
broot.browser.browser_state.BrowserState→broot.app.state_type.PanelStateType
- Direction
- browser.browser_state uses app.state_type, so a change to app.state_type can break browser.browser_state, while a change to browser.browser_state can't break app.state_type.
- Position
- Below the diagonal: browser.browser_state uses a module listed above it, which is the healthy direction.
35→6 browser.browser_state uses command.trigger_type✕
- Connections
- 1 pair of types, where a type in browser.browser_state uses a type in command.trigger_type.
- The types involved
broot.browser.browser_state.BrowserState→broot.command.trigger_type.TriggerType
- Direction
- browser.browser_state uses command.trigger_type, so a change to command.trigger_type can break browser.browser_state, while a change to browser.browser_state can't break command.trigger_type.
- Position
- Below the diagonal: browser.browser_state uses a module listed above it, which is the healthy direction.
35→9 browser.browser_state uses task_sync✕
- Connections
- 1 pair of types, where a type in browser.browser_state uses a type in task_sync.
- The types involved
broot.browser.browser_state.BrowserState→broot.task_sync.Dam
- Direction
- browser.browser_state uses task_sync, so a change to task_sync can break browser.browser_state, while a change to browser.browser_state can't break task_sync.
- Position
- Below the diagonal: browser.browser_state uses a module listed above it, which is the healthy direction.
35→10 browser.browser_state uses verb.internal_execution✕
- Connections
- 1 pair of types, where a type in browser.browser_state uses a type in verb.internal_execution.
- The types involved
broot.browser.browser_state.BrowserState→broot.verb.internal_execution.InternalExecution
- Direction
- browser.browser_state uses verb.internal_execution, so a change to verb.internal_execution can break browser.browser_state, while a change to browser.browser_state can't break verb.internal_execution.
- Position
- Below the diagonal: browser.browser_state uses a module listed above it, which is the healthy direction.
35→11 browser.browser_state uses verb.verb_invocation✕
- Connections
- 1 pair of types, where a type in browser.browser_state uses a type in verb.verb_invocation.
- The types involved
broot.browser.browser_state.BrowserState→broot.verb.verb_invocation.VerbInvocation
- Direction
- browser.browser_state uses verb.verb_invocation, so a change to verb.verb_invocation can break browser.browser_state, while a change to browser.browser_state can't break verb.verb_invocation.
- Position
- Below the diagonal: browser.browser_state uses a module listed above it, which is the healthy direction.
35→12 browser.browser_state uses app.selection✕
- Connections
- 1 pair of types, where a type in browser.browser_state uses a type in app.selection.
- The types involved
broot.browser.browser_state.BrowserState→broot.app.selection.Selection
- Direction
- browser.browser_state uses app.selection, so a change to app.selection can break browser.browser_state, while a change to browser.browser_state can't break app.selection.
- Position
- Below the diagonal: browser.browser_state uses a module listed above it, which is the healthy direction.
35→14 browser.browser_state uses pattern.input_pattern✕
- Connections
- 1 pair of types, where a type in browser.browser_state uses a type in pattern.input_pattern.
- The types involved
broot.browser.browser_state.BrowserState→broot.pattern.input_pattern.InputPattern
- Direction
- browser.browser_state uses pattern.input_pattern, so a change to pattern.input_pattern can break browser.browser_state, while a change to browser.browser_state can't break pattern.input_pattern.
- Position
- Below the diagonal: browser.browser_state uses a module listed above it, which is the healthy direction.
35→16 browser.browser_state uses verb.invocation_parser✕
- Connections
- 1 pair of types, where a type in browser.browser_state uses a type in verb.invocation_parser.
- The types involved
broot.browser.browser_state.BrowserState→broot.verb.invocation_parser.InvocationParser
- Direction
- browser.browser_state uses verb.invocation_parser, so a change to verb.invocation_parser can break browser.browser_state, while a change to browser.browser_state can't break verb.invocation_parser.
- Position
- Below the diagonal: browser.browser_state uses a module listed above it, which is the healthy direction.
35→18 browser.browser_state uses tree.tree_options✕
- Connections
- 1 pair of types, where a type in browser.browser_state uses a type in tree.tree_options.
- The types involved
broot.browser.browser_state.BrowserState→broot.tree.tree_options.TreeOptions
- Direction
- browser.browser_state uses tree.tree_options, so a change to tree.tree_options can break browser.browser_state, while a change to browser.browser_state can't break tree.tree_options.
- Position
- Below the diagonal: browser.browser_state uses a module listed above it, which is the healthy direction.
35→21 browser.browser_state uses app.app_context✕
- Connections
- 1 pair of types, where a type in browser.browser_state uses a type in app.app_context.
- The types involved
broot.browser.browser_state.BrowserState→broot.app.app_context.AppContext
- Direction
- browser.browser_state uses app.app_context, so a change to app.app_context can break browser.browser_state, while a change to browser.browser_state can't break app.app_context.
- Position
- Below the diagonal: browser.browser_state uses a module listed above it, which is the healthy direction.
35→22 browser.browser_state uses command.command✕
- Connections
- 1 pair of types, where a type in browser.browser_state uses a type in command.command.
- The types involved
broot.browser.browser_state.BrowserState→broot.command.command.Command
- Direction
- browser.browser_state uses command.command, so a change to command.command can break browser.browser_state, while a change to browser.browser_state can't break command.command.
- Position
- Below the diagonal: browser.browser_state uses a module listed above it, which is the healthy direction.
35→24 browser.browser_state uses display.screen✕
- Connections
- 1 pair of types, where a type in browser.browser_state uses a type in display.screen.
- The types involved
broot.browser.browser_state.BrowserState→broot.display.screen.Screen
- Direction
- browser.browser_state uses display.screen, so a change to display.screen can break browser.browser_state, while a change to browser.browser_state can't break display.screen.
- Position
- Below the diagonal: browser.browser_state uses a module listed above it, which is the healthy direction.
35→27 browser.browser_state uses app.cmd_context✕
- Connections
- 1 pair of types, where a type in browser.browser_state uses a type in app.cmd_context.
- The types involved
broot.browser.browser_state.BrowserState→broot.app.cmd_context.CmdContext
- Direction
- browser.browser_state uses app.cmd_context, so a change to app.cmd_context can break browser.browser_state, while a change to browser.browser_state can't break app.cmd_context.
- Position
- Below the diagonal: browser.browser_state uses a module listed above it, which is the healthy direction.
35→28 browser.browser_state uses app.display_context✕
- Connections
- 1 pair of types, where a type in browser.browser_state uses a type in app.display_context.
- The types involved
broot.browser.browser_state.BrowserState→broot.app.display_context.DisplayContext
- Direction
- browser.browser_state uses app.display_context, so a change to app.display_context can break browser.browser_state, while a change to browser.browser_state can't break app.display_context.
- Position
- Below the diagonal: browser.browser_state uses a module listed above it, which is the healthy direction.
35→29 browser.browser_state uses tree.tree✕
- Connections
- 1 pair of types, where a type in browser.browser_state uses a type in tree.tree.
- The types involved
broot.browser.browser_state.BrowserState→broot.tree.tree.Tree
- Direction
- browser.browser_state uses tree.tree, so a change to tree.tree can break browser.browser_state, while a change to browser.browser_state can't break tree.tree.
- Position
- Below the diagonal: browser.browser_state uses a module listed above it, which is the healthy direction.
35→31 browser.browser_state uses app.panel_state✕
- Connections
- 1 pair of types, where a type in browser.browser_state uses a type in app.panel_state.
- The types involved
broot.browser.browser_state.BrowserState→broot.app.panel_state.PanelState
- Direction
- browser.browser_state uses app.panel_state, so a change to app.panel_state can break browser.browser_state, while a change to browser.browser_state can't break app.panel_state.
- Position
- Below the diagonal: browser.browser_state uses a module listed above it, which is the healthy direction.
36→1 filesystems.filesystems_state uses app.app_state✕
- Connections
- 1 pair of types, where a type in filesystems.filesystems_state uses a type in app.app_state.
- The types involved
broot.filesystems.filesystems_state.FilesystemState→broot.app.app_state.AppState
- Direction
- filesystems.filesystems_state uses app.app_state, so a change to app.app_state can break filesystems.filesystems_state, while a change to filesystems.filesystems_state can't break app.app_state.
- Position
- Below the diagonal: filesystems.filesystems_state uses a module listed above it, which is the healthy direction.
36→2 filesystems.filesystems_state uses app.cmd_result✕
- Connections
- 1 pair of types, where a type in filesystems.filesystems_state uses a type in app.cmd_result.
- The types involved
broot.filesystems.filesystems_state.FilesystemState→broot.app.cmd_result.CmdResult
- Direction
- filesystems.filesystems_state uses app.cmd_result, so a change to app.cmd_result can break filesystems.filesystems_state, while a change to filesystems.filesystems_state can't break app.cmd_result.
- Position
- Below the diagonal: filesystems.filesystems_state uses a module listed above it, which is the healthy direction.
36→3 filesystems.filesystems_state uses app.mode✕
- Connections
- 1 pair of types, where a type in filesystems.filesystems_state uses a type in app.mode.
- The types involved
broot.filesystems.filesystems_state.FilesystemState→broot.app.mode.Mode
- Direction
- filesystems.filesystems_state uses app.mode, so a change to app.mode can break filesystems.filesystems_state, while a change to filesystems.filesystems_state can't break app.mode.
- Position
- Below the diagonal: filesystems.filesystems_state uses a module listed above it, which is the healthy direction.
36→4 filesystems.filesystems_state uses app.state_type✕
- Connections
- 1 pair of types, where a type in filesystems.filesystems_state uses a type in app.state_type.
- The types involved
broot.filesystems.filesystems_state.FilesystemState→broot.app.state_type.PanelStateType
- Direction
- filesystems.filesystems_state uses app.state_type, so a change to app.state_type can break filesystems.filesystems_state, while a change to filesystems.filesystems_state can't break app.state_type.
- Position
- Below the diagonal: filesystems.filesystems_state uses a module listed above it, which is the healthy direction.
36→5 filesystems.filesystems_state uses command.scroll✕
- Connections
- 1 pair of types, where a type in filesystems.filesystems_state uses a type in command.scroll.
- The types involved
broot.filesystems.filesystems_state.FilesystemState→broot.command.scroll.ScrollCommand
- Direction
- filesystems.filesystems_state uses command.scroll, so a change to command.scroll can break filesystems.filesystems_state, while a change to filesystems.filesystems_state can't break command.scroll.
- Position
- Below the diagonal: filesystems.filesystems_state uses a module listed above it, which is the healthy direction.
36→6 filesystems.filesystems_state uses command.trigger_type✕
- Connections
- 1 pair of types, where a type in filesystems.filesystems_state uses a type in command.trigger_type.
- The types involved
broot.filesystems.filesystems_state.FilesystemState→broot.command.trigger_type.TriggerType
- Direction
- filesystems.filesystems_state uses command.trigger_type, so a change to command.trigger_type can break filesystems.filesystems_state, while a change to filesystems.filesystems_state can't break command.trigger_type.
- Position
- Below the diagonal: filesystems.filesystems_state uses a module listed above it, which is the healthy direction.
36→7 filesystems.filesystems_state uses pattern.pattern✕
- Connections
- 1 pair of types, where a type in filesystems.filesystems_state uses a type in pattern.pattern.
- The types involved
broot.filesystems.filesystems_state.FilteredContent→broot.pattern.pattern.Pattern
- Direction
- filesystems.filesystems_state uses pattern.pattern, so a change to pattern.pattern can break filesystems.filesystems_state, while a change to filesystems.filesystems_state can't break pattern.pattern.
- Position
- Below the diagonal: filesystems.filesystems_state uses a module listed above it, which is the healthy direction.
36→10 filesystems.filesystems_state uses verb.internal_execution✕
- Connections
- 1 pair of types, where a type in filesystems.filesystems_state uses a type in verb.internal_execution.
- The types involved
broot.filesystems.filesystems_state.FilesystemState→broot.verb.internal_execution.InternalExecution
- Direction
- filesystems.filesystems_state uses verb.internal_execution, so a change to verb.internal_execution can break filesystems.filesystems_state, while a change to filesystems.filesystems_state can't break verb.internal_execution.
- Position
- Below the diagonal: filesystems.filesystems_state uses a module listed above it, which is the healthy direction.
36→11 filesystems.filesystems_state uses verb.verb_invocation✕
- Connections
- 1 pair of types, where a type in filesystems.filesystems_state uses a type in verb.verb_invocation.
- The types involved
broot.filesystems.filesystems_state.FilesystemState→broot.verb.verb_invocation.VerbInvocation
- Direction
- filesystems.filesystems_state uses verb.verb_invocation, so a change to verb.verb_invocation can break filesystems.filesystems_state, while a change to filesystems.filesystems_state can't break verb.verb_invocation.
- Position
- Below the diagonal: filesystems.filesystems_state uses a module listed above it, which is the healthy direction.
36→12 filesystems.filesystems_state uses app.selection✕
- Connections
- 1 pair of types, where a type in filesystems.filesystems_state uses a type in app.selection.
- The types involved
broot.filesystems.filesystems_state.FilesystemState→broot.app.selection.Selection
- Direction
- filesystems.filesystems_state uses app.selection, so a change to app.selection can break filesystems.filesystems_state, while a change to filesystems.filesystems_state can't break app.selection.
- Position
- Below the diagonal: filesystems.filesystems_state uses a module listed above it, which is the healthy direction.
36→14 filesystems.filesystems_state uses pattern.input_pattern✕
- Connections
- 1 pair of types, where a type in filesystems.filesystems_state uses a type in pattern.input_pattern.
- The types involved
broot.filesystems.filesystems_state.FilesystemState→broot.pattern.input_pattern.InputPattern
- Direction
- filesystems.filesystems_state uses pattern.input_pattern, so a change to pattern.input_pattern can break filesystems.filesystems_state, while a change to filesystems.filesystems_state can't break pattern.input_pattern.
- Position
- Below the diagonal: filesystems.filesystems_state uses a module listed above it, which is the healthy direction.
36→16 filesystems.filesystems_state uses verb.invocation_parser✕
- Connections
- 1 pair of types, where a type in filesystems.filesystems_state uses a type in verb.invocation_parser.
- The types involved
broot.filesystems.filesystems_state.FilesystemState→broot.verb.invocation_parser.InvocationParser
- Direction
- filesystems.filesystems_state uses verb.invocation_parser, so a change to verb.invocation_parser can break filesystems.filesystems_state, while a change to filesystems.filesystems_state can't break verb.invocation_parser.
- Position
- Below the diagonal: filesystems.filesystems_state uses a module listed above it, which is the healthy direction.
36→18 filesystems.filesystems_state uses tree.tree_options✕
- Connections
- 1 pair of types, where a type in filesystems.filesystems_state uses a type in tree.tree_options.
- The types involved
broot.filesystems.filesystems_state.FilesystemState→broot.tree.tree_options.TreeOptions
- Direction
- filesystems.filesystems_state uses tree.tree_options, so a change to tree.tree_options can break filesystems.filesystems_state, while a change to filesystems.filesystems_state can't break tree.tree_options.
- Position
- Below the diagonal: filesystems.filesystems_state uses a module listed above it, which is the healthy direction.
36→21 filesystems.filesystems_state uses app.app_context✕
- Connections
- 1 pair of types, where a type in filesystems.filesystems_state uses a type in app.app_context.
- The types involved
broot.filesystems.filesystems_state.FilesystemState→broot.app.app_context.AppContext
- Direction
- filesystems.filesystems_state uses app.app_context, so a change to app.app_context can break filesystems.filesystems_state, while a change to filesystems.filesystems_state can't break app.app_context.
- Position
- Below the diagonal: filesystems.filesystems_state uses a module listed above it, which is the healthy direction.
36→22 filesystems.filesystems_state uses command.command✕
- Connections
- 1 pair of types, where a type in filesystems.filesystems_state uses a type in command.command.
- The types involved
broot.filesystems.filesystems_state.FilesystemState→broot.command.command.Command
- Direction
- filesystems.filesystems_state uses command.command, so a change to command.command can break filesystems.filesystems_state, while a change to filesystems.filesystems_state can't break command.command.
- Position
- Below the diagonal: filesystems.filesystems_state uses a module listed above it, which is the healthy direction.
36→24 filesystems.filesystems_state uses display.screen✕
- Connections
- 1 pair of types, where a type in filesystems.filesystems_state uses a type in display.screen.
- The types involved
broot.filesystems.filesystems_state.FilesystemState→broot.display.screen.Screen
- Direction
- filesystems.filesystems_state uses display.screen, so a change to display.screen can break filesystems.filesystems_state, while a change to filesystems.filesystems_state can't break display.screen.
- Position
- Below the diagonal: filesystems.filesystems_state uses a module listed above it, which is the healthy direction.
36→27 filesystems.filesystems_state uses app.cmd_context✕
- Connections
- 1 pair of types, where a type in filesystems.filesystems_state uses a type in app.cmd_context.
- The types involved
broot.filesystems.filesystems_state.FilesystemState→broot.app.cmd_context.CmdContext
- Direction
- filesystems.filesystems_state uses app.cmd_context, so a change to app.cmd_context can break filesystems.filesystems_state, while a change to filesystems.filesystems_state can't break app.cmd_context.
- Position
- Below the diagonal: filesystems.filesystems_state uses a module listed above it, which is the healthy direction.
36→28 filesystems.filesystems_state uses app.display_context✕
- Connections
- 1 pair of types, where a type in filesystems.filesystems_state uses a type in app.display_context.
- The types involved
broot.filesystems.filesystems_state.FilesystemState→broot.app.display_context.DisplayContext
- Direction
- filesystems.filesystems_state uses app.display_context, so a change to app.display_context can break filesystems.filesystems_state, while a change to filesystems.filesystems_state can't break app.display_context.
- Position
- Below the diagonal: filesystems.filesystems_state uses a module listed above it, which is the healthy direction.
36→31 filesystems.filesystems_state uses app.panel_state✕
- Connections
- 1 pair of types, where a type in filesystems.filesystems_state uses a type in app.panel_state.
- The types involved
broot.filesystems.filesystems_state.FilesystemState→broot.app.panel_state.PanelState
- Direction
- filesystems.filesystems_state uses app.panel_state, so a change to app.panel_state can break filesystems.filesystems_state, while a change to filesystems.filesystems_state can't break app.panel_state.
- Position
- Below the diagonal: filesystems.filesystems_state uses a module listed above it, which is the healthy direction.
37→1 help.help_state uses app.app_state✕
- Connections
- 1 pair of types, where a type in help.help_state uses a type in app.app_state.
- The types involved
broot.help.help_state.HelpState→broot.app.app_state.AppState
- Direction
- help.help_state uses app.app_state, so a change to app.app_state can break help.help_state, while a change to help.help_state can't break app.app_state.
- Position
- Below the diagonal: help.help_state uses a module listed above it, which is the healthy direction.
37→2 help.help_state uses app.cmd_result✕
- Connections
- 1 pair of types, where a type in help.help_state uses a type in app.cmd_result.
- The types involved
broot.help.help_state.HelpState→broot.app.cmd_result.CmdResult
- Direction
- help.help_state uses app.cmd_result, so a change to app.cmd_result can break help.help_state, while a change to help.help_state can't break app.cmd_result.
- Position
- Below the diagonal: help.help_state uses a module listed above it, which is the healthy direction.
37→3 help.help_state uses app.mode✕
- Connections
- 1 pair of types, where a type in help.help_state uses a type in app.mode.
- The types involved
broot.help.help_state.HelpState→broot.app.mode.Mode
- Direction
- help.help_state uses app.mode, so a change to app.mode can break help.help_state, while a change to help.help_state can't break app.mode.
- Position
- Below the diagonal: help.help_state uses a module listed above it, which is the healthy direction.
37→4 help.help_state uses app.state_type✕
- Connections
- 1 pair of types, where a type in help.help_state uses a type in app.state_type.
- The types involved
broot.help.help_state.HelpState→broot.app.state_type.PanelStateType
- Direction
- help.help_state uses app.state_type, so a change to app.state_type can break help.help_state, while a change to help.help_state can't break app.state_type.
- Position
- Below the diagonal: help.help_state uses a module listed above it, which is the healthy direction.
37→6 help.help_state uses command.trigger_type✕
- Connections
- 1 pair of types, where a type in help.help_state uses a type in command.trigger_type.
- The types involved
broot.help.help_state.HelpState→broot.command.trigger_type.TriggerType
- Direction
- help.help_state uses command.trigger_type, so a change to command.trigger_type can break help.help_state, while a change to help.help_state can't break command.trigger_type.
- Position
- Below the diagonal: help.help_state uses a module listed above it, which is the healthy direction.
37→7 help.help_state uses pattern.pattern✕
- Connections
- 1 pair of types, where a type in help.help_state uses a type in pattern.pattern.
- The types involved
broot.help.help_state.HelpState→broot.pattern.pattern.Pattern
- Direction
- help.help_state uses pattern.pattern, so a change to pattern.pattern can break help.help_state, while a change to help.help_state can't break pattern.pattern.
- Position
- Below the diagonal: help.help_state uses a module listed above it, which is the healthy direction.
37→10 help.help_state uses verb.internal_execution✕
- Connections
- 1 pair of types, where a type in help.help_state uses a type in verb.internal_execution.
- The types involved
broot.help.help_state.HelpState→broot.verb.internal_execution.InternalExecution
- Direction
- help.help_state uses verb.internal_execution, so a change to verb.internal_execution can break help.help_state, while a change to help.help_state can't break verb.internal_execution.
- Position
- Below the diagonal: help.help_state uses a module listed above it, which is the healthy direction.
37→11 help.help_state uses verb.verb_invocation✕
- Connections
- 1 pair of types, where a type in help.help_state uses a type in verb.verb_invocation.
- The types involved
broot.help.help_state.HelpState→broot.verb.verb_invocation.VerbInvocation
- Direction
- help.help_state uses verb.verb_invocation, so a change to verb.verb_invocation can break help.help_state, while a change to help.help_state can't break verb.verb_invocation.
- Position
- Below the diagonal: help.help_state uses a module listed above it, which is the healthy direction.
37→12 help.help_state uses app.selection✕
- Connections
- 1 pair of types, where a type in help.help_state uses a type in app.selection.
- The types involved
broot.help.help_state.HelpState→broot.app.selection.Selection
- Direction
- help.help_state uses app.selection, so a change to app.selection can break help.help_state, while a change to help.help_state can't break app.selection.
- Position
- Below the diagonal: help.help_state uses a module listed above it, which is the healthy direction.
37→14 help.help_state uses pattern.input_pattern✕
- Connections
- 1 pair of types, where a type in help.help_state uses a type in pattern.input_pattern.
- The types involved
broot.help.help_state.HelpState→broot.pattern.input_pattern.InputPattern
- Direction
- help.help_state uses pattern.input_pattern, so a change to pattern.input_pattern can break help.help_state, while a change to help.help_state can't break pattern.input_pattern.
- Position
- Below the diagonal: help.help_state uses a module listed above it, which is the healthy direction.
37→16 help.help_state uses verb.invocation_parser✕
- Connections
- 1 pair of types, where a type in help.help_state uses a type in verb.invocation_parser.
- The types involved
broot.help.help_state.HelpState→broot.verb.invocation_parser.InvocationParser
- Direction
- help.help_state uses verb.invocation_parser, so a change to verb.invocation_parser can break help.help_state, while a change to help.help_state can't break verb.invocation_parser.
- Position
- Below the diagonal: help.help_state uses a module listed above it, which is the healthy direction.
37→18 help.help_state uses tree.tree_options✕
- Connections
- 1 pair of types, where a type in help.help_state uses a type in tree.tree_options.
- The types involved
broot.help.help_state.HelpState→broot.tree.tree_options.TreeOptions
- Direction
- help.help_state uses tree.tree_options, so a change to tree.tree_options can break help.help_state, while a change to help.help_state can't break tree.tree_options.
- Position
- Below the diagonal: help.help_state uses a module listed above it, which is the healthy direction.
37→21 help.help_state uses app.app_context✕
- Connections
- 1 pair of types, where a type in help.help_state uses a type in app.app_context.
- The types involved
broot.help.help_state.HelpState→broot.app.app_context.AppContext
- Direction
- help.help_state uses app.app_context, so a change to app.app_context can break help.help_state, while a change to help.help_state can't break app.app_context.
- Position
- Below the diagonal: help.help_state uses a module listed above it, which is the healthy direction.
37→22 help.help_state uses command.command✕
- Connections
- 1 pair of types, where a type in help.help_state uses a type in command.command.
- The types involved
broot.help.help_state.HelpState→broot.command.command.Command
- Direction
- help.help_state uses command.command, so a change to command.command can break help.help_state, while a change to help.help_state can't break command.command.
- Position
- Below the diagonal: help.help_state uses a module listed above it, which is the healthy direction.
37→24 help.help_state uses display.screen✕
- Connections
- 1 pair of types, where a type in help.help_state uses a type in display.screen.
- The types involved
broot.help.help_state.HelpState→broot.display.screen.Screen
- Direction
- help.help_state uses display.screen, so a change to display.screen can break help.help_state, while a change to help.help_state can't break display.screen.
- Position
- Below the diagonal: help.help_state uses a module listed above it, which is the healthy direction.
37→27 help.help_state uses app.cmd_context✕
- Connections
- 1 pair of types, where a type in help.help_state uses a type in app.cmd_context.
- The types involved
broot.help.help_state.HelpState→broot.app.cmd_context.CmdContext
- Direction
- help.help_state uses app.cmd_context, so a change to app.cmd_context can break help.help_state, while a change to help.help_state can't break app.cmd_context.
- Position
- Below the diagonal: help.help_state uses a module listed above it, which is the healthy direction.
37→28 help.help_state uses app.display_context✕
- Connections
- 1 pair of types, where a type in help.help_state uses a type in app.display_context.
- The types involved
broot.help.help_state.HelpState→broot.app.display_context.DisplayContext
- Direction
- help.help_state uses app.display_context, so a change to app.display_context can break help.help_state, while a change to help.help_state can't break app.display_context.
- Position
- Below the diagonal: help.help_state uses a module listed above it, which is the healthy direction.
37→31 help.help_state uses app.panel_state✕
- Connections
- 1 pair of types, where a type in help.help_state uses a type in app.panel_state.
- The types involved
broot.help.help_state.HelpState→broot.app.panel_state.PanelState
- Direction
- help.help_state uses app.panel_state, so a change to app.panel_state can break help.help_state, while a change to help.help_state can't break app.panel_state.
- Position
- Below the diagonal: help.help_state uses a module listed above it, which is the healthy direction.
38→1 preview.preview_state uses app.app_state✕
- Connections
- 1 pair of types, where a type in preview.preview_state uses a type in app.app_state.
- The types involved
broot.preview.preview_state.PreviewState→broot.app.app_state.AppState
- Direction
- preview.preview_state uses app.app_state, so a change to app.app_state can break preview.preview_state, while a change to preview.preview_state can't break app.app_state.
- Position
- Below the diagonal: preview.preview_state uses a module listed above it, which is the healthy direction.
38→2 preview.preview_state uses app.cmd_result✕
- Connections
- 1 pair of types, where a type in preview.preview_state uses a type in app.cmd_result.
- The types involved
broot.preview.preview_state.PreviewState→broot.app.cmd_result.CmdResult
- Direction
- preview.preview_state uses app.cmd_result, so a change to app.cmd_result can break preview.preview_state, while a change to preview.preview_state can't break app.cmd_result.
- Position
- Below the diagonal: preview.preview_state uses a module listed above it, which is the healthy direction.
38→3 preview.preview_state uses app.mode✕
- Connections
- 1 pair of types, where a type in preview.preview_state uses a type in app.mode.
- The types involved
broot.preview.preview_state.PreviewState→broot.app.mode.Mode
- Direction
- preview.preview_state uses app.mode, so a change to app.mode can break preview.preview_state, while a change to preview.preview_state can't break app.mode.
- Position
- Below the diagonal: preview.preview_state uses a module listed above it, which is the healthy direction.
38→4 preview.preview_state uses app.state_type✕
- Connections
- 1 pair of types, where a type in preview.preview_state uses a type in app.state_type.
- The types involved
broot.preview.preview_state.PreviewState→broot.app.state_type.PanelStateType
- Direction
- preview.preview_state uses app.state_type, so a change to app.state_type can break preview.preview_state, while a change to preview.preview_state can't break app.state_type.
- Position
- Below the diagonal: preview.preview_state uses a module listed above it, which is the healthy direction.
38→6 preview.preview_state uses command.trigger_type✕
- Connections
- 1 pair of types, where a type in preview.preview_state uses a type in command.trigger_type.
- The types involved
broot.preview.preview_state.PreviewState→broot.command.trigger_type.TriggerType
- Direction
- preview.preview_state uses command.trigger_type, so a change to command.trigger_type can break preview.preview_state, while a change to preview.preview_state can't break command.trigger_type.
- Position
- Below the diagonal: preview.preview_state uses a module listed above it, which is the healthy direction.
38→9 preview.preview_state uses task_sync✕
- Connections
- 1 pair of types, where a type in preview.preview_state uses a type in task_sync.
- The types involved
broot.preview.preview_state.PreviewState→broot.task_sync.Dam
- Direction
- preview.preview_state uses task_sync, so a change to task_sync can break preview.preview_state, while a change to preview.preview_state can't break task_sync.
- Position
- Below the diagonal: preview.preview_state uses a module listed above it, which is the healthy direction.
38→10 preview.preview_state uses verb.internal_execution✕
- Connections
- 1 pair of types, where a type in preview.preview_state uses a type in verb.internal_execution.
- The types involved
broot.preview.preview_state.PreviewState→broot.verb.internal_execution.InternalExecution
- Direction
- preview.preview_state uses verb.internal_execution, so a change to verb.internal_execution can break preview.preview_state, while a change to preview.preview_state can't break verb.internal_execution.
- Position
- Below the diagonal: preview.preview_state uses a module listed above it, which is the healthy direction.
38→11 preview.preview_state uses verb.verb_invocation✕
- Connections
- 1 pair of types, where a type in preview.preview_state uses a type in verb.verb_invocation.
- The types involved
broot.preview.preview_state.PreviewState→broot.verb.verb_invocation.VerbInvocation
- Direction
- preview.preview_state uses verb.verb_invocation, so a change to verb.verb_invocation can break preview.preview_state, while a change to preview.preview_state can't break verb.verb_invocation.
- Position
- Below the diagonal: preview.preview_state uses a module listed above it, which is the healthy direction.
38→12 preview.preview_state uses app.selection✕
- Connections
- 1 pair of types, where a type in preview.preview_state uses a type in app.selection.
- The types involved
broot.preview.preview_state.PreviewState→broot.app.selection.Selection
- Direction
- preview.preview_state uses app.selection, so a change to app.selection can break preview.preview_state, while a change to preview.preview_state can't break app.selection.
- Position
- Below the diagonal: preview.preview_state uses a module listed above it, which is the healthy direction.
38→14 preview.preview_state uses pattern.input_pattern✕
- Connections
- 1 pair of types, where a type in preview.preview_state uses a type in pattern.input_pattern.
- The types involved
broot.preview.preview_state.PreviewState→broot.pattern.input_pattern.InputPattern
- Direction
- preview.preview_state uses pattern.input_pattern, so a change to pattern.input_pattern can break preview.preview_state, while a change to preview.preview_state can't break pattern.input_pattern.
- Position
- Below the diagonal: preview.preview_state uses a module listed above it, which is the healthy direction.
38→16 preview.preview_state uses verb.invocation_parser✕
- Connections
- 1 pair of types, where a type in preview.preview_state uses a type in verb.invocation_parser.
- The types involved
broot.preview.preview_state.PreviewState→broot.verb.invocation_parser.InvocationParser
- Direction
- preview.preview_state uses verb.invocation_parser, so a change to verb.invocation_parser can break preview.preview_state, while a change to preview.preview_state can't break verb.invocation_parser.
- Position
- Below the diagonal: preview.preview_state uses a module listed above it, which is the healthy direction.
38→18 preview.preview_state uses tree.tree_options✕
- Connections
- 1 pair of types, where a type in preview.preview_state uses a type in tree.tree_options.
- The types involved
broot.preview.preview_state.PreviewState→broot.tree.tree_options.TreeOptions
- Direction
- preview.preview_state uses tree.tree_options, so a change to tree.tree_options can break preview.preview_state, while a change to preview.preview_state can't break tree.tree_options.
- Position
- Below the diagonal: preview.preview_state uses a module listed above it, which is the healthy direction.
38→21 preview.preview_state uses app.app_context✕
- Connections
- 1 pair of types, where a type in preview.preview_state uses a type in app.app_context.
- The types involved
broot.preview.preview_state.PreviewState→broot.app.app_context.AppContext
- Direction
- preview.preview_state uses app.app_context, so a change to app.app_context can break preview.preview_state, while a change to preview.preview_state can't break app.app_context.
- Position
- Below the diagonal: preview.preview_state uses a module listed above it, which is the healthy direction.
38→22 preview.preview_state uses command.command✕
- Connections
- 1 pair of types, where a type in preview.preview_state uses a type in command.command.
- The types involved
broot.preview.preview_state.PreviewState→broot.command.command.Command
- Direction
- preview.preview_state uses command.command, so a change to command.command can break preview.preview_state, while a change to preview.preview_state can't break command.command.
- Position
- Below the diagonal: preview.preview_state uses a module listed above it, which is the healthy direction.
38→24 preview.preview_state uses display.screen✕
- Connections
- 1 pair of types, where a type in preview.preview_state uses a type in display.screen.
- The types involved
broot.preview.preview_state.PreviewState→broot.display.screen.Screen
- Direction
- preview.preview_state uses display.screen, so a change to display.screen can break preview.preview_state, while a change to preview.preview_state can't break display.screen.
- Position
- Below the diagonal: preview.preview_state uses a module listed above it, which is the healthy direction.
38→27 preview.preview_state uses app.cmd_context✕
- Connections
- 1 pair of types, where a type in preview.preview_state uses a type in app.cmd_context.
- The types involved
broot.preview.preview_state.PreviewState→broot.app.cmd_context.CmdContext
- Direction
- preview.preview_state uses app.cmd_context, so a change to app.cmd_context can break preview.preview_state, while a change to preview.preview_state can't break app.cmd_context.
- Position
- Below the diagonal: preview.preview_state uses a module listed above it, which is the healthy direction.
38→28 preview.preview_state uses app.display_context✕
- Connections
- 1 pair of types, where a type in preview.preview_state uses a type in app.display_context.
- The types involved
broot.preview.preview_state.PreviewState→broot.app.display_context.DisplayContext
- Direction
- preview.preview_state uses app.display_context, so a change to app.display_context can break preview.preview_state, while a change to preview.preview_state can't break app.display_context.
- Position
- Below the diagonal: preview.preview_state uses a module listed above it, which is the healthy direction.
38→31 preview.preview_state uses app.panel_state✕
- Connections
- 1 pair of types, where a type in preview.preview_state uses a type in app.panel_state.
- The types involved
broot.preview.preview_state.PreviewState→broot.app.panel_state.PanelState
- Direction
- preview.preview_state uses app.panel_state, so a change to app.panel_state can break preview.preview_state, while a change to preview.preview_state can't break app.panel_state.
- Position
- Below the diagonal: preview.preview_state uses a module listed above it, which is the healthy direction.
38→32 preview.preview_state uses preview.preview✕
- Connections
- 1 pair of types, where a type in preview.preview_state uses a type in preview.preview.
- The types involved
broot.preview.preview_state.PreviewState→broot.preview.preview.Preview
- Direction
- preview.preview_state uses preview.preview, so a change to preview.preview can break preview.preview_state, while a change to preview.preview_state can't break preview.preview.
- Position
- Below the diagonal: preview.preview_state uses a module listed above it, which is the healthy direction.
39→1 stage.stage_state uses app.app_state✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in app.app_state.
- The types involved
broot.stage.stage_state.StageState→broot.app.app_state.AppState
- Direction
- stage.stage_state uses app.app_state, so a change to app.app_state can break stage.stage_state, while a change to stage.stage_state can't break app.app_state.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
39→2 stage.stage_state uses app.cmd_result✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in app.cmd_result.
- The types involved
broot.stage.stage_state.StageState→broot.app.cmd_result.CmdResult
- Direction
- stage.stage_state uses app.cmd_result, so a change to app.cmd_result can break stage.stage_state, while a change to stage.stage_state can't break app.cmd_result.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
39→3 stage.stage_state uses app.mode✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in app.mode.
- The types involved
broot.stage.stage_state.StageState→broot.app.mode.Mode
- Direction
- stage.stage_state uses app.mode, so a change to app.mode can break stage.stage_state, while a change to stage.stage_state can't break app.mode.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
39→4 stage.stage_state uses app.state_type✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in app.state_type.
- The types involved
broot.stage.stage_state.StageState→broot.app.state_type.PanelStateType
- Direction
- stage.stage_state uses app.state_type, so a change to app.state_type can break stage.stage_state, while a change to stage.stage_state can't break app.state_type.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
39→5 stage.stage_state uses command.scroll✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in command.scroll.
- The types involved
broot.stage.stage_state.StageState→broot.command.scroll.ScrollCommand
- Direction
- stage.stage_state uses command.scroll, so a change to command.scroll can break stage.stage_state, while a change to stage.stage_state can't break command.scroll.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
39→6 stage.stage_state uses command.trigger_type✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in command.trigger_type.
- The types involved
broot.stage.stage_state.StageState→broot.command.trigger_type.TriggerType
- Direction
- stage.stage_state uses command.trigger_type, so a change to command.trigger_type can break stage.stage_state, while a change to stage.stage_state can't break command.trigger_type.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
39→8 stage.stage_state uses skin.style_map✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in skin.style_map.
- The types involved
broot.stage.stage_state.StageState→broot.skin.style_map.StyleMap
- Direction
- stage.stage_state uses skin.style_map, so a change to skin.style_map can break stage.stage_state, while a change to stage.stage_state can't break skin.style_map.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
39→9 stage.stage_state uses task_sync✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in task_sync.
- The types involved
broot.stage.stage_state.StageState→broot.task_sync.Dam
- Direction
- stage.stage_state uses task_sync, so a change to task_sync can break stage.stage_state, while a change to stage.stage_state can't break task_sync.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
39→10 stage.stage_state uses verb.internal_execution✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in verb.internal_execution.
- The types involved
broot.stage.stage_state.StageState→broot.verb.internal_execution.InternalExecution
- Direction
- stage.stage_state uses verb.internal_execution, so a change to verb.internal_execution can break stage.stage_state, while a change to stage.stage_state can't break verb.internal_execution.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
39→11 stage.stage_state uses verb.verb_invocation✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in verb.verb_invocation.
- The types involved
broot.stage.stage_state.StageState→broot.verb.verb_invocation.VerbInvocation
- Direction
- stage.stage_state uses verb.verb_invocation, so a change to verb.verb_invocation can break stage.stage_state, while a change to stage.stage_state can't break verb.verb_invocation.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
39→12 stage.stage_state uses app.selection✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in app.selection.
- The types involved
broot.stage.stage_state.StageState→broot.app.selection.Selection
- Direction
- stage.stage_state uses app.selection, so a change to app.selection can break stage.stage_state, while a change to stage.stage_state can't break app.selection.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
39→14 stage.stage_state uses pattern.input_pattern✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in pattern.input_pattern.
- The types involved
broot.stage.stage_state.StageState→broot.pattern.input_pattern.InputPattern
- Direction
- stage.stage_state uses pattern.input_pattern, so a change to pattern.input_pattern can break stage.stage_state, while a change to stage.stage_state can't break pattern.input_pattern.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
39→16 stage.stage_state uses verb.invocation_parser✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in verb.invocation_parser.
- The types involved
broot.stage.stage_state.StageState→broot.verb.invocation_parser.InvocationParser
- Direction
- stage.stage_state uses verb.invocation_parser, so a change to verb.invocation_parser can break stage.stage_state, while a change to stage.stage_state can't break verb.invocation_parser.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
39→17 stage.stage_state uses app.sel_info✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in app.sel_info.
- The types involved
broot.stage.stage_state.StageState→broot.app.sel_info.SelInfo
- Direction
- stage.stage_state uses app.sel_info, so a change to app.sel_info can break stage.stage_state, while a change to stage.stage_state can't break app.sel_info.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
39→18 stage.stage_state uses tree.tree_options✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in tree.tree_options.
- The types involved
broot.stage.stage_state.StageState→broot.tree.tree_options.TreeOptions
- Direction
- stage.stage_state uses tree.tree_options, so a change to tree.tree_options can break stage.stage_state, while a change to stage.stage_state can't break tree.tree_options.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
39→21 stage.stage_state uses app.app_context✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in app.app_context.
- The types involved
broot.stage.stage_state.StageState→broot.app.app_context.AppContext
- Direction
- stage.stage_state uses app.app_context, so a change to app.app_context can break stage.stage_state, while a change to stage.stage_state can't break app.app_context.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
39→22 stage.stage_state uses command.command✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in command.command.
- The types involved
broot.stage.stage_state.StageState→broot.command.command.Command
- Direction
- stage.stage_state uses command.command, so a change to command.command can break stage.stage_state, while a change to stage.stage_state can't break command.command.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
39→24 stage.stage_state uses display.screen✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in display.screen.
- The types involved
broot.stage.stage_state.StageState→broot.display.screen.Screen
- Direction
- stage.stage_state uses display.screen, so a change to display.screen can break stage.stage_state, while a change to stage.stage_state can't break display.screen.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
39→27 stage.stage_state uses app.cmd_context✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in app.cmd_context.
- The types involved
broot.stage.stage_state.StageState→broot.app.cmd_context.CmdContext
- Direction
- stage.stage_state uses app.cmd_context, so a change to app.cmd_context can break stage.stage_state, while a change to stage.stage_state can't break app.cmd_context.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
39→28 stage.stage_state uses app.display_context✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in app.display_context.
- The types involved
broot.stage.stage_state.StageState→broot.app.display_context.DisplayContext
- Direction
- stage.stage_state uses app.display_context, so a change to app.display_context can break stage.stage_state, while a change to stage.stage_state can't break app.display_context.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
39→31 stage.stage_state uses app.panel_state✕
- Connections
- 1 pair of types, where a type in stage.stage_state uses a type in app.panel_state.
- The types involved
broot.stage.stage_state.StageState→broot.app.panel_state.PanelState
- Direction
- stage.stage_state uses app.panel_state, so a change to app.panel_state can break stage.stage_state, while a change to stage.stage_state can't break app.panel_state.
- Position
- Below the diagonal: stage.stage_state uses a module listed above it, which is the healthy direction.
40→1 trash.trash_state uses app.app_state✕
- Connections
- 1 pair of types, where a type in trash.trash_state uses a type in app.app_state.
- The types involved
broot.trash.trash_state.TrashState→broot.app.app_state.AppState
- Direction
- trash.trash_state uses app.app_state, so a change to app.app_state can break trash.trash_state, while a change to trash.trash_state can't break app.app_state.
- Position
- Below the diagonal: trash.trash_state uses a module listed above it, which is the healthy direction.
40→2 trash.trash_state uses app.cmd_result✕
- Connections
- 1 pair of types, where a type in trash.trash_state uses a type in app.cmd_result.
- The types involved
broot.trash.trash_state.TrashState→broot.app.cmd_result.CmdResult
- Direction
- trash.trash_state uses app.cmd_result, so a change to app.cmd_result can break trash.trash_state, while a change to trash.trash_state can't break app.cmd_result.
- Position
- Below the diagonal: trash.trash_state uses a module listed above it, which is the healthy direction.
40→3 trash.trash_state uses app.mode✕
- Connections
- 1 pair of types, where a type in trash.trash_state uses a type in app.mode.
- The types involved
broot.trash.trash_state.TrashState→broot.app.mode.Mode
- Direction
- trash.trash_state uses app.mode, so a change to app.mode can break trash.trash_state, while a change to trash.trash_state can't break app.mode.
- Position
- Below the diagonal: trash.trash_state uses a module listed above it, which is the healthy direction.
40→4 trash.trash_state uses app.state_type✕
- Connections
- 1 pair of types, where a type in trash.trash_state uses a type in app.state_type.
- The types involved
broot.trash.trash_state.TrashState→broot.app.state_type.PanelStateType
- Direction
- trash.trash_state uses app.state_type, so a change to app.state_type can break trash.trash_state, while a change to trash.trash_state can't break app.state_type.
- Position
- Below the diagonal: trash.trash_state uses a module listed above it, which is the healthy direction.
40→5 trash.trash_state uses command.scroll✕
- Connections
- 1 pair of types, where a type in trash.trash_state uses a type in command.scroll.
- The types involved
broot.trash.trash_state.TrashState→broot.command.scroll.ScrollCommand
- Direction
- trash.trash_state uses command.scroll, so a change to command.scroll can break trash.trash_state, while a change to trash.trash_state can't break command.scroll.
- Position
- Below the diagonal: trash.trash_state uses a module listed above it, which is the healthy direction.
40→6 trash.trash_state uses command.trigger_type✕
- Connections
- 1 pair of types, where a type in trash.trash_state uses a type in command.trigger_type.
- The types involved
broot.trash.trash_state.TrashState→broot.command.trigger_type.TriggerType
- Direction
- trash.trash_state uses command.trigger_type, so a change to command.trigger_type can break trash.trash_state, while a change to trash.trash_state can't break command.trigger_type.
- Position
- Below the diagonal: trash.trash_state uses a module listed above it, which is the healthy direction.
40→7 trash.trash_state uses pattern.pattern✕
- Connections
- 1 pair of types, where a type in trash.trash_state uses a type in pattern.pattern.
- The types involved
broot.trash.trash_state.FilteredContent→broot.pattern.pattern.Pattern
- Direction
- trash.trash_state uses pattern.pattern, so a change to pattern.pattern can break trash.trash_state, while a change to trash.trash_state can't break pattern.pattern.
- Position
- Below the diagonal: trash.trash_state uses a module listed above it, which is the healthy direction.
40→10 trash.trash_state uses verb.internal_execution✕
- Connections
- 1 pair of types, where a type in trash.trash_state uses a type in verb.internal_execution.
- The types involved
broot.trash.trash_state.TrashState→broot.verb.internal_execution.InternalExecution
- Direction
- trash.trash_state uses verb.internal_execution, so a change to verb.internal_execution can break trash.trash_state, while a change to trash.trash_state can't break verb.internal_execution.
- Position
- Below the diagonal: trash.trash_state uses a module listed above it, which is the healthy direction.
40→11 trash.trash_state uses verb.verb_invocation✕
- Connections
- 1 pair of types, where a type in trash.trash_state uses a type in verb.verb_invocation.
- The types involved
broot.trash.trash_state.TrashState→broot.verb.verb_invocation.VerbInvocation
- Direction
- trash.trash_state uses verb.verb_invocation, so a change to verb.verb_invocation can break trash.trash_state, while a change to trash.trash_state can't break verb.verb_invocation.
- Position
- Below the diagonal: trash.trash_state uses a module listed above it, which is the healthy direction.
40→12 trash.trash_state uses app.selection✕
- Connections
- 1 pair of types, where a type in trash.trash_state uses a type in app.selection.
- The types involved
broot.trash.trash_state.TrashState→broot.app.selection.Selection
- Direction
- trash.trash_state uses app.selection, so a change to app.selection can break trash.trash_state, while a change to trash.trash_state can't break app.selection.
- Position
- Below the diagonal: trash.trash_state uses a module listed above it, which is the healthy direction.
40→14 trash.trash_state uses pattern.input_pattern✕
- Connections
- 1 pair of types, where a type in trash.trash_state uses a type in pattern.input_pattern.
- The types involved
broot.trash.trash_state.TrashState→broot.pattern.input_pattern.InputPattern
- Direction
- trash.trash_state uses pattern.input_pattern, so a change to pattern.input_pattern can break trash.trash_state, while a change to trash.trash_state can't break pattern.input_pattern.
- Position
- Below the diagonal: trash.trash_state uses a module listed above it, which is the healthy direction.
40→16 trash.trash_state uses verb.invocation_parser✕
- Connections
- 1 pair of types, where a type in trash.trash_state uses a type in verb.invocation_parser.
- The types involved
broot.trash.trash_state.TrashState→broot.verb.invocation_parser.InvocationParser
- Direction
- trash.trash_state uses verb.invocation_parser, so a change to verb.invocation_parser can break trash.trash_state, while a change to trash.trash_state can't break verb.invocation_parser.
- Position
- Below the diagonal: trash.trash_state uses a module listed above it, which is the healthy direction.
40→18 trash.trash_state uses tree.tree_options✕
- Connections
- 1 pair of types, where a type in trash.trash_state uses a type in tree.tree_options.
- The types involved
broot.trash.trash_state.TrashState→broot.tree.tree_options.TreeOptions
- Direction
- trash.trash_state uses tree.tree_options, so a change to tree.tree_options can break trash.trash_state, while a change to trash.trash_state can't break tree.tree_options.
- Position
- Below the diagonal: trash.trash_state uses a module listed above it, which is the healthy direction.
40→21 trash.trash_state uses app.app_context✕
- Connections
- 1 pair of types, where a type in trash.trash_state uses a type in app.app_context.
- The types involved
broot.trash.trash_state.TrashState→broot.app.app_context.AppContext
- Direction
- trash.trash_state uses app.app_context, so a change to app.app_context can break trash.trash_state, while a change to trash.trash_state can't break app.app_context.
- Position
- Below the diagonal: trash.trash_state uses a module listed above it, which is the healthy direction.
40→22 trash.trash_state uses command.command✕
- Connections
- 1 pair of types, where a type in trash.trash_state uses a type in command.command.
- The types involved
broot.trash.trash_state.TrashState→broot.command.command.Command
- Direction
- trash.trash_state uses command.command, so a change to command.command can break trash.trash_state, while a change to trash.trash_state can't break command.command.
- Position
- Below the diagonal: trash.trash_state uses a module listed above it, which is the healthy direction.
40→24 trash.trash_state uses display.screen✕
- Connections
- 1 pair of types, where a type in trash.trash_state uses a type in display.screen.
- The types involved
broot.trash.trash_state.TrashState→broot.display.screen.Screen
- Direction
- trash.trash_state uses display.screen, so a change to display.screen can break trash.trash_state, while a change to trash.trash_state can't break display.screen.
- Position
- Below the diagonal: trash.trash_state uses a module listed above it, which is the healthy direction.
40→27 trash.trash_state uses app.cmd_context✕
- Connections
- 1 pair of types, where a type in trash.trash_state uses a type in app.cmd_context.
- The types involved
broot.trash.trash_state.TrashState→broot.app.cmd_context.CmdContext
- Direction
- trash.trash_state uses app.cmd_context, so a change to app.cmd_context can break trash.trash_state, while a change to trash.trash_state can't break app.cmd_context.
- Position
- Below the diagonal: trash.trash_state uses a module listed above it, which is the healthy direction.
40→28 trash.trash_state uses app.display_context✕
- Connections
- 1 pair of types, where a type in trash.trash_state uses a type in app.display_context.
- The types involved
broot.trash.trash_state.TrashState→broot.app.display_context.DisplayContext
- Direction
- trash.trash_state uses app.display_context, so a change to app.display_context can break trash.trash_state, while a change to trash.trash_state can't break app.display_context.
- Position
- Below the diagonal: trash.trash_state uses a module listed above it, which is the healthy direction.
40→31 trash.trash_state uses app.panel_state✕
- Connections
- 1 pair of types, where a type in trash.trash_state uses a type in app.panel_state.
- The types involved
broot.trash.trash_state.TrashState→broot.app.panel_state.PanelState
- Direction
- trash.trash_state uses app.panel_state, so a change to app.panel_state can break trash.trash_state, while a change to trash.trash_state can't break app.panel_state.
- Position
- Below the diagonal: trash.trash_state uses a module listed above it, which is the healthy direction.
40→36 trash.trash_state uses filesystems.filesystems_state✕
- Connections
- 1 pair of types, where a type in trash.trash_state uses a type in filesystems.filesystems_state.
- The types involved
broot.trash.trash_state.TrashState→broot.filesystems.filesystems_state.FilteredContent
- Direction
- trash.trash_state uses filesystems.filesystems_state, so a change to filesystems.filesystems_state can break trash.trash_state, while a change to trash.trash_state can't break filesystems.filesystems_state.
- Position
- Below the diagonal: trash.trash_state 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
| A05:2025 — Injection | 2 | High / Critical |
Roadmap
First, resolve the missing Architectural Decision Records by documenting significant design choices in a dedicated folder to ensure architectural clarity. Next, address orphaned knowledge by updating the icon_name_to_icon_code_point_map.rs file and add a quick start section to the root README to help new contributors. Finally, tighten the public API by hiding internal implementation types to prevent breaking changes for library consumers.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +8.9 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. | +7.8 pts | Medium | Architecture documentation |
| Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with icon_name_to_icon_code_point_map.rs. | +3.0 pts | Low | Knowledge Freshness |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +2.9 pts | Medium | Documentation (README) |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +1.2 pts | Low | Project Cohesion |
| Resolve the 6 Boundary-crossing change coupling finding(s) in Change Coupling — start with browser_state.rs (3), image_view.rs (2), hex_view.rs. | +0.6 pts | Low | Change Coupling |
| Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers. | +1.7 pts | Medium | Library API & versioning |
| Resolve the 9 Hotspot finding(s) in Churn × Complexity Hotspots — start with panel_state.rs, browser_state.rs, verb_store.rs. | +1.3 pts | High | Churn × Complexity Hotspots |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| src/browser/browser_state.rs | 3.6 | Slop | Change Coupling: Boundary-crossing change coupling: browser_state.rs ↔ help_state.rs |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| src/hex/hex_view.rs | 5.4 | Mixed | Change Coupling: Boundary-crossing change coupling: hex_view.rs ↔ text_view.rs |
| src/image/image_view.rs | 5.5 | Mixed | Change Coupling: Boundary-crossing change coupling: image_view.rs ↔ mod.rs |
| src/app/app.rs | 5.5 | Mixed | Cyclomatic Complexity: App::apply_command (cyclomatic 70) |
| REDACTED | 5.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| src/app/panel_state.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/display/displayable_tree.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/filesystems/filesystems_state.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/preview/preview_state.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/app/standard_status.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/stage/stage_state.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/cli/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/git/ignore.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/app/app_panels.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/app/app_context.rs | 6.3 | Mixed | God Classes: TooManyFields: AppContext |
| src/pattern/search_mode.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/content_search/needle.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/trash/trash_state.rs | 7.0 | Mixed | Cyclomatic Complexity: TrashState::display (cyclomatic 27) |
| src/syntactic/text_view.rs | 7.0 | Mixed | Cyclomatic Complexity: TextView::display (cyclomatic 33) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 51 of 51 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 51 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 215 of 232 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.
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A hotspot's complexity is meant to be the worst body its churn actually touched. For src/skin/style_map.rs that could not be established — the complexity reader for the file reports no body extents, or the history carries no per-line attribution — so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (134 contributor(s) across 2159 commit(s) sampled, automation and bot accounts excluded). One of them holds 88% of the history; the other 133 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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.
- AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- 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 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 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, 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.
- X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust 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.
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.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
39 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PanelState::on_internal_generic at 118. A further 1 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 ExecutionBuilder::get_sel_standard_replacement at 19 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/verb/execution_builder.rs (ExecutionBuilder::get_sel_standard_replacement at 19). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 4 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with PanelState::on_internal_generic (cyclomatic 118), StyleMaps::create (cyclomatic 83), App::apply_command (cyclomatic 70). — 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 4 together lifts Cyclomatic Complexity from 5.4 to about 6.3/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
65 method(s) exceeded the cognitive complexity threshold of 15; the worst was PanelState::on_internal_generic at 124.
What to do
- Bring the 24 bodies over 30 down to 30 or less in Cognitive Complexity — start with PanelState::on_internal_generic (cognitive 124), TextView::display (cognitive 118), App::apply_command (cognitive 116). — 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 24 together lifts Cognitive Complexity from 3.6 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
35 god class(es) detected.
What to do
- Resolve the 12 MethodTooLong finding(s) in God Classes — start with app.rs (2), panel_state.rs, browser_state.rs. — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 11 ClassTooLong finding(s) in God Classes — start with panel_state.rs, browser_state.rs, verb_store.rs. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 7 FileTooLong finding(s) in God Classes — start with panel_state.rs, browser_state.rs, app_panels.rs. — One of this dimension's main actionable groups (7 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
16 duplicated block group(s) detected.
What to do
- Resolve the 4 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with composite_pattern.rs, text_view.rs, trash_state.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with needle.rs, scroll.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with pattern.rs, bline.rs. — One of this dimension's main actionable groups (2 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 85 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with verb.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
205 test methods: 198 unit, 7 integration, 0 BDD, 0 e2e. The Rust suite contributes 205 `#[test]` function(s) across 46 file(s) declaring at least one; its unit/integration split is Cargo's own — 1 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.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 46 test files): measured (0 flaky).
D12 · Dependency Hygiene
10 outdated, 0 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.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 497 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.
D15 · Churn × Complexity Hotspots
Top hotspots: src/app/panel_state.rs (8×118=944); src/browser/browser_state.rs (8×69=552); src/verb/verb_store.rs (17×27=459)
What to do
- Resolve the 9 Hotspot finding(s) in Churn × Complexity Hotspots — start with panel_state.rs, browser_state.rs, verb_store.rs. — One of this dimension's main actionable groups (9 warning-level).
D17 · Explicit Debt
26 deducted task-comment markers across 38678 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 20 TodoComment finding(s) in Explicit Debt — start with standard_status.rs (5), app_panels.rs (2), stage_state.rs. — One of this dimension's main actionable groups (20 warning-level).
- Resolve the 6 FixmeComment finding(s) in Explicit Debt — start with app_panels.rs (3), preview.rs, help_state.rs. — One of this dimension's main actionable groups (6 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. 7 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 1 build units (Cargo) 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)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `build-scripts/_common.sh` (line 30, line 181), `src/syntactic/text_view.rs` (line 736) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
5 finding(s): 0 critical, 0 high, 5 medium, 0 low.
What to do
- Resolve the 3 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
1 of 123 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is resources/icons/vscode/data/icon_name_to_icon_code_point_map.rs. Counted over 123 of the 236 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 Orphaned knowledge finding(s) in Knowledge Freshness — start with icon_name_to_icon_code_point_map.rs. — One of this dimension's main actionable groups (1 issue-level).
D35 · Change Coupling
Strongest change-coupling: standard_status.rs↔browser_state.rs 73%; browser_state.rs↔help_state.rs 69%; image_view.rs↔mod.rs 67%
What to do
- Resolve the 6 Boundary-crossing change coupling finding(s) in Change Coupling — start with browser_state.rs (3), image_view.rs (2), hex_view.rs. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 4 Change coupling finding(s) in Change Coupling — start with standard_status.rs, app.rs, panel.rs. — One of this dimension's main actionable groups (4 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 1 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
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- 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
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- 204/240 types (85%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers.
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add cargo-audit / cargo-deny (or clippy) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 618 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
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
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 85% | Adequate — gated by D2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 85% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 57% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 59% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 98% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 63 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC7 A11y enforcement — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- 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 — Not applicable: 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 — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — 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 — ~657 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.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Rust 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 .rs, 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) — 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.
- 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 — not scored — this repository shows only 1 of the 3 signals this lens looks for (6 value object(s))
- 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
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, 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
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not 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.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 236 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.
- X17 Uncapped recursion over a caller-supplied document — 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
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — 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.
- X24 Document value interpolated into markup unescaped — 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
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X3 Exception handling — 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
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 9 finding(s)
- Boundary-crossing change coupling: browser_state.rs ↔ help_state.rs src/browser/browser_state.rs:1
- Boundary-crossing change coupling: image_view.rs ↔ mod.rs src/image/image_view.rs:1
- Boundary-crossing change coupling: hex_view.rs ↔ text_view.rs src/hex/hex_view.rs:1
- Boundary-crossing change coupling: browser_state.rs ↔ help_verbs.rs src/browser/browser_state.rs:1
- Boundary-crossing change coupling: image_view.rs ↔ image_renderer.rs src/image/image_view.rs:1
- Boundary-crossing change coupling: browser_state.rs ↔ sequence.rs src/browser/browser_state.rs:1
- REDACTED
- REDACTED
- Orphaned knowledge resources/icons/vscode/data/icon_name_to_icon_code_point_map.rs:1
Serious — 201 finding(s)
- TodoComment src/stage/stage_state.rs:347
- TodoComment src/preview/preview_state.rs:330
- TodoComment src/filesystems/filesystems_state.rs:182
- TodoComment src/pattern/content_regex_pattern.rs:55
- TodoComment src/pattern/search_mode.rs:194
- TodoComment src/help/help_state.rs:97
- TodoComment src/git/ignore.rs:3
- TodoComment src/display/displayable_tree.rs:282
- TodoComment src/content_type/magic_numbers.rs:76
- TodoComment src/content_search/needle.rs:238
- TodoComment src/cli/mod.rs:126
- TodoComment src/app/app_panels.rs:275
- TodoComment src/app/app_panels.rs:279
- TodoComment src/app/cmd_result.rs:72
- TodoComment src/app/panel_state.rs:771
- TodoComment src/app/standard_status.rs:13
- TodoComment src/app/standard_status.rs:47
- TodoComment src/app/standard_status.rs:247
- TodoComment src/app/standard_status.rs:250
- TodoComment src/app/standard_status.rs:253
- MethodTooLong: PanelState.on_internal_generic src/app/panel_state.rs:110
- MethodTooLong: BrowserState.on_internal src/browser/browser_state.rs:336
- MethodTooLong: VerbStore.add_builtin_verbs src/verb/verb_store.rs:85
- MethodTooLong: FilesystemState.display src/filesystems/filesystems_state.rs:241
- MethodTooLong: App.apply_command src/app/app.rs:113
- MethodTooLong: TextView.display src/syntactic/text_view.rs:504
- MethodTooLong: DisplayableTree.write_on src/display/displayable_tree.rs:480
- MethodTooLong: TrashState.display src/trash/trash_state.rs:338
- MethodTooLong: App.run src/app/app.rs:449
- MethodTooLong: AppContext.from src/app/app_context.rs:182
- MethodTooLong: UnifiedDiffView.display src/preview/unified_diff_view.rs:284
- MethodTooLong: DirSummer.compute_dir_sum src/file_sum/sum_computation.rs:66
- ClassTooLong: PanelState src/app/panel_state.rs:29
- ClassTooLong: BrowserState src/browser/browser_state.rs:27
- ClassTooLong: VerbStore src/verb/verb_store.rs:33
- ClassTooLong: AppPanelsAndInputs src/app/app_panels.rs:33
- ClassTooLong: FilesystemState src/filesystems/filesystems_state.rs:44
- ClassTooLong: DisplayableTree src/display/displayable_tree.rs:59
- ClassTooLong: TrashState src/trash/trash_state.rs:43
- ClassTooLong: Tree src/tree/tree.rs:33
- ClassTooLong: TextView src/syntactic/text_view.rs:109
- ClassTooLong: App src/app/app.rs:52
- ClassTooLong: PreviewState src/preview/preview_state.rs:47
- Hotspot: src/app/panel_state.rs src/app/panel_state.rs:110
- Hotspot: src/browser/browser_state.rs src/browser/browser_state.rs:336
- Hotspot: src/verb/verb_store.rs src/verb/verb_store.rs:459
- Hotspot: src/skin/style_map.rs src/skin/style_map.rs:72
- Hotspot: src/preview/preview_state.rs src/preview/preview_state.rs:435
- Hotspot: src/verb/execution_builder.rs src/verb/execution_builder.rs:109
- Hotspot: src/app/app.rs src/app/app.rs:449
- Hotspot: src/cli/mod.rs src/cli/mod.rs:73
- Hotspot: src/launchable.rs src/launchable.rs:180
- FileTooLong: app/panel_state.rs src/app/panel_state.rs
- FileTooLong: browser/browser_state.rs src/browser/browser_state.rs
- FileTooLong: app/app_panels.rs src/app/app_panels.rs
- FileTooLong: syntactic/text_view.rs src/syntactic/text_view.rs
- FileTooLong: verb/verb_store.rs src/verb/verb_store.rs
- FileTooLong: filesystems/filesystems_state.rs src/filesystems/filesystems_state.rs
- FileTooLong: display/displayable_tree.rs src/display/displayable_tree.rs
- FixmeComment src/preview/preview.rs:227
- FixmeComment src/help/help_state.rs:249
- FixmeComment src/app/app_panels.rs:319
- FixmeComment src/app/app_panels.rs:553
- FixmeComment src/app/app_panels.rs:579
- FixmeComment src/app/panel_state.rs:1075
- broot::kitty::detect_support::detect_kitty_graphics_protocol_display (cognitive 30) src/kitty/detect_support.rs:74
- broot::git::diff::hunks (cognitive 25) src/git/diff.rs:168
- broot::cli::run (cognitive 24) src/cli/mod.rs:73
- broot::help::help_verbs::matching_verb_rows (cognitive 22) src/help/help_verbs.rs:48
- broot::launchable::resolve_env_variables (cognitive 18) src/launchable.rs:81
- broot::verb::internal_focus::on_internal (cognitive 17) src/verb/internal_focus.rs:183
- TrashState::display (cognitive 77) src/trash/trash_state.rs:338
- TrashState::on_internal (cognitive 23) src/trash/trash_state.rs:508
- TrashState::move_line (cognitive 22) src/trash/trash_state.rs:150
- TrashState::on_pattern (cognitive 19) src/trash/trash_state.rs:295
- TrashState::take_selected_item (cognitive 16) src/trash/trash_state.rs:206
- DisplayableTree::write_on (cognitive 74) src/display/displayable_tree.rs:480
- DisplayableTree::write_line_label (cognitive 25) src/display/displayable_tree.rs:318
- DisplayableTree::write_branch (cognitive 21) src/display/displayable_tree.rs:269
- DisplayableTree::write_root_line (cognitive 19) src/display/displayable_tree.rs:414
- DisplayableTree::label_style (cognitive 17) src/display/displayable_tree.rs:94
- TooManyFields: StyleMap src/skin/style_map.rs:42
- TooManyFields: Args src/cli/args.rs:17
- TooManyFields: AppContext src/app/app_context.rs:49
- TooManyFields: Conf src/conf/conf.rs:60
- Change coupling: standard_status.rs ↔ browser_state.rs src/app/standard_status.rs:1
- Change coupling: app.rs ↔ panel.rs src/app/app.rs:1
- Change coupling: panel.rs ↔ browser_state.rs src/app/panel.rs:1
- Change coupling: app_context.rs ↔ col.rs src/app/app_context.rs:1
- Duplicated block (10 lines × 2) src/pattern/composite_pattern.rs:233
- Duplicated block (10 lines × 2) src/syntactic/text_view.rs:450
- Duplicated block (10 lines × 2) src/trash/trash_state.rs:381
- Duplicated block (10 lines × 2) src/verb/internal_path.rs:127
- TreeBuilder::gather_lines (cognitive 67) src/tree_build/builder.rs:313
- TreeBuilder::make_bline (cognitive 30) src/tree_build/builder.rs:137
- TreeBuilder::load_children (cognitive 19) src/tree_build/builder.rs:243
- REDACTED
- REDACTED
- REDACTED
- App::apply_command (cyclomatic 70) src/app/app.rs:113
- App::run (cyclomatic 24) src/app/app.rs:449
- FilesystemState::display (cyclomatic 36) src/filesystems/filesystems_state.rs:241
- FilesystemState::on_internal (cyclomatic 22) src/filesystems/filesystems_state.rs:545
- TextView::display (cyclomatic 33) src/syntactic/text_view.rs:504
- TextView::read_lines (cyclomatic 22) src/syntactic/text_view.rs:237
- TrashState::display (cyclomatic 27) src/trash/trash_state.rs:338
- TrashState::on_internal (cyclomatic 23) src/trash/trash_state.rs:508
- TreeBuilder::gather_lines (cyclomatic 27) src/tree_build/builder.rs:313
- TreeBuilder::make_bline (cyclomatic 21) src/tree_build/builder.rs:137
- VerbStore::add_from_conf (cyclomatic 27) src/verb/verb_store.rs:459
- VerbStore::search (cyclomatic 19) src/verb/verb_store.rs:641
- PanelInput::on_key (cyclomatic 23) src/command/panel_input.rs:428
- PanelInput::handle_input_related_internal (cyclomatic 21) src/command/panel_input.rs:154
- StageState::display (cyclomatic 22) src/stage/stage_state.rs:265
- StageState::on_internal (cyclomatic 19) src/stage/stage_state.rs:409
- broot::cli::run (cyclomatic 20) src/cli/mod.rs:73
- broot::kitty::detect_support::detect_kitty_graphics_protocol_display (cyclomatic 17) src/kitty/detect_support.rs:74
- PanelState::on_internal_generic (cognitive 124) src/app/panel_state.rs:110
- PanelState::get_status (cognitive 21) src/app/panel_state.rs:1143
- TextView::display (cognitive 118) src/syntactic/text_view.rs:504
- TextView::read_lines (cognitive 49) src/syntactic/text_view.rs:237
- App::apply_command (cognitive 116) src/app/app.rs:113
- App::run (cognitive 45) src/app/app.rs:449
- FilesystemState::display (cognitive 88) src/filesystems/filesystems_state.rs:241
- FilesystemState::on_internal (cognitive 19) src/filesystems/filesystems_state.rs:545
- StageState::display (cognitive 83) src/stage/stage_state.rs:265
- StageState::on_internal (cognitive 20) src/stage/stage_state.rs:409
- Tree::after_lines_changed (cognitive 56) src/tree/tree.rs:75
- Tree::move_selection (cognitive 21) src/tree/tree.rs:210
- VerbStore::search (cognitive 38) src/verb/verb_store.rs:641
- VerbStore::add_from_conf (cognitive 31) src/verb/verb_store.rs:459
- FilteredStage::compute (cognitive 21) src/stage/filtered_stage.rs:26
- FilteredStage::move_selection (cognitive 18) src/stage/filtered_stage.rs:175
- Ignorer::root_chain (cognitive 20) src/git/ignore.rs:232
- Ignorer::accepts (cognitive 17) src/git/ignore.rs:310
- Duplicated block (8 lines × 2) src/content_search/needle.rs:102
- Duplicated block (8 lines × 2) src/command/scroll.rs:37
- Duplicated block (5 lines × 2) src/pattern/pattern.rs:100
- Duplicated block (5 lines × 2) src/tree_build/bline.rs:82
- PanelState::on_internal_generic (cyclomatic 118) src/app/panel_state.rs:110
- StyleMaps::create (cyclomatic 83) src/skin/style_map.rs:72
- BrowserState::on_internal (cyclomatic 69) src/browser/browser_state.rs:336
- DisplayableTree::write_on (cyclomatic 36) src/display/displayable_tree.rs:480
- HexView::display (cyclomatic 32) src/hex/hex_view.rs:107
- TreeOptions::apply_launch_args (cyclomatic 31) src/tree/tree_options.rs:136
- PreviewState::on_internal (cyclomatic 30) src/preview/preview_state.rs:435
- DirSummer::compute_dir_sum (cyclomatic 29) src/file_sum/sum_computation.rs:66
- UnifiedDiffView::display (cyclomatic 25) src/preview/unified_diff_view.rs:284
- CommandParts::from (cyclomatic 24) src/command/parts.rs:37
- Areas::compute_areas (cyclomatic 24) src/display/areas.rs:87
- Tree::after_lines_changed (cyclomatic 24) src/tree/tree.rs:75
- StandardStatusBuilder::status (cyclomatic 23) src/app/standard_status.rs:187
- MountSpaceDisplay::write (cyclomatic 19) src/filesystems/mount_space_display.rs:40
- FuzzyPattern::tight_match_from_index (cyclomatic 19) src/pattern/fuzzy_pattern.rs:90
- SearchModeMapEntry::parse (cyclomatic 17) src/pattern/search_mode.rs:136
- PermWriter::write_mode (cyclomatic 16) src/display/permissions.rs:47
- SourceImage::fitting (cyclomatic 16) src/image/source_image.rs:75
- Launchable::execute (cyclomatic 16) src/launchable.rs:180
- Server::new (cyclomatic 16) src/net/server.rs:54
- VerbInvocation::from (cyclomatic 16) src/verb/verb_invocation.rs:97
- DirSummer::compute_dir_sum (cognitive 102) src/file_sum/sum_computation.rs:66
- Areas::compute_areas (cognitive 84) src/display/areas.rs:87
- StyleMaps::create (cognitive 82) src/skin/style_map.rs:72
- UnifiedDiffView::display (cognitive 73) src/preview/unified_diff_view.rs:284
- HexView::display (cognitive 70) src/hex/hex_view.rs:107
- BrowserState::on_internal (cognitive 69) src/browser/browser_state.rs:336
- FuzzyPattern::tight_match_from_index (cognitive 50) src/pattern/fuzzy_pattern.rs:90
- MountSpaceDisplay::write (cognitive 37) src/filesystems/mount_space_display.rs:40
- Launchable::execute (cognitive 37) src/launchable.rs:180
- PermWriter::write_mode (cognitive 36) src/display/permissions.rs:47
- StandardStatusBuilder::status (cognitive 32) src/app/standard_status.rs:187
- PanelInput::on_key (cognitive 29) src/command/panel_input.rs:428
- TreeOptions::apply_launch_args (cognitive 29) src/tree/tree_options.rs:136
- VerbInvocation::from (cognitive 29) src/verb/verb_invocation.rs:97
- KittyImage::print_with_chunks (cognitive 28) src/kitty/image_renderer.rs:257
- BLine::can_enter (cognitive 28) src/tree_build/bline.rs:95
- Server::new (cognitive 27) src/net/server.rs:54
- CommandParts::from (cognitive 26) src/command/parts.rs:37
- TLine::draw_range_in (cognitive 26) src/tty/tline.rs:154
- MatchedString::queue_on (cognitive 24) src/display/matched_string.rs:116
- SourceImage::fitting (cognitive 24) src/image/source_image.rs:75
- TtyView::display (cognitive 21) src/tty/tty_view.rs:133
- ExecutionBuilder::expand_tokens (cognitive 21) src/verb/execution_builder.rs:394
- Completions::list_for_path (cognitive 18) src/command/completion.rs:112
- ImageView::display (cognitive 17) src/image/image_view.rs:92
- ExternalExecution::cmd_result_exec_stay_in_broot (cognitive 17) src/verb/external_execution.rs:217
- AppPanelsAndInputs::draw_panels_once (cognitive 16) src/app/app_panels.rs:730
- IgnoreRule::from (cognitive 16) src/git/ignore.rs:72
- TooManyMethods: AppPanelsAndInputs src/app/app_panels.rs:33
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (25 lines × 2) src/verb/internal_focus.rs:112
- Duplicated block (23 lines × 2) src/filesystems/filesystems_state.rs:246
- Duplicated block (16 lines × 2) src/pattern/composite_pattern.rs:46
- Duplicated block (13–14 lines × 2) src/pattern/composite_pattern.rs:127
- Duplicated block (14 lines × 2) src/trash/trash_state.rs:377
- Duplicated block (9–11 lines × 2) src/shell_install/nushell.rs:245
- Duplicated block (6 lines × 2) src/preview/unified_diff_view.rs:308
- Duplicated block (8 lines × 3) src/hex/hex_view.rs:247
- Low cohesion: Verb (LCOM4 6) src/verb/verb.rs:33
Minor — 12 finding(s)
- Duplicated predicate src/browser/browser_state.rs:446
- Duplicated predicate src/browser/browser_state.rs:465
- Duplicated predicate src/net/message.rs:27
- Silent fallback default on Err src/verb/execution_builder.rs:219
- Silent fallback default on Err src/kitty/detect_support.rs:60
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- No ADRs
- No architecture diagram/doc
- Large public API surface
- No SAST
Minor — 10 finding(s)
- Outdated: crokey
- Outdated: image
- Outdated: interprocess
- Outdated: lazy-regex
- Outdated: lfs-core
- Outdated: libc
- Outdated: memmap2
- Outdated: notify
- Outdated: smallvec
- Outdated: toml
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-da60bcc92c5e4cb59355bc10d41baff3/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-da60bcc92c5e4cb59355bc10d41baff3/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 2 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 5 | artifacts/raw/osv-scanner.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. | 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |