Executive summary
hmdfrds/godot-vim meets our standard for production. It scores 78.6 out of 100 and is rated Strong, and its one critical finding is a security problem in its automatic dependency updates.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step for the work it takes is adding tests for untested code, worth about 3.0 points. Keeping a changelog comes next, worth about 3.4 points.
One automatic update takes new releases before a bad one can be spotted. Setting a waiting period for automatic updates would close this risk.
The product code is 65,009 lines, about €110,000 to rebuild.
Every lens already scores high enough to be rated Strong, so no single lens holds the score back.
Rebuild cost: about €110,000 · Estimate
| Cost to rebuild | €37,000 to €190,000, for 619 to 1,965 hours of work, about 0.8 person-years for 1 to 2 engineers |
|---|---|
| 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 | ×1.3 at a score of 79. 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: 65,009 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 actions.caps | 2 actions.keys | 3 actions.outcome | 4 config.path | 5 effects.compound | 6 navigation.dock_nav | 7 navigation.filesystem_explorer | 8 plugin.caret_reconcile | 9 settings.snapshot | 10 types | 11 actions.surface | 12 bridge.codec | 13 bridge.context | 14 config.panelmap | 15 config.source | 16 host.dispatch | 17 state.buffer | 18 state.globals | 19 ui.coordinator | 20 actions.bind | 21 config.types | 22 plugin.source_cmd | 23 state.shell | 24 actions.action | 25 bridge.godot_host | 26 actions.providers.debugger | 27 actions.resolve | 28 actions.specs | 29 bridge.port_impl | 30 config.policy | 31 actions.introspect | 32 actions.sequence | 33 controller.completion | 34 controller.pipeline_outcome | 35 effects.dispatch | 36 controller | 37 plugin.outcome | 38 controller.process | 39 plugin.input | 40 plugin |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 actions.caps | ||||||||||||||||||||||||||||||||||||||||
| 2 actions.keys | ||||||||||||||||||||||||||||||||||||||||
| 3 actions.outcome | ||||||||||||||||||||||||||||||||||||||||
| 4 config.path | ||||||||||||||||||||||||||||||||||||||||
| 5 effects.compound | ||||||||||||||||||||||||||||||||||||||||
| 6 navigation.dock_nav | ||||||||||||||||||||||||||||||||||||||||
| 7 navigation.filesystem_explorer | ||||||||||||||||||||||||||||||||||||||||
| 8 plugin.caret_reconcile | ||||||||||||||||||||||||||||||||||||||||
| 9 settings.snapshot | ||||||||||||||||||||||||||||||||||||||||
| 10 types | ||||||||||||||||||||||||||||||||||||||||
| 11 actions.surface | 3 | |||||||||||||||||||||||||||||||||||||||
| 12 bridge.codec | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 bridge.context | 2 | |||||||||||||||||||||||||||||||||||||||
| 14 config.panelmap | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 config.source | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 host.dispatch | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 state.buffer | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 state.globals | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 ui.coordinator | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 20 actions.bind | 2 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 21 config.types | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 plugin.source_cmd | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 state.shell | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 actions.action | 2 | 1 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 25 bridge.godot_host | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 actions.providers.debugger | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 actions.resolve | 1 | 1 | 2 | 4 | 3 | |||||||||||||||||||||||||||||||||||
| 28 actions.specs | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 29 bridge.port_impl | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 config.policy | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 actions.introspect | 1 | 2 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 32 actions.sequence | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 33 controller.completion | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 34 controller.pipeline_outcome | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 effects.dispatch | 1 | 3 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 36 controller | 2 | 2 | 2 | 1 | 1 | 3 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||
| 37 plugin.outcome | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 38 controller.process | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 39 plugin.input | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 40 plugin | 1 | 1 | 1 | 1 | 3 | 1 | 1 | 1 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 |
11→1 actions.surface uses actions.caps✕
- Connections
- 3 pairs of types, where a type in actions.surface uses a type in actions.caps.
- The types involved
godot_vim.actions.surface.ChainNode→godot_vim.actions.caps.Capsgodot_vim.actions.surface.FocusChain→godot_vim.actions.caps.Capsgodot_vim.actions.surface.SurfacePath→godot_vim.actions.caps.Caps
- Direction
- actions.surface uses actions.caps, so a change to actions.caps can break actions.surface, while a change to actions.surface can't break actions.caps.
- Position
- Below the diagonal: actions.surface uses a module listed above it, which is the healthy direction.
12→10 bridge.codec uses types✕
- Connections
- 2 pairs of types, where a type in bridge.codec uses a type in types.
- The types involved
godot_vim.bridge.codec.LineIndex→godot_vim.types.CharLineColgodot_vim.bridge.codec.LineIndex→godot_vim.types.GraphemeLineCol
- Direction
- bridge.codec uses types, so a change to types can break bridge.codec, while a change to bridge.codec can't break types.
- Position
- Below the diagonal: bridge.codec uses a module listed above it, which is the healthy direction.
13→5 bridge.context uses effects.compound✕
- Connections
- 2 pairs of types, where a type in bridge.context uses a type in effects.compound.
- The types involved
godot_vim.bridge.context.OwnedGodotFoldProvider→godot_vim.effects.compound.LineNumbergodot_vim.bridge.context.OwnedGodotIndentProvider→godot_vim.effects.compound.LineNumber
- Direction
- bridge.context uses effects.compound, so a change to effects.compound can break bridge.context, while a change to bridge.context can't break effects.compound.
- Position
- Below the diagonal: bridge.context uses a module listed above it, which is the healthy direction.
14→24 config.panelmap uses actions.action part of a loop✕
- Connections
- 1 pair of types, where a type in config.panelmap uses a type in actions.action.
- The types involved
godot_vim.config.panelmap.PanelMap→godot_vim.actions.action.Params
- Direction
- config.panelmap uses actions.action, so a change to actions.action can break config.panelmap, while a change to config.panelmap can't break actions.action.
- 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→4 config.source uses config.path✕
- Connections
- 1 pair of types, where a type in config.source uses a type in config.path.
- The types involved
godot_vim.config.source.SourceEnv→godot_vim.config.path.ResolvedConfig
- Direction
- config.source uses config.path, so a change to config.path can break config.source, while a change to config.source can't break config.path.
- Position
- Below the diagonal: config.source uses a module listed above it, which is the healthy direction.
15→10 config.source uses types✕
- Connections
- 1 pair of types, where a type in config.source uses a type in types.
- The types involved
godot_vim.config.source.source$module→godot_vim.types.StatusMessage
- Direction
- config.source uses types, so a change to types can break config.source, while a change to config.source can't break types.
- Position
- Below the diagonal: config.source uses a module listed above it, which is the healthy direction.
16→9 host.dispatch uses settings.snapshot✕
- Connections
- 2 pairs of types, where a type in host.dispatch uses a type in settings.snapshot.
- The types involved
godot_vim.host.dispatch.SecurityPolicy→godot_vim.settings.snapshot.FileAccessScopegodot_vim.host.dispatch.SecurityPolicy→godot_vim.settings.snapshot.ShellExecution
- Direction
- host.dispatch uses settings.snapshot, so a change to settings.snapshot can break host.dispatch, while a change to host.dispatch can't break settings.snapshot.
- Position
- Below the diagonal: host.dispatch uses a module listed above it, which is the healthy direction.
16→25 host.dispatch uses bridge.godot_host part of a loop✕
- Connections
- 1 pair of types, where a type in host.dispatch uses a type in bridge.godot_host.
- The types involved
godot_vim.host.dispatch.dispatch$module→godot_vim.bridge.godot_host.PendingUiAction
- Direction
- host.dispatch uses bridge.godot_host, so a change to bridge.godot_host can break host.dispatch, while a change to host.dispatch can't break bridge.godot_host.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→10 state.buffer uses types✕
- Connections
- 2 pairs of types, where a type in state.buffer uses a type in types.
- The types involved
godot_vim.state.buffer.BufferState→godot_vim.types.CharLineColgodot_vim.state.buffer.VisualSelectionState→godot_vim.types.CharLineCol
- Direction
- state.buffer uses types, so a change to types can break state.buffer, while a change to state.buffer can't break types.
- Position
- Below the diagonal: state.buffer uses a module listed above it, which is the healthy direction.
18→10 state.globals uses types✕
- Connections
- 1 pair of types, where a type in state.globals uses a type in types.
- The types involved
godot_vim.state.globals.GlobalState→godot_vim.types.StatusMessage
- Direction
- state.globals uses types, so a change to types can break state.globals, while a change to state.globals can't break types.
- Position
- Below the diagonal: state.globals uses a module listed above it, which is the healthy direction.
19→9 ui.coordinator uses settings.snapshot✕
- Connections
- 1 pair of types, where a type in ui.coordinator uses a type in settings.snapshot.
- The types involved
godot_vim.ui.coordinator.UiCoordinator→godot_vim.settings.snapshot.SettingsSnapshot
- Direction
- ui.coordinator uses settings.snapshot, so a change to settings.snapshot can break ui.coordinator, while a change to ui.coordinator can't break settings.snapshot.
- Position
- Below the diagonal: ui.coordinator uses a module listed above it, which is the healthy direction.
19→10 ui.coordinator uses types✕
- Connections
- 3 pairs of types, where a type in ui.coordinator uses a type in types.
- The types involved
godot_vim.ui.coordinator.DirtyCache→godot_vim.types.CharLineColgodot_vim.ui.coordinator.DirtyCache→godot_vim.types.StatusMessagegodot_vim.ui.coordinator.UiCoordinator→godot_vim.types.UiSnapshot
- Direction
- ui.coordinator uses types, so a change to types can break ui.coordinator, while a change to ui.coordinator can't break types.
- Position
- Below the diagonal: ui.coordinator uses a module listed above it, which is the healthy direction.
20→11 actions.bind uses actions.surface✕
- Connections
- 2 pairs of types, where a type in actions.bind uses a type in actions.surface.
- The types involved
godot_vim.actions.bind.BindingIndex→godot_vim.actions.surface.Forestgodot_vim.actions.bind.bind$module→godot_vim.actions.surface.Forest
- Direction
- actions.bind uses actions.surface, so a change to actions.surface can break actions.bind, while a change to actions.bind can't break actions.surface.
- Position
- Below the diagonal: actions.bind uses a module listed above it, which is the healthy direction.
20→14 actions.bind uses config.panelmap✕
- Connections
- 1 pair of types, where a type in actions.bind uses a type in config.panelmap.
- The types involved
godot_vim.actions.bind.bind$module→godot_vim.config.panelmap.PanelMap
- Direction
- actions.bind uses config.panelmap, so a change to config.panelmap can break actions.bind, while a change to actions.bind can't break config.panelmap.
- Position
- Below the diagonal: actions.bind uses a module listed above it, which is the healthy direction.
20→24 actions.bind uses actions.action part of a loop✕
- Connections
- 4 pairs of types, where a type in actions.bind uses a type in actions.action.
- The types involved
godot_vim.actions.bind.BindingIndex→godot_vim.actions.action.ActionIdgodot_vim.actions.bind.Rule→godot_vim.actions.action.Paramsgodot_vim.actions.bind.Rule→godot_vim.actions.action.RuleTargetgodot_vim.actions.bind.bind$module→godot_vim.actions.action.ActionRegistry
- Direction
- actions.bind uses actions.action, so a change to actions.action can break actions.bind, while a change to actions.bind can't break actions.action.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→14 config.types uses config.panelmap✕
- Connections
- 1 pair of types, where a type in config.types uses a type in config.panelmap.
- The types involved
godot_vim.config.types.PanelPayload→godot_vim.config.panelmap.PanelLine
- Direction
- config.types uses config.panelmap, so a change to config.panelmap can break config.types, while a change to config.types can't break config.panelmap.
- Position
- Below the diagonal: config.types uses a module listed above it, which is the healthy direction.
22→4 plugin.source_cmd uses config.path✕
- Connections
- 1 pair of types, where a type in plugin.source_cmd uses a type in config.path.
- The types involved
godot_vim.plugin.source_cmd.source_cmd$module→godot_vim.config.path.ResolvedConfig
- Direction
- plugin.source_cmd uses config.path, so a change to config.path can break plugin.source_cmd, while a change to plugin.source_cmd can't break config.path.
- Position
- Below the diagonal: plugin.source_cmd uses a module listed above it, which is the healthy direction.
22→15 plugin.source_cmd uses config.source✕
- Connections
- 1 pair of types, where a type in plugin.source_cmd uses a type in config.source.
- The types involved
godot_vim.plugin.source_cmd.source_cmd$module→godot_vim.config.source.SourceEnv
- Direction
- plugin.source_cmd uses config.source, so a change to config.source can break plugin.source_cmd, while a change to plugin.source_cmd can't break config.source.
- Position
- Below the diagonal: plugin.source_cmd uses a module listed above it, which is the healthy direction.
23→10 state.shell uses types✕
- Connections
- 2 pairs of types, where a type in state.shell uses a type in types.
- The types involved
godot_vim.state.shell.ShellState→godot_vim.types.HighlightYankgodot_vim.state.shell.ShellState→godot_vim.types.MatchRange
- Direction
- state.shell uses types, so a change to types can break state.shell, while a change to state.shell can't break types.
- Position
- Below the diagonal: state.shell uses a module listed above it, which is the healthy direction.
23→17 state.shell uses state.buffer✕
- Connections
- 1 pair of types, where a type in state.shell uses a type in state.buffer.
- The types involved
godot_vim.state.shell.ShellState→godot_vim.state.buffer.BufferState
- Direction
- state.shell uses state.buffer, so a change to state.buffer can break state.shell, while a change to state.shell can't break state.buffer.
- Position
- Below the diagonal: state.shell uses a module listed above it, which is the healthy direction.
23→18 state.shell uses state.globals✕
- Connections
- 1 pair of types, where a type in state.shell uses a type in state.globals.
- The types involved
godot_vim.state.shell.ShellState→godot_vim.state.globals.GlobalState
- Direction
- state.shell uses state.globals, so a change to state.globals can break state.shell, while a change to state.shell can't break state.globals.
- Position
- Below the diagonal: state.shell uses a module listed above it, which is the healthy direction.
24→1 actions.action uses actions.caps✕
- Connections
- 2 pairs of types, where a type in actions.action uses a type in actions.caps.
- The types involved
godot_vim.actions.action.ActionRegistry→godot_vim.actions.caps.Capsgodot_vim.actions.action.ActionSpec→godot_vim.actions.caps.Caps
- Direction
- actions.action uses actions.caps, so a change to actions.caps can break actions.action, while a change to actions.action can't break actions.caps.
- Position
- Below the diagonal: actions.action uses a module listed above it, which is the healthy direction.
24→3 actions.action uses actions.outcome✕
- Connections
- 1 pair of types, where a type in actions.action uses a type in actions.outcome.
- The types involved
godot_vim.actions.action.ActionRegistry→godot_vim.actions.outcome.Outcome
- Direction
- actions.action uses actions.outcome, so a change to actions.outcome can break actions.action, while a change to actions.action can't break actions.outcome.
- Position
- Below the diagonal: actions.action uses a module listed above it, which is the healthy direction.
24→5 actions.action uses effects.compound✕
- Connections
- 1 pair of types, where a type in actions.action uses a type in effects.compound.
- The types involved
godot_vim.actions.action.PanelOps→godot_vim.effects.compound.WindowNavAction
- Direction
- actions.action uses effects.compound, so a change to effects.compound can break actions.action, while a change to actions.action can't break effects.compound.
- Position
- Below the diagonal: actions.action uses a module listed above it, which is the healthy direction.
24→6 actions.action uses navigation.dock_nav✕
- Connections
- 2 pairs of types, where a type in actions.action uses a type in navigation.dock_nav.
- The types involved
godot_vim.actions.action.PanelOps→godot_vim.navigation.dock_nav.HierarchyActiongodot_vim.actions.action.PanelOps→godot_vim.navigation.dock_nav.NavDirection
- Direction
- actions.action uses navigation.dock_nav, so a change to navigation.dock_nav can break actions.action, while a change to actions.action can't break navigation.dock_nav.
- Position
- Below the diagonal: actions.action uses a module listed above it, which is the healthy direction.
24→7 actions.action uses navigation.filesystem_explorer✕
- Connections
- 1 pair of types, where a type in actions.action uses a type in navigation.filesystem_explorer.
- The types involved
godot_vim.actions.action.ActionCtx→godot_vim.navigation.filesystem_explorer.FileSystemExplorer
- Direction
- actions.action uses navigation.filesystem_explorer, so a change to navigation.filesystem_explorer can break actions.action, while a change to actions.action can't break navigation.filesystem_explorer.
- Position
- Below the diagonal: actions.action uses a module listed above it, which is the healthy direction.
24→20 actions.action uses actions.bind✕
- Connections
- 1 pair of types, where a type in actions.action uses a type in actions.bind.
- The types involved
godot_vim.actions.action.ActionSpec→godot_vim.actions.bind.Consumption
- Direction
- actions.action uses actions.bind, so a change to actions.bind can break actions.action, while a change to actions.action can't break actions.bind.
- Position
- Below the diagonal: actions.action uses a module listed above it, which is the healthy direction.
25→12 bridge.godot_host uses bridge.codec✕
- Connections
- 1 pair of types, where a type in bridge.godot_host uses a type in bridge.codec.
- The types involved
godot_vim.bridge.godot_host.GodotHost→godot_vim.bridge.codec.LineIndex
- Direction
- bridge.godot_host uses bridge.codec, so a change to bridge.codec can break bridge.godot_host, while a change to bridge.godot_host can't break bridge.codec.
- Position
- Below the diagonal: bridge.godot_host uses a module listed above it, which is the healthy direction.
25→13 bridge.godot_host uses bridge.context✕
- Connections
- 2 pairs of types, where a type in bridge.godot_host uses a type in bridge.context.
- The types involved
godot_vim.bridge.godot_host.GodotHost→godot_vim.bridge.context.OwnedGodotFoldProvidergodot_vim.bridge.godot_host.GodotHost→godot_vim.bridge.context.OwnedGodotIndentProvider
- Direction
- bridge.godot_host uses bridge.context, so a change to bridge.context can break bridge.godot_host, while a change to bridge.godot_host can't break bridge.context.
- Position
- Below the diagonal: bridge.godot_host uses a module listed above it, which is the healthy direction.
25→16 bridge.godot_host uses host.dispatch✕
- Connections
- 1 pair of types, where a type in bridge.godot_host uses a type in host.dispatch.
- The types involved
godot_vim.bridge.godot_host.GodotHost→godot_vim.host.dispatch.SecurityPolicy
- Direction
- bridge.godot_host uses host.dispatch, so a change to host.dispatch can break bridge.godot_host, while a change to bridge.godot_host can't break host.dispatch.
- Position
- Below the diagonal: bridge.godot_host uses a module listed above it, which is the healthy direction.
25→23 bridge.godot_host uses state.shell✕
- Connections
- 1 pair of types, where a type in bridge.godot_host uses a type in state.shell.
- The types involved
godot_vim.bridge.godot_host.GodotHost→godot_vim.state.shell.ShellState
- Direction
- bridge.godot_host uses state.shell, so a change to state.shell can break bridge.godot_host, while a change to bridge.godot_host can't break state.shell.
- Position
- Below the diagonal: bridge.godot_host uses a module listed above it, which is the healthy direction.
26→3 actions.providers.debugger uses actions.outcome✕
- Connections
- 1 pair of types, where a type in actions.providers.debugger uses a type in actions.outcome.
- The types involved
godot_vim.actions.providers.debugger.debugger$module→godot_vim.actions.outcome.Outcome
- Direction
- actions.providers.debugger uses actions.outcome, so a change to actions.outcome can break actions.providers.debugger, while a change to actions.providers.debugger can't break actions.outcome.
- Position
- Below the diagonal: actions.providers.debugger uses a module listed above it, which is the healthy direction.
26→6 actions.providers.debugger uses navigation.dock_nav✕
- Connections
- 2 pairs of types, where a type in actions.providers.debugger uses a type in navigation.dock_nav.
- The types involved
godot_vim.actions.providers.debugger.DebuggerTreeOps→godot_vim.navigation.dock_nav.NavDirectiongodot_vim.actions.providers.debugger.debugger$module→godot_vim.navigation.dock_nav.NavDirection
- Direction
- actions.providers.debugger uses navigation.dock_nav, so a change to navigation.dock_nav can break actions.providers.debugger, while a change to actions.providers.debugger can't break navigation.dock_nav.
- Position
- Below the diagonal: actions.providers.debugger uses a module listed above it, which is the healthy direction.
26→24 actions.providers.debugger uses actions.action✕
- Connections
- 1 pair of types, where a type in actions.providers.debugger uses a type in actions.action.
- The types involved
godot_vim.actions.providers.debugger.debugger$module→godot_vim.actions.action.ActionCtx
- Direction
- actions.providers.debugger uses actions.action, so a change to actions.action can break actions.providers.debugger, while a change to actions.providers.debugger can't break actions.action.
- Position
- Below the diagonal: actions.providers.debugger uses a module listed above it, which is the healthy direction.
27→1 actions.resolve uses actions.caps✕
- Connections
- 1 pair of types, where a type in actions.resolve uses a type in actions.caps.
- The types involved
godot_vim.actions.resolve.resolve$module→godot_vim.actions.caps.Caps
- Direction
- actions.resolve uses actions.caps, so a change to actions.caps can break actions.resolve, while a change to actions.resolve can't break actions.caps.
- Position
- Below the diagonal: actions.resolve uses a module listed above it, which is the healthy direction.
27→2 actions.resolve uses actions.keys✕
- Connections
- 1 pair of types, where a type in actions.resolve uses a type in actions.keys.
- The types involved
godot_vim.actions.resolve.ResolveInput→godot_vim.actions.keys.Probes
- Direction
- actions.resolve uses actions.keys, so a change to actions.keys can break actions.resolve, while a change to actions.resolve can't break actions.keys.
- Position
- Below the diagonal: actions.resolve uses a module listed above it, which is the healthy direction.
27→11 actions.resolve uses actions.surface✕
- Connections
- 2 pairs of types, where a type in actions.resolve uses a type in actions.surface.
- The types involved
godot_vim.actions.resolve.OverlayPlan→godot_vim.actions.surface.OverlayFactsgodot_vim.actions.resolve.ResolveInput→godot_vim.actions.surface.SurfacePath
- Direction
- actions.resolve uses actions.surface, so a change to actions.surface can break actions.resolve, while a change to actions.resolve can't break actions.surface.
- Position
- Below the diagonal: actions.resolve uses a module listed above it, which is the healthy direction.
27→20 actions.resolve uses actions.bind✕
- Connections
- 4 pairs of types, where a type in actions.resolve uses a type in actions.bind.
- The types involved
godot_vim.actions.resolve.Candidate→godot_vim.actions.bind.Consumptiongodot_vim.actions.resolve.Candidate→godot_vim.actions.bind.Repeatgodot_vim.actions.resolve.ResolveInput→godot_vim.actions.bind.BindingIndexgodot_vim.actions.resolve.resolve$module→godot_vim.actions.bind.BindingIndex
- Direction
- actions.resolve uses actions.bind, so a change to actions.bind can break actions.resolve, while a change to actions.resolve can't break actions.bind.
- Position
- Below the diagonal: actions.resolve uses a module listed above it, which is the healthy direction.
27→24 actions.resolve uses actions.action✕
- Connections
- 3 pairs of types, where a type in actions.resolve uses a type in actions.action.
- The types involved
godot_vim.actions.resolve.Candidate→godot_vim.actions.action.Paramsgodot_vim.actions.resolve.ResolveInput→godot_vim.actions.action.ActionRegistrygodot_vim.actions.resolve.resolve$module→godot_vim.actions.action.ActionRegistry
- Direction
- actions.resolve uses actions.action, so a change to actions.action can break actions.resolve, while a change to actions.resolve can't break actions.action.
- Position
- Below the diagonal: actions.resolve uses a module listed above it, which is the healthy direction.
28→3 actions.specs uses actions.outcome✕
- Connections
- 1 pair of types, where a type in actions.specs uses a type in actions.outcome.
- The types involved
godot_vim.actions.specs.specs$module→godot_vim.actions.outcome.Outcome
- Direction
- actions.specs uses actions.outcome, so a change to actions.outcome can break actions.specs, while a change to actions.specs can't break actions.outcome.
- Position
- Below the diagonal: actions.specs uses a module listed above it, which is the healthy direction.
28→5 actions.specs uses effects.compound✕
- Connections
- 1 pair of types, where a type in actions.specs uses a type in effects.compound.
- The types involved
godot_vim.actions.specs.specs$module→godot_vim.effects.compound.WindowNavAction
- Direction
- actions.specs uses effects.compound, so a change to effects.compound can break actions.specs, while a change to actions.specs can't break effects.compound.
- Position
- Below the diagonal: actions.specs uses a module listed above it, which is the healthy direction.
28→6 actions.specs uses navigation.dock_nav✕
- Connections
- 2 pairs of types, where a type in actions.specs uses a type in navigation.dock_nav.
- The types involved
godot_vim.actions.specs.specs$module→godot_vim.navigation.dock_nav.HierarchyActiongodot_vim.actions.specs.specs$module→godot_vim.navigation.dock_nav.NavDirection
- Direction
- actions.specs uses navigation.dock_nav, so a change to navigation.dock_nav can break actions.specs, while a change to actions.specs can't break navigation.dock_nav.
- Position
- Below the diagonal: actions.specs uses a module listed above it, which is the healthy direction.
28→24 actions.specs uses actions.action✕
- Connections
- 2 pairs of types, where a type in actions.specs uses a type in actions.action.
- The types involved
godot_vim.actions.specs.specs$module→godot_vim.actions.action.ActionCtxgodot_vim.actions.specs.specs$module→godot_vim.actions.action.ActionRegistry
- Direction
- actions.specs uses actions.action, so a change to actions.action can break actions.specs, while a change to actions.specs can't break actions.action.
- Position
- Below the diagonal: actions.specs uses a module listed above it, which is the healthy direction.
29→10 bridge.port_impl uses types✕
- Connections
- 1 pair of types, where a type in bridge.port_impl uses a type in types.
- The types involved
godot_vim.bridge.port_impl.CodeEditPort→godot_vim.types.CharLineCol
- Direction
- bridge.port_impl uses types, so a change to types can break bridge.port_impl, while a change to bridge.port_impl can't break types.
- Position
- Below the diagonal: bridge.port_impl uses a module listed above it, which is the healthy direction.
29→25 bridge.port_impl uses bridge.godot_host✕
- Connections
- 1 pair of types, where a type in bridge.port_impl uses a type in bridge.godot_host.
- The types involved
godot_vim.bridge.port_impl.CodeEditPort→godot_vim.bridge.godot_host.PendingUiAction
- Direction
- bridge.port_impl uses bridge.godot_host, so a change to bridge.godot_host can break bridge.port_impl, while a change to bridge.port_impl can't break bridge.godot_host.
- Position
- Below the diagonal: bridge.port_impl uses a module listed above it, which is the healthy direction.
30→9 config.policy uses settings.snapshot✕
- Connections
- 3 pairs of types, where a type in config.policy uses a type in settings.snapshot.
- The types involved
godot_vim.config.policy.LoadPolicy→godot_vim.settings.snapshot.ProjectVimrcgodot_vim.config.policy.SourceAccess→godot_vim.settings.snapshot.FileAccessScopegodot_vim.config.policy.Tier→godot_vim.settings.snapshot.ProjectVimrc
- Direction
- config.policy uses settings.snapshot, so a change to settings.snapshot can break config.policy, while a change to config.policy can't break settings.snapshot.
- Position
- Below the diagonal: config.policy uses a module listed above it, which is the healthy direction.
30→15 config.policy uses config.source✕
- Connections
- 1 pair of types, where a type in config.policy uses a type in config.source.
- The types involved
godot_vim.config.policy.SourceAccess→godot_vim.config.source.SourceEnv
- Direction
- config.policy uses config.source, so a change to config.source can break config.policy, while a change to config.policy can't break config.source.
- Position
- Below the diagonal: config.policy uses a module listed above it, which is the healthy direction.
30→24 config.policy uses actions.action✕
- Connections
- 1 pair of types, where a type in config.policy uses a type in actions.action.
- The types involved
godot_vim.config.policy.LoadPolicy→godot_vim.actions.action.ActionRegistry
- Direction
- config.policy uses actions.action, so a change to actions.action can break config.policy, while a change to config.policy can't break actions.action.
- Position
- Below the diagonal: config.policy uses a module listed above it, which is the healthy direction.
31→2 actions.introspect uses actions.keys✕
- Connections
- 1 pair of types, where a type in actions.introspect uses a type in actions.keys.
- The types involved
godot_vim.actions.introspect.introspect$module→godot_vim.actions.keys.Probes
- Direction
- actions.introspect uses actions.keys, so a change to actions.keys can break actions.introspect, while a change to actions.introspect can't break actions.keys.
- Position
- Below the diagonal: actions.introspect uses a module listed above it, which is the healthy direction.
31→11 actions.introspect uses actions.surface✕
- Connections
- 2 pairs of types, where a type in actions.introspect uses a type in actions.surface.
- The types involved
godot_vim.actions.introspect.introspect$module→godot_vim.actions.surface.FocusChaingodot_vim.actions.introspect.introspect$module→godot_vim.actions.surface.SurfacePath
- Direction
- actions.introspect uses actions.surface, so a change to actions.surface can break actions.introspect, while a change to actions.introspect can't break actions.surface.
- Position
- Below the diagonal: actions.introspect uses a module listed above it, which is the healthy direction.
31→20 actions.introspect uses actions.bind✕
- Connections
- 2 pairs of types, where a type in actions.introspect uses a type in actions.bind.
- The types involved
godot_vim.actions.introspect.introspect$module→godot_vim.actions.bind.BindingIndexgodot_vim.actions.introspect.introspect$module→godot_vim.actions.bind.Rule
- Direction
- actions.introspect uses actions.bind, so a change to actions.bind can break actions.introspect, while a change to actions.introspect can't break actions.bind.
- Position
- Below the diagonal: actions.introspect uses a module listed above it, which is the healthy direction.
31→24 actions.introspect uses actions.action✕
- Connections
- 1 pair of types, where a type in actions.introspect uses a type in actions.action.
- The types involved
godot_vim.actions.introspect.introspect$module→godot_vim.actions.action.ActionRegistry
- Direction
- actions.introspect uses actions.action, so a change to actions.action can break actions.introspect, while a change to actions.introspect can't break actions.action.
- Position
- Below the diagonal: actions.introspect uses a module listed above it, which is the healthy direction.
31→27 actions.introspect uses actions.resolve✕
- Connections
- 1 pair of types, where a type in actions.introspect uses a type in actions.resolve.
- The types involved
godot_vim.actions.introspect.introspect$module→godot_vim.actions.resolve.Stop
- Direction
- actions.introspect uses actions.resolve, so a change to actions.resolve can break actions.introspect, while a change to actions.introspect can't break actions.resolve.
- Position
- Below the diagonal: actions.introspect uses a module listed above it, which is the healthy direction.
32→1 actions.sequence uses actions.caps✕
- Connections
- 1 pair of types, where a type in actions.sequence uses a type in actions.caps.
- The types involved
godot_vim.actions.sequence.Pending→godot_vim.actions.caps.Caps
- Direction
- actions.sequence uses actions.caps, so a change to actions.caps can break actions.sequence, while a change to actions.sequence can't break actions.caps.
- Position
- Below the diagonal: actions.sequence uses a module listed above it, which is the healthy direction.
32→11 actions.sequence uses actions.surface✕
- Connections
- 1 pair of types, where a type in actions.sequence uses a type in actions.surface.
- The types involved
godot_vim.actions.sequence.sequence$module→godot_vim.actions.surface.SurfacePath
- Direction
- actions.sequence uses actions.surface, so a change to actions.surface can break actions.sequence, while a change to actions.sequence can't break actions.surface.
- Position
- Below the diagonal: actions.sequence uses a module listed above it, which is the healthy direction.
32→20 actions.sequence uses actions.bind✕
- Connections
- 2 pairs of types, where a type in actions.sequence uses a type in actions.bind.
- The types involved
godot_vim.actions.sequence.Pending→godot_vim.actions.bind.BindingIndexgodot_vim.actions.sequence.sequence$module→godot_vim.actions.bind.BindingIndex
- Direction
- actions.sequence uses actions.bind, so a change to actions.bind can break actions.sequence, while a change to actions.sequence can't break actions.bind.
- Position
- Below the diagonal: actions.sequence uses a module listed above it, which is the healthy direction.
32→24 actions.sequence uses actions.action✕
- Connections
- 1 pair of types, where a type in actions.sequence uses a type in actions.action.
- The types involved
godot_vim.actions.sequence.Pending→godot_vim.actions.action.ActionRegistry
- Direction
- actions.sequence uses actions.action, so a change to actions.action can break actions.sequence, while a change to actions.sequence can't break actions.action.
- Position
- Below the diagonal: actions.sequence uses a module listed above it, which is the healthy direction.
32→27 actions.sequence uses actions.resolve✕
- Connections
- 1 pair of types, where a type in actions.sequence uses a type in actions.resolve.
- The types involved
godot_vim.actions.sequence.Pending→godot_vim.actions.resolve.ResolveInput
- Direction
- actions.sequence uses actions.resolve, so a change to actions.resolve can break actions.sequence, while a change to actions.sequence can't break actions.resolve.
- Position
- Below the diagonal: actions.sequence uses a module listed above it, which is the healthy direction.
33→11 controller.completion uses actions.surface✕
- Connections
- 1 pair of types, where a type in controller.completion uses a type in actions.surface.
- The types involved
godot_vim.controller.completion.completion$module→godot_vim.actions.surface.HostKey
- Direction
- controller.completion uses actions.surface, so a change to actions.surface can break controller.completion, while a change to controller.completion can't break actions.surface.
- Position
- Below the diagonal: controller.completion uses a module listed above it, which is the healthy direction.
33→24 controller.completion uses actions.action✕
- Connections
- 1 pair of types, where a type in controller.completion uses a type in actions.action.
- The types involved
godot_vim.controller.completion.CompletionPort→godot_vim.actions.action.CompletionOps
- Direction
- controller.completion uses actions.action, so a change to actions.action can break controller.completion, while a change to controller.completion can't break actions.action.
- Position
- Below the diagonal: controller.completion uses a module listed above it, which is the healthy direction.
33→27 controller.completion uses actions.resolve✕
- Connections
- 2 pairs of types, where a type in controller.completion uses a type in actions.resolve.
- The types involved
godot_vim.controller.completion.completion$module→godot_vim.actions.resolve.Dispositiongodot_vim.controller.completion.completion$module→godot_vim.actions.resolve.OverlayPlan
- Direction
- controller.completion uses actions.resolve, so a change to actions.resolve can break controller.completion, while a change to controller.completion can't break actions.resolve.
- Position
- Below the diagonal: controller.completion uses a module listed above it, which is the healthy direction.
34→27 controller.pipeline_outcome uses actions.resolve✕
- Connections
- 1 pair of types, where a type in controller.pipeline_outcome uses a type in actions.resolve.
- The types involved
godot_vim.controller.pipeline_outcome.pipeline_outcome$module→godot_vim.actions.resolve.Disposition
- Direction
- controller.pipeline_outcome uses actions.resolve, so a change to actions.resolve can break controller.pipeline_outcome, while a change to controller.pipeline_outcome can't break actions.resolve.
- Position
- Below the diagonal: controller.pipeline_outcome uses a module listed above it, which is the healthy direction.
35→5 effects.dispatch uses effects.compound✕
- Connections
- 1 pair of types, where a type in effects.dispatch uses a type in effects.compound.
- The types involved
godot_vim.effects.dispatch.dispatch$module→godot_vim.effects.compound.CompoundAction
- Direction
- effects.dispatch uses effects.compound, so a change to effects.compound can break effects.dispatch, while a change to effects.dispatch can't break effects.compound.
- Position
- Below the diagonal: effects.dispatch uses a module listed above it, which is the healthy direction.
35→12 effects.dispatch uses bridge.codec✕
- Connections
- 3 pairs of types, where a type in effects.dispatch uses a type in bridge.codec.
- The types involved
godot_vim.effects.dispatch.DispatchContext→godot_vim.bridge.codec.LineIndexgodot_vim.effects.dispatch.DispatchEnv→godot_vim.bridge.codec.DocumentViewgodot_vim.effects.dispatch.dispatch$module→godot_vim.bridge.codec.DocumentView
- Direction
- effects.dispatch uses bridge.codec, so a change to bridge.codec can break effects.dispatch, while a change to effects.dispatch can't break bridge.codec.
- Position
- Below the diagonal: effects.dispatch uses a module listed above it, which is the healthy direction.
35→23 effects.dispatch uses state.shell✕
- Connections
- 2 pairs of types, where a type in effects.dispatch uses a type in state.shell.
- The types involved
godot_vim.effects.dispatch.DispatchContext→godot_vim.state.shell.ShellStategodot_vim.effects.dispatch.dispatch$module→godot_vim.state.shell.ShellState
- Direction
- effects.dispatch uses state.shell, so a change to state.shell can break effects.dispatch, while a change to effects.dispatch can't break state.shell.
- Position
- Below the diagonal: effects.dispatch uses a module listed above it, which is the healthy direction.
35→24 effects.dispatch uses actions.action✕
- Connections
- 1 pair of types, where a type in effects.dispatch uses a type in actions.action.
- The types involved
godot_vim.effects.dispatch.dispatch$module→godot_vim.actions.action.Effect
- Direction
- effects.dispatch uses actions.action, so a change to actions.action can break effects.dispatch, while a change to effects.dispatch can't break actions.action.
- Position
- Below the diagonal: effects.dispatch uses a module listed above it, which is the healthy direction.
35→29 effects.dispatch uses bridge.port_impl✕
- Connections
- 1 pair of types, where a type in effects.dispatch uses a type in bridge.port_impl.
- The types involved
godot_vim.effects.dispatch.DispatchContext→godot_vim.bridge.port_impl.AutoBraceSnapshot
- Direction
- effects.dispatch uses bridge.port_impl, so a change to bridge.port_impl can break effects.dispatch, while a change to effects.dispatch can't break bridge.port_impl.
- Position
- Below the diagonal: effects.dispatch uses a module listed above it, which is the healthy direction.
36→9 controller uses settings.snapshot✕
- Connections
- 2 pairs of types, where a type in controller uses a type in settings.snapshot.
- The types involved
godot_vim.controller.ControllerContext→godot_vim.settings.snapshot.SettingsSnapshotgodot_vim.controller.VimController→godot_vim.settings.snapshot.SettingsSnapshot
- Direction
- controller uses settings.snapshot, so a change to settings.snapshot can break controller, while a change to controller can't break settings.snapshot.
- Position
- Below the diagonal: controller uses a module listed above it, which is the healthy direction.
36→10 controller uses types✕
- Connections
- 2 pairs of types, where a type in controller uses a type in types.
- The types involved
godot_vim.controller.VimController→godot_vim.types.StatusMessagegodot_vim.controller.VimController→godot_vim.types.UiSnapshot
- Direction
- controller uses types, so a change to types can break controller, while a change to controller can't break types.
- Position
- Below the diagonal: controller uses a module listed above it, which is the healthy direction.
36→16 controller uses host.dispatch✕
- Connections
- 2 pairs of types, where a type in controller uses a type in host.dispatch.
- The types involved
godot_vim.controller.ControllerContext→godot_vim.host.dispatch.SecurityPolicygodot_vim.controller.VimController→godot_vim.host.dispatch.SecurityPolicy
- Direction
- controller uses host.dispatch, so a change to host.dispatch can break controller, while a change to controller can't break host.dispatch.
- Position
- Below the diagonal: controller uses a module listed above it, which is the healthy direction.
36→23 controller uses state.shell✕
- Connections
- 1 pair of types, where a type in controller uses a type in state.shell.
- The types involved
godot_vim.controller.VimController→godot_vim.state.shell.ShellState
- Direction
- controller uses state.shell, so a change to state.shell can break controller, while a change to controller can't break state.shell.
- Position
- Below the diagonal: controller uses a module listed above it, which is the healthy direction.
36→24 controller uses actions.action✕
- Connections
- 1 pair of types, where a type in controller uses a type in actions.action.
- The types involved
godot_vim.controller.TransientShellState→godot_vim.actions.action.Effect
- Direction
- controller uses actions.action, so a change to actions.action can break controller, while a change to controller can't break actions.action.
- Position
- Below the diagonal: controller uses a module listed above it, which is the healthy direction.
36→25 controller uses bridge.godot_host✕
- Connections
- 3 pairs of types, where a type in controller uses a type in bridge.godot_host.
- The types involved
godot_vim.controller.TransientShellState→godot_vim.bridge.godot_host.PendingUiActiongodot_vim.controller.VimController→godot_vim.bridge.godot_host.GodotHostgodot_vim.controller.VimController→godot_vim.bridge.godot_host.PendingUiAction
- Direction
- controller uses bridge.godot_host, so a change to bridge.godot_host can break controller, while a change to controller can't break bridge.godot_host.
- Position
- Below the diagonal: controller uses a module listed above it, which is the healthy direction.
36→27 controller uses actions.resolve✕
- Connections
- 1 pair of types, where a type in controller uses a type in actions.resolve.
- The types involved
godot_vim.controller.VimController→godot_vim.actions.resolve.OverlayPlan
- Direction
- controller uses actions.resolve, so a change to actions.resolve can break controller, while a change to controller can't break actions.resolve.
- Position
- Below the diagonal: controller uses a module listed above it, which is the healthy direction.
36→30 controller uses config.policy✕
- Connections
- 1 pair of types, where a type in controller uses a type in config.policy.
- The types involved
godot_vim.controller.VimController→godot_vim.config.policy.LoadPolicy
- Direction
- controller uses config.policy, so a change to config.policy can break controller, while a change to controller can't break config.policy.
- Position
- Below the diagonal: controller uses a module listed above it, which is the healthy direction.
36→34 controller uses controller.pipeline_outcome✕
- Connections
- 1 pair of types, where a type in controller uses a type in controller.pipeline_outcome.
- The types involved
godot_vim.controller.VimController→godot_vim.controller.pipeline_outcome.PipelineOutcome
- Direction
- controller uses controller.pipeline_outcome, so a change to controller.pipeline_outcome can break controller, while a change to controller can't break controller.pipeline_outcome.
- Position
- Below the diagonal: controller uses a module listed above it, which is the healthy direction.
37→8 plugin.outcome uses plugin.caret_reconcile✕
- Connections
- 1 pair of types, where a type in plugin.outcome uses a type in plugin.caret_reconcile.
- The types involved
godot_vim.plugin.outcome.EngineOutcome→godot_vim.plugin.caret_reconcile.CaretReconciler
- Direction
- plugin.outcome uses plugin.caret_reconcile, so a change to plugin.caret_reconcile can break plugin.outcome, while a change to plugin.outcome can't break plugin.caret_reconcile.
- Position
- Below the diagonal: plugin.outcome uses a module listed above it, which is the healthy direction.
37→10 plugin.outcome uses types✕
- Connections
- 1 pair of types, where a type in plugin.outcome uses a type in types.
- The types involved
godot_vim.plugin.outcome.EngineOutcome→godot_vim.types.UiSnapshot
- Direction
- plugin.outcome uses types, so a change to types can break plugin.outcome, while a change to plugin.outcome can't break types.
- Position
- Below the diagonal: plugin.outcome uses a module listed above it, which is the healthy direction.
37→19 plugin.outcome uses ui.coordinator✕
- Connections
- 1 pair of types, where a type in plugin.outcome uses a type in ui.coordinator.
- The types involved
godot_vim.plugin.outcome.EngineOutcome→godot_vim.ui.coordinator.UiCoordinator
- Direction
- plugin.outcome uses ui.coordinator, so a change to ui.coordinator can break plugin.outcome, while a change to plugin.outcome can't break ui.coordinator.
- Position
- Below the diagonal: plugin.outcome uses a module listed above it, which is the healthy direction.
37→34 plugin.outcome uses controller.pipeline_outcome✕
- Connections
- 2 pairs of types, where a type in plugin.outcome uses a type in controller.pipeline_outcome.
- The types involved
godot_vim.plugin.outcome.AppliedOutcome→godot_vim.controller.pipeline_outcome.PipelineOutcomegodot_vim.plugin.outcome.EngineOutcome→godot_vim.controller.pipeline_outcome.PipelineOutcome
- Direction
- plugin.outcome uses controller.pipeline_outcome, so a change to controller.pipeline_outcome can break plugin.outcome, while a change to plugin.outcome can't break controller.pipeline_outcome.
- Position
- Below the diagonal: plugin.outcome uses a module listed above it, which is the healthy direction.
38→5 controller.process uses effects.compound✕
- Connections
- 1 pair of types, where a type in controller.process uses a type in effects.compound.
- The types involved
godot_vim.controller.process.process$module→godot_vim.effects.compound.WindowNavAction
- Direction
- controller.process uses effects.compound, so a change to effects.compound can break controller.process, while a change to controller.process can't break effects.compound.
- Position
- Below the diagonal: controller.process uses a module listed above it, which is the healthy direction.
38→24 controller.process uses actions.action✕
- Connections
- 1 pair of types, where a type in controller.process uses a type in actions.action.
- The types involved
godot_vim.controller.process.process$module→godot_vim.actions.action.Effect
- Direction
- controller.process uses actions.action, so a change to actions.action can break controller.process, while a change to controller.process can't break actions.action.
- Position
- Below the diagonal: controller.process uses a module listed above it, which is the healthy direction.
38→25 controller.process uses bridge.godot_host✕
- Connections
- 1 pair of types, where a type in controller.process uses a type in bridge.godot_host.
- The types involved
godot_vim.controller.process.process$module→godot_vim.bridge.godot_host.PendingUiAction
- Direction
- controller.process uses bridge.godot_host, so a change to bridge.godot_host can break controller.process, while a change to controller.process can't break bridge.godot_host.
- Position
- Below the diagonal: controller.process uses a module listed above it, which is the healthy direction.
38→27 controller.process uses actions.resolve✕
- Connections
- 1 pair of types, where a type in controller.process uses a type in actions.resolve.
- The types involved
godot_vim.controller.process.process$module→godot_vim.actions.resolve.OverlayPlan
- Direction
- controller.process uses actions.resolve, so a change to actions.resolve can break controller.process, while a change to controller.process can't break actions.resolve.
- Position
- Below the diagonal: controller.process uses a module listed above it, which is the healthy direction.
38→34 controller.process uses controller.pipeline_outcome✕
- Connections
- 1 pair of types, where a type in controller.process uses a type in controller.pipeline_outcome.
- The types involved
godot_vim.controller.process.process$module→godot_vim.controller.pipeline_outcome.PipelineOutcome
- Direction
- controller.process uses controller.pipeline_outcome, so a change to controller.pipeline_outcome can break controller.process, while a change to controller.process can't break controller.pipeline_outcome.
- Position
- Below the diagonal: controller.process uses a module listed above it, which is the healthy direction.
38→36 controller.process uses controller✕
- Connections
- 1 pair of types, where a type in controller.process uses a type in controller.
- The types involved
godot_vim.controller.process.process$module→godot_vim.controller.ControllerContext
- Direction
- controller.process uses controller, so a change to controller can break controller.process, while a change to controller.process can't break controller.
- Position
- Below the diagonal: controller.process uses a module listed above it, which is the healthy direction.
39→8 plugin.input uses plugin.caret_reconcile✕
- Connections
- 1 pair of types, where a type in plugin.input uses a type in plugin.caret_reconcile.
- The types involved
godot_vim.plugin.input.input$module→godot_vim.plugin.caret_reconcile.CaretReconciler
- Direction
- plugin.input uses plugin.caret_reconcile, so a change to plugin.caret_reconcile can break plugin.input, while a change to plugin.input can't break plugin.caret_reconcile.
- Position
- Below the diagonal: plugin.input uses a module listed above it, which is the healthy direction.
39→11 plugin.input uses actions.surface✕
- Connections
- 2 pairs of types, where a type in plugin.input uses a type in actions.surface.
- The types involved
godot_vim.plugin.input.ChainCache→godot_vim.actions.surface.FocusChaingodot_vim.plugin.input.input$module→godot_vim.actions.surface.HostKey
- Direction
- plugin.input uses actions.surface, so a change to actions.surface can break plugin.input, while a change to plugin.input can't break actions.surface.
- Position
- Below the diagonal: plugin.input uses a module listed above it, which is the healthy direction.
39→19 plugin.input uses ui.coordinator✕
- Connections
- 1 pair of types, where a type in plugin.input uses a type in ui.coordinator.
- The types involved
godot_vim.plugin.input.input$module→godot_vim.ui.coordinator.UiCoordinator
- Direction
- plugin.input uses ui.coordinator, so a change to ui.coordinator can break plugin.input, while a change to plugin.input can't break ui.coordinator.
- Position
- Below the diagonal: plugin.input uses a module listed above it, which is the healthy direction.
39→27 plugin.input uses actions.resolve✕
- Connections
- 1 pair of types, where a type in plugin.input uses a type in actions.resolve.
- The types involved
godot_vim.plugin.input.input$module→godot_vim.actions.resolve.Disposition
- Direction
- plugin.input uses actions.resolve, so a change to actions.resolve can break plugin.input, while a change to plugin.input can't break actions.resolve.
- Position
- Below the diagonal: plugin.input uses a module listed above it, which is the healthy direction.
39→36 plugin.input uses controller✕
- Connections
- 1 pair of types, where a type in plugin.input uses a type in controller.
- The types involved
godot_vim.plugin.input.input$module→godot_vim.controller.VimController
- Direction
- plugin.input uses controller, so a change to controller can break plugin.input, while a change to plugin.input can't break controller.
- Position
- Below the diagonal: plugin.input uses a module listed above it, which is the healthy direction.
40→3 plugin uses actions.outcome✕
- Connections
- 1 pair of types, where a type in plugin uses a type in actions.outcome.
- The types involved
godot_vim.plugin.GodotVimCore→godot_vim.actions.outcome.Outcome
- Direction
- plugin uses actions.outcome, so a change to actions.outcome can break plugin, while a change to plugin can't break actions.outcome.
- Position
- Below the diagonal: plugin uses a module listed above it, which is the healthy direction.
40→4 plugin uses config.path✕
- Connections
- 1 pair of types, where a type in plugin uses a type in config.path.
- The types involved
godot_vim.plugin.GodotVimCore→godot_vim.config.path.ResolvedConfig
- Direction
- plugin uses config.path, so a change to config.path can break plugin, while a change to plugin can't break config.path.
- Position
- Below the diagonal: plugin uses a module listed above it, which is the healthy direction.
40→7 plugin uses navigation.filesystem_explorer✕
- Connections
- 1 pair of types, where a type in plugin uses a type in navigation.filesystem_explorer.
- The types involved
godot_vim.plugin.GodotVimCore→godot_vim.navigation.filesystem_explorer.FileSystemExplorer
- Direction
- plugin uses navigation.filesystem_explorer, so a change to navigation.filesystem_explorer can break plugin, while a change to plugin can't break navigation.filesystem_explorer.
- Position
- Below the diagonal: plugin uses a module listed above it, which is the healthy direction.
40→8 plugin uses plugin.caret_reconcile✕
- Connections
- 1 pair of types, where a type in plugin uses a type in plugin.caret_reconcile.
- The types involved
godot_vim.plugin.GodotVimCore→godot_vim.plugin.caret_reconcile.CaretReconciler
- Direction
- plugin uses plugin.caret_reconcile, so a change to plugin.caret_reconcile can break plugin, while a change to plugin can't break plugin.caret_reconcile.
- Position
- Below the diagonal: plugin uses a module listed above it, which is the healthy direction.
40→9 plugin uses settings.snapshot✕
- Connections
- 3 pairs of types, where a type in plugin uses a type in settings.snapshot.
- The types involved
godot_vim.plugin.GodotVimCore→godot_vim.settings.snapshot.FileAccessScopegodot_vim.plugin.GodotVimCore→godot_vim.settings.snapshot.ProjectVimrcgodot_vim.plugin.GodotVimCore→godot_vim.settings.snapshot.SettingsSnapshot
- Direction
- plugin uses settings.snapshot, so a change to settings.snapshot can break plugin, while a change to plugin can't break settings.snapshot.
- Position
- Below the diagonal: plugin uses a module listed above it, which is the healthy direction.
40→11 plugin uses actions.surface✕
- Connections
- 1 pair of types, where a type in plugin uses a type in actions.surface.
- The types involved
godot_vim.plugin.GodotVimCore→godot_vim.actions.surface.SurfacePath
- Direction
- plugin uses actions.surface, so a change to actions.surface can break plugin, while a change to plugin can't break actions.surface.
- Position
- Below the diagonal: plugin uses a module listed above it, which is the healthy direction.
40→15 plugin uses config.source✕
- Connections
- 1 pair of types, where a type in plugin uses a type in config.source.
- The types involved
godot_vim.plugin.GodotVimCore→godot_vim.config.source.Loaded
- Direction
- plugin uses config.source, so a change to config.source can break plugin, while a change to plugin can't break config.source.
- Position
- Below the diagonal: plugin uses a module listed above it, which is the healthy direction.
40→19 plugin uses ui.coordinator✕
- Connections
- 1 pair of types, where a type in plugin uses a type in ui.coordinator.
- The types involved
godot_vim.plugin.GodotVimCore→godot_vim.ui.coordinator.UiCoordinator
- Direction
- plugin uses ui.coordinator, so a change to ui.coordinator can break plugin, while a change to plugin can't break ui.coordinator.
- Position
- Below the diagonal: plugin uses a module listed above it, which is the healthy direction.
40→20 plugin uses actions.bind✕
- Connections
- 2 pairs of types, where a type in plugin uses a type in actions.bind.
- The types involved
godot_vim.plugin.GodotVimCore→godot_vim.actions.bind.BindingIndexgodot_vim.plugin.GodotVimCore→godot_vim.actions.bind.PanelDiagnostic
- Direction
- plugin uses actions.bind, so a change to actions.bind can break plugin, while a change to plugin can't break actions.bind.
- Position
- Below the diagonal: plugin uses a module listed above it, which is the healthy direction.
40→22 plugin uses plugin.source_cmd✕
- Connections
- 2 pairs of types, where a type in plugin uses a type in plugin.source_cmd.
- The types involved
godot_vim.plugin.GodotVimCore→godot_vim.plugin.source_cmd.EnvPartsgodot_vim.plugin.GodotVimCore→godot_vim.plugin.source_cmd.LoadTarget
- Direction
- plugin uses plugin.source_cmd, so a change to plugin.source_cmd can break plugin, while a change to plugin can't break plugin.source_cmd.
- Position
- Below the diagonal: plugin uses a module listed above it, which is the healthy direction.
40→24 plugin uses actions.action✕
- Connections
- 2 pairs of types, where a type in plugin uses a type in actions.action.
- The types involved
godot_vim.plugin.GodotVimCore→godot_vim.actions.action.ActionRegistrygodot_vim.plugin.plugin$module→godot_vim.actions.action.ActionRegistry
- Direction
- plugin uses actions.action, so a change to actions.action can break plugin, while a change to plugin can't break actions.action.
- Position
- Below the diagonal: plugin uses a module listed above it, which is the healthy direction.
40→25 plugin uses bridge.godot_host✕
- Connections
- 1 pair of types, where a type in plugin uses a type in bridge.godot_host.
- The types involved
godot_vim.plugin.GodotVimCore→godot_vim.bridge.godot_host.PendingUiAction
- Direction
- plugin uses bridge.godot_host, so a change to bridge.godot_host can break plugin, while a change to plugin can't break bridge.godot_host.
- Position
- Below the diagonal: plugin uses a module listed above it, which is the healthy direction.
40→27 plugin uses actions.resolve✕
- Connections
- 1 pair of types, where a type in plugin uses a type in actions.resolve.
- The types involved
godot_vim.plugin.GodotVimCore→godot_vim.actions.resolve.Candidate
- Direction
- plugin uses actions.resolve, so a change to actions.resolve can break plugin, while a change to plugin can't break actions.resolve.
- Position
- Below the diagonal: plugin uses a module listed above it, which is the healthy direction.
40→32 plugin uses actions.sequence✕
- Connections
- 1 pair of types, where a type in plugin uses a type in actions.sequence.
- The types involved
godot_vim.plugin.GodotVimCore→godot_vim.actions.sequence.Pending
- Direction
- plugin uses actions.sequence, so a change to actions.sequence can break plugin, while a change to plugin can't break actions.sequence.
- Position
- Below the diagonal: plugin uses a module listed above it, which is the healthy direction.
40→36 plugin uses controller✕
- Connections
- 1 pair of types, where a type in plugin uses a type in controller.
- The types involved
godot_vim.plugin.GodotVimCore→godot_vim.controller.VimController
- Direction
- plugin uses controller, so a change to controller can break plugin, while a change to plugin can't break controller.
- Position
- Below the diagonal: plugin uses a module listed above it, which is the healthy direction.
40→39 plugin uses plugin.input✕
- Connections
- 1 pair of types, where a type in plugin uses a type in plugin.input.
- The types involved
godot_vim.plugin.GodotVimCore→godot_vim.plugin.input.ChainCache
- Direction
- plugin uses plugin.input, so a change to plugin.input can break plugin, while a change to plugin can't break plugin.input.
- Position
- Below the diagonal: plugin 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 | 3 | Medium |
| A05:2025 — Injection | 1 | High / Critical |
Roadmap
Top priorities: Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release; 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; Resolve the 58 Low coverage finding(s) in Code Coverage — start with outcome.rs (2), clipboard.rs (2), mod.rs (2).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 58 Low coverage finding(s) in Code Coverage — start with outcome.rs (2), clipboard.rs (2), mod.rs (2). | +3.0 pts | Medium | Code Coverage |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +3.4 pts | Medium | Release Hygiene |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.1 pts | Medium | Architecture documentation |
| 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. | +1.7 pts | Medium | Documentation (README) |
| Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live. | +0.8 pts | Medium | Incompleteness & stubs |
| Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with godot_vim::host::dispatch::execute (cyclomatic 78), godot_vim::effects::dispatch::dispatch (cyclomatic 52). | +0.4 pts | Medium | Cyclomatic Complexity |
| Resolve the 7 Hotspot finding(s) in Churn × Complexity Hotspots — start with dispatch.rs (2), process.rs, input.rs. | +0.5 pts | High | Churn × Complexity Hotspots |
| Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with godot_vim::effects::dispatch::dispatch (cognitive 111), godot_vim::host::dispatch::execute (cognitive 86). | +0.3 pts | Medium | Cognitive Complexity |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| src/ui/line_numbers.rs | 4.4 | Mixed | Cyclomatic Complexity: LineNumberManager::update_gutters_impl (cyclomatic 16) |
| src/controller/process.rs | 5.5 | Mixed | Cyclomatic Complexity: godot_vim::controller::process::process_cycle_impl (cyclomatic 29) |
| src/plugin/input.rs | 5.5 | Mixed | Cyclomatic Complexity: GodotVimCore::handle_gui_input_impl (cyclomatic 26) |
| src/plugin/mod.rs | 5.6 | Mixed | Cognitive Complexity: GodotVimCore::on_floating_window_focused (cognitive 17) |
| src/controller/mod.rs | 5.7 | Mixed | God Classes: ClassTooLong: VimController |
| src/ui/cursor_shape.rs | 5.9 | Mixed | Cyclomatic Complexity: godot_vim::ui::cursor_shape::compute_override_x_and_width (cyclomatic 18) |
| src/plugin/attach.rs | 5.9 | Mixed | Cyclomatic Complexity: GodotVimCore::detach (cyclomatic 16) |
| src/ui/geometry.rs | 5.9 | Mixed | Cognitive Complexity: godot_vim::ui::geometry::compute_highlight_rects_char (cognitive 29) |
| src/ui/mapping_dialog.rs | 5.9 | Mixed | God Classes: ClassTooLong: MappingDialog |
| src/host/dispatch.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/ui/coordinator.rs | 6.3 | Mixed | Cyclomatic Complexity: UiCoordinator::update (cyclomatic 22) |
| src/plugin/floating.rs | 6.3 | Mixed | Cognitive Complexity: GodotVimCore::connect_floating_viewport (cognitive 30) |
| src/host/custom_commands.rs | 6.3 | Mixed | Cognitive Complexity: godot_vim::host::custom_commands::handle_dock_command (cognitive 21) |
| src/host/editor_host.rs | 6.3 | Mixed | Code Duplication: Edited copy of a member (20 corresponding lines) |
| src/ui/inccommand.rs | 6.3 | Mixed | Code Duplication: Edited copy of a member (13 corresponding lines) |
| src/navigation/dock_nav.rs | 7.0 | Mixed | Cognitive Complexity: godot_vim::navigation::dock_nav::handle_tree_hierarchy (cognitive 20) |
| src/navigation/dock_search.rs | 7.0 | Mixed | Cognitive Complexity: godot_vim::navigation::dock_search::find_sibling_nav_control (cognitive 20) |
| src/ui/status_bar.rs | 7.0 | Mixed | Cognitive Complexity: VimStatusBar::update (cognitive 19) |
| src/host/external.rs | 7.0 | Mixed | Cognitive Complexity: godot_vim::host::external::reindent_lines (cognitive 17) |
| src/settings/registration.rs | 7.0 | Mixed | God Classes: FunctionTooLong: godot_vim::settings::registration::register_all |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 42 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 42 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, 200 of 202 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- 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 (2 contributor(s) across 569 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 hold 0% 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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each 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.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (65009 LoC, 99 module-visible types across 16 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala, PHP, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala, PHP, Go, Swift, Erlang, F# or Visual Basic 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.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# and Visual Basic syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin, PHP, F# and Visual Basic source only, and no C# was loaded, and this repository's Gdscript, 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.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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.
- X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Kotlin, Scala, Go, Swift, Python and Ruby source only, and no C# was loaded, no Java, Kotlin, Scala, Go, Swift, Python or Ruby was found, and this repository's Gdscript 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.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- 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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run 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.
- 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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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
16 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was godot_vim::host::dispatch::execute at 78. A further 2 function(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 godot_vim::bridge::input::get_named_key at 55 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with godot_vim::host::dispatch::execute (cyclomatic 78), godot_vim::effects::dispatch::dispatch (cyclomatic 52). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 7.0 to about 8.0/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
35 function(s) exceeded the cognitive complexity threshold of 15; the worst was godot_vim::effects::dispatch::dispatch at 111.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with godot_vim::effects::dispatch::dispatch (cognitive 111), godot_vim::host::dispatch::execute (cognitive 86). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 5.5 to about 6.3/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
20 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 7 FunctionTooLong finding(s) in God Classes — start with dispatch.rs (3), process.rs (2), registration.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 7 FileTooLong finding(s) in God Classes — start with mod.rs (2), dispatch.rs, process.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 3 ClassTooLong finding(s) in God Classes — start with mod.rs (2), mapping_dialog.rs. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
21 duplicated block group(s) detected. 1.5 % of the production lines (969 of 65,009) are in a reported copy. A further 19 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 1 of the 40 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 3 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with panelmap.rs, file.rs, floating.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (20 corresponding lines) finding(s) in Code Duplication — start with line_numbers.rs, editor_host.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with android.rs, keys.rs. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
1 of 44 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with line_numbers.rs. — One of this dimension's main actionable groups (1 warning-level).
D8 · Code Coverage
Line coverage 45.9% — 58 file(s) below 50%. Measured from the Rust suite (repository root: `cargo nextest run` and the doc tests instrumented, 3 run(s), 134 production file(s)). Taken over 3 runs of the suite: a line counts as covered only when every run executed it.
What to do
- Resolve the 58 Low coverage finding(s) in Code Coverage — start with outcome.rs (2), clipboard.rs (2), mod.rs (2). — One of this dimension's main actionable groups (58 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 96 test files): measured (0 flaky).
D12 · Dependency Hygiene
0 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 48 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. A further 11 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: src/controller/process.rs (19×29=551); src/effects/dispatch.rs (9×52=468); src/host/dispatch.rs (5×78=390)
What to do
- Resolve the 7 Hotspot finding(s) in Churn × Complexity Hotspots — start with dispatch.rs (2), process.rs, input.rs. — One of this dimension's main actionable groups (7 warning-level).
D17 · Explicit Debt
1 deducted task-comment markers across 65009 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with dispatch.rs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 5 document(s) read across 1 unit(s).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. semgrep hit a parse error in 1 file(s) — `scripts/godot-suite.sh` (line 317, line 404) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 122 of the 149 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
Build pipeline generates provenance, signs artifacts and produces an SBOM.
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `handle_command_line_edit` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/effects/mode.rs:22
- `handle_begin_insert` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/effects/mode.rs:27
- `handle_set_block_insert` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/effects/mode.rs:43
- `handle_highlight_matches` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/effects/search.rs:17
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X12 · Unreachable branch
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
- `log::trace!` at line 236 is called with an argument built by `scan_roots.iter().map(|(n,label)|{format!("{}({})",label,n.get_class())}).collect::<Vec<_>>().join(", ")` (line 243), whose cost grows with the collection it walks. Rust evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because log::trace! is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `log_enabled!`/`tracing::enabled!` test, no debug flag, no `cfg(debug_assertions)`, and the work is in the argument itself, not deferred into a field the subscriber formats or a closure the formatter calls. — src/plugin/floating.rs:236
What to do
- In Rust, hand the logger the value and let it format only what it writes: `debug!("rows: {:?}", rows)` or a field, `debug!(rows = ?rows, "loaded")` — `format_args!` and `?`/`%` fields defer the formatting. When the line needs a computed view (a `collect`, a `join`, a `serde_json::to_string`), put it behind `if log_enabled!(Level::Debug)` (`if tracing::enabled!(Level::DEBUG)` for tracing), which asks the target's own filter. The macros put their arguments behind the global maximum level only, so a collect or serialisation in the argument runs whenever any target is at debug, and the logger then drops this line.
X25 · Inert configuration knob
X5 · Nullable reference types
- `self.pending_tooltip.as_ref()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `handle_pending_ui_action` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/plugin/mod.rs:1290
- `self.attached_editor.as_ref()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `recover_controller_from_panic` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/plugin/mod.rs:1329
- `self.pending_tooltip.as_mut()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `poll_pending_tooltip` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/plugin/mod.rs:1491
- `self.pending_tooltip.take()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `poll_pending_tooltip` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/plugin/mod.rs:1495
- `i32::try_from(target)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `handle_switch_buffer` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/host/buffer.rs:68
- `offsets.last()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `decompose_multi_site_diff` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — src/controller/reconcile.rs:357, src/controller/reconcile.rs:365
- `char::from_u32(unicode)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `translate_key` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/bridge/input.rs:304
What to do
- Each row is a forced `Option`/`Result` no guard on its path proves present. Handle the absent case where it arises rather than forcing it: `?` to hand it to the caller, `if let` / `match` / `let … else` to branch on it, `unwrap_or` / `unwrap_or_default` / `unwrap_or_else` where a default is right. Where the value genuinely cannot be absent, say so in a way a reader can check from the line: test it first (`if x.is_none() { return … }`), look the key up with `contains_key` or the index against `len()`, or construct the value so it cannot be absent.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 86.1 | Strong | Solid. |
| Architecture | 95.1 | Exemplary | Solid. |
| Maturity | 76.6 | Strong | Solid. |
| Readiness | 73.2 | Strong | Largest drag on the score — prioritise here. |
| Security | 96.0 | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 70 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- 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.
- 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 — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- 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 — ~1304 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host; this repository builds only code that other code links in, and runs nothing itself, so no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (3799 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — 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
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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.
- 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
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (31 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
- 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'.
- P2 Observability — This repository's Rust source (1 module(s), 149 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the 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 — coverage data present for 134 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- 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 scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- 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: 139 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.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — 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.
- X22 Contradicted release guard — 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
- 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 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
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — 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.
- 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 — 1 finding(s)
- REDACTED
Serious — 193 finding(s)
- Low coverage: src/actions/outcome.rs src/actions/outcome.rs:1
- Low coverage: src/bridge/clipboard.rs src/bridge/clipboard.rs:1
- Low coverage: src/bridge/code_edit_ext.rs src/bridge/code_edit_ext.rs:1
- Low coverage: src/bridge/context.rs src/bridge/context.rs:1
- Low coverage: src/bridge/godot_calls.rs src/bridge/godot_calls.rs:1
- Low coverage: src/bridge/godot_host.rs src/bridge/godot_host.rs:1
- Low coverage: src/bridge/port.rs src/bridge/port.rs:1
- Low coverage: src/bridge/port_impl.rs src/bridge/port_impl.rs:1
- Low coverage: src/config/path.rs src/config/path.rs:1
- Low coverage: src/controller/completion.rs src/controller/completion.rs:1
- Low coverage: src/controller/mod.rs src/controller/mod.rs:1
- Low coverage: src/controller/process.rs src/controller/process.rs:1
- Low coverage: src/effects/compound.rs src/effects/compound.rs:1
- Low coverage: src/host/buffer.rs src/host/buffer.rs:1
- Low coverage: src/host/clipboard.rs src/host/clipboard.rs:1
- Low coverage: src/host/custom_commands.rs src/host/custom_commands.rs:1
- Low coverage: src/host/dispatch.rs src/host/dispatch.rs:1
- Low coverage: src/host/editor_host.rs src/host/editor_host.rs:1
- Low coverage: src/host/external.rs src/host/external.rs:1
- Low coverage: src/lib.rs src/lib.rs:1
- Low coverage: src/navigation/cycle.rs src/navigation/cycle.rs:1
- Low coverage: src/navigation/dock.rs src/navigation/dock.rs:1
- Low coverage: src/navigation/dock_nav.rs src/navigation/dock_nav.rs:1
- Low coverage: src/navigation/dock_search.rs src/navigation/dock_search.rs:1
- Low coverage: src/navigation/filesystem_explorer.rs src/navigation/filesystem_explorer.rs:1
- godot_vim::effects::dispatch::dispatch (cognitive 111) src/effects/dispatch.rs:397
- godot_vim::host::dispatch::execute (cognitive 86) src/host/dispatch.rs:61
- godot_vim::controller::process::process_cycle_impl (cognitive 42) src/controller/process.rs:37
- godot_vim::actions::introspect::explain_on_path (cognitive 39) src/actions/introspect.rs:298
- godot_vim::config::parser::parse_config (cognitive 39) src/config/parser.rs:19
- godot_vim::bridge::input::translate_key (cognitive 37) src/bridge/input.rs:267
- godot_vim::ui::cursor_shape::compute_override_x_and_width (cognitive 35) src/ui/cursor_shape.rs:167
- godot_vim::bridge::input::resolve_ctrl_key (cognitive 30) src/bridge/input.rs:162
- godot_vim::ui::geometry::compute_highlight_rects_char (cognitive 29) src/ui/geometry.rs:84
- godot_vim::controller::process::sync_multi_cursors_to_godot (cognitive 28) src/controller/process.rs:815
- godot_vim::controller::reconcile::decompose_multi_site_diff (cognitive 28) src/controller/reconcile.rs:250
- godot_vim::config::writer::serialize (cognitive 27) src/config/writer.rs:17
- godot_vim::host::file::handle_write_file (cognitive 24) src/host/file.rs:90
- godot_vim::actions::resolve::walk_path (cognitive 21) src/actions/resolve.rs:332
- godot_vim::host::custom_commands::handle_dock_command (cognitive 21) src/host/custom_commands.rs:175
- godot_vim::host::custom_commands::make_dock_tab_visible (cognitive 21) src/host/custom_commands.rs:258
- godot_vim::navigation::dock_nav::handle_tree_hierarchy (cognitive 20) src/navigation/dock_nav.rs:198
- godot_vim::navigation::dock_search::find_sibling_nav_control (cognitive 20) src/navigation/dock_search.rs:67
- godot_vim::ftplugin::runtime::update (cognitive 19) src/ftplugin/runtime.rs:381
- godot_vim::config::panelmap::parse_params (cognitive 18) src/config/panelmap.rs:370
- godot_vim::host::external::reindent_lines (cognitive 17) src/host/external.rs:267
- godot_vim::multi_cursor::sync::sync_cursors_to_editor (cognitive 17) src/multi_cursor/sync.rs:47
- godot_vim::effects::cursor::handle_set_selection (cognitive 16) src/effects/cursor.rs:90
- godot_vim::host::eval::eval_simple_expression (cognitive 16) src/host/eval.rs:45
- godot_vim::host::dispatch::execute (cyclomatic 78) src/host/dispatch.rs:61
- godot_vim::effects::dispatch::dispatch (cyclomatic 52) src/effects/dispatch.rs:397
- godot_vim::controller::process::process_cycle_impl (cyclomatic 29) src/controller/process.rs:37
- godot_vim::bridge::input::physical_to_ascii (cyclomatic 28) src/bridge/input.rs:97
- godot_vim::bridge::input::translate_key (cyclomatic 28) src/bridge/input.rs:267
- godot_vim::actions::introspect::explain_on_path (cyclomatic 20) src/actions/introspect.rs:298
- godot_vim::controller::reconcile::decompose_multi_site_diff (cyclomatic 19) src/controller/reconcile.rs:250
- godot_vim::bridge::input::resolve_ctrl_key (cyclomatic 18) src/bridge/input.rs:162
- godot_vim::ui::cursor_shape::compute_override_x_and_width (cyclomatic 18) src/ui/cursor_shape.rs:167
- godot_vim::config::parser::parse_config (cyclomatic 17) src/config/parser.rs:19
- godot_vim::actions::resolve::walk_path (cyclomatic 16) src/actions/resolve.rs:332
- Symbol treated as nullable, then dereferenced unguarded src/plugin/mod.rs:1290
- Symbol treated as nullable, then dereferenced unguarded src/plugin/mod.rs:1329
- Symbol treated as nullable, then dereferenced unguarded src/plugin/mod.rs:1491
- Symbol treated as nullable, then dereferenced unguarded src/plugin/mod.rs:1495
- Symbol treated as nullable, then dereferenced unguarded src/host/buffer.rs:68
- Symbol treated as nullable, then dereferenced unguarded src/controller/reconcile.rs:357
- Symbol treated as nullable, then dereferenced unguarded src/controller/reconcile.rs:365
- Symbol treated as nullable, then dereferenced unguarded src/bridge/input.rs:304
- Hotspot: src/controller/process.rs src/controller/process.rs:37
- Hotspot: src/effects/dispatch.rs src/effects/dispatch.rs:397
- Hotspot: src/host/dispatch.rs src/host/dispatch.rs:61
- Hotspot: src/plugin/input.rs src/plugin/input.rs:581
- Hotspot: src/actions/introspect.rs src/actions/introspect.rs:298
- Hotspot: src/ui/coordinator.rs src/ui/coordinator.rs:320
- Hotspot: src/plugin/attach.rs src/plugin/attach.rs:161
- FunctionTooLong: godot_vim::effects::dispatch::dispatch src/effects/dispatch.rs:397
- FunctionTooLong: godot_vim::host::dispatch::execute src/host/dispatch.rs:61
- FunctionTooLong: godot_vim::effects::dispatch::dispatch_pass2_effect src/effects/dispatch.rs:866
- FunctionTooLong: godot_vim::controller::process::process_cycle_impl src/controller/process.rs:37
- FunctionTooLong: godot_vim::settings::registration::register_all src/settings/registration.rs:30
- FunctionTooLong: godot_vim::actions::introspect::explain_on_path src/actions/introspect.rs:298
- FunctionTooLong: godot_vim::controller::process::sync_multi_cursors_to_godot src/controller/process.rs:815
- FileTooLong: plugin/mod.rs src/plugin/mod.rs
- FileTooLong: controller/mod.rs src/controller/mod.rs
- FileTooLong: effects/dispatch.rs src/effects/dispatch.rs
- FileTooLong: controller/process.rs src/controller/process.rs
- FileTooLong: ui/cursor_shape.rs src/ui/cursor_shape.rs
- FileTooLong: plugin/input.rs src/plugin/input.rs
- FileTooLong: ui/mapping_dialog.rs src/ui/mapping_dialog.rs
- GodotVimCore::handle_gui_input_impl (cognitive 39) src/plugin/input.rs:581
- GodotVimCore::connect_floating_viewport (cognitive 30) src/plugin/floating.rs:68
- GodotVimCore::detach (cognitive 20) src/plugin/attach.rs:161
- GodotVimCore::handle_input_impl (cognitive 19) src/plugin/input.rs:194
- GodotVimCore::on_floating_window_focused (cognitive 17) src/plugin/mod.rs:595
- Empty method body — does nothing with its inputs src/effects/mode.rs:22
- Empty method body — does nothing with its inputs src/effects/mode.rs:27
- Empty method body — does nothing with its inputs src/effects/mode.rs:43
- Empty method body — does nothing with its inputs src/effects/search.rs:17
- GodotVimCore::handle_gui_input_impl (cyclomatic 26) src/plugin/input.rs:581
- GodotVimCore::handle_input_impl (cyclomatic 22) src/plugin/input.rs:194
- GodotVimCore::detach (cyclomatic 16) src/plugin/attach.rs:161
- ClassTooLong: GodotVimCore src/plugin/mod.rs:72
- ClassTooLong: VimController src/controller/mod.rs:215
- ClassTooLong: MappingDialog src/ui/mapping_dialog.rs:69
- Duplicated block (10 lines × 2) src/config/panelmap.rs:242
- Duplicated block (10 lines × 2) src/host/file.rs:128
- Duplicated block (10 lines × 2) src/plugin/floating.rs:325
- TooManyMethods: GodotVimCore src/plugin/mod.rs:72
- TooManyMethods: VimController src/controller/mod.rs:215
- Edited copy of a member (20 corresponding lines) src/ui/line_numbers.rs:418
- Edited copy of a member (20 corresponding lines) src/host/editor_host.rs:212
- Edited copy of a member (12 corresponding lines) src/plugin/android.rs:108
- Edited copy of a member (12 corresponding lines) src/actions/keys.rs:222
- Edited copy of a member (14 corresponding lines) src/effects/text.rs:37
- Edited copy of a member (14 corresponding lines) src/scene_tree.rs:50
- Edited copy of a member (15 corresponding lines) src/controller/process.rs:591
- Edited copy of a member (15 corresponding lines) src/plugin/attach.rs:330
- Edited copy of a member (13 corresponding lines) src/plugin/signals.rs:47
- Edited copy of a member (13 corresponding lines) src/ui/inccommand.rs:78
- Duplicated block (15–16 lines × 2) src/controller/process.rs:136
- Duplicated block (15–16 lines × 2) src/ui/inccommand.rs:57
- Duplicated block (8 lines × 2) src/controller/process.rs:898
- Duplicated block (8 lines × 2) src/controller/reconcile.rs:353
- Duplicated block (6–7 lines × 2) src/controller/process.rs:504
- Duplicated block (6–7 lines × 2) src/ui/geometry.rs:99
- Duplicated block (7 lines × 2) src/effects/dispatch.rs:610
- Duplicated block (7 lines × 2) src/ui/mapping_dialog.rs:456
- UiCoordinator::update (cyclomatic 22) src/ui/coordinator.rs:320
- LineNumberManager::update_gutters_impl (cyclomatic 16) src/ui/line_numbers.rs:342
- TodoComment src/host/dispatch.rs:333
- UiCoordinator::update (cognitive 25) src/ui/coordinator.rs:320
- Forest::audit (cognitive 22) src/actions/surface.rs:692
- LineNumberManager::update_gutters_impl (cognitive 22) src/ui/line_numbers.rs:342
- VimStatusBar::update (cognitive 19) src/ui/status_bar.rs:202
- MappingService::user_mappings (cognitive 18) src/config/mapping_service.rs:95
- Pending::extend (cognitive 17) src/actions/sequence.rs:269
- MethodTooLong: GodotVimCore.handle_gui_input_impl src/plugin/input.rs:581
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (32 corresponding lines) src/ui/geometry.rs:146
- Edited copy of a member (30 corresponding lines) src/plugin/mod.rs:890
- Edited copy of a member (21 corresponding lines) src/state/undo_store.rs:221
- Edited copies of one member (4 members, 17+ corresponding lines) src/ui/block_visual.rs:50
- Edited copy of a member (18 corresponding lines) src/actions/providers/debugger.rs:189
- Edited copy of a member (8 corresponding lines) src/effects/scroll.rs:88
- Edited copy of a member (11 corresponding lines) src/actions/keys.rs:334
- Edited copy of a member (6 corresponding lines) src/bridge/document.rs:90
- Duplicated block (19 lines × 2) src/host/editor_host.rs:213
- Duplicated block (12–16 lines × 2) src/controller/process.rs:729
- Duplicated block (16 lines × 2) src/effects/cursor.rs:154
- Duplicated block (12 lines × 2) src/bridge/port_impl.rs:54
- Duplicated block (11 lines × 2) src/controller/mod.rs:1201
- Duplicated block (10–11 lines × 2) src/plugin/input.rs:768
- Duplicated block (8–9 lines × 3) src/effects/dispatch.rs:462
- Duplicated block (15 lines × 2) src/plugin/mod.rs:891
- Duplicated block (9 lines × 2) src/actions/introspect.rs:146
- Duplicated block (5 lines × 2) src/bridge/input.rs:178
- Edited copies of one member (5 members, 6+ corresponding lines) src/testing/bridge_tests/macros.rs:363
- Low cohesion: LineNumberManager (LCOM4 4) src/ui/line_numbers.rs:40
Minor — 8 finding(s)
- Duplicated predicate src/controller/mod.rs:1416
- Duplicated predicate src/actions/specs.rs:1036
- Duplicated predicate src/ui/cursor_shape.rs:419
- Duplicated predicate src/ui/cursor_shape.rs:424
- No ADRs
- No changelog
- Diagnostic log message is built whether or not it is wanted src/plugin/floating.rs:236
- Silent fallback default on Err src/ui/mapping_dialog.rs:639
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-fa4cce558eee42cbb31e63a1fb8354e0/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=403" --report-format json --report-path /tmp/watchdog-gitleaks-fa4cce558eee42cbb31e63a1fb8354e0/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-fa4cce558eee42cbb31e63a1fb8354e0/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 1 | 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 . | 1 | 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 |