Executive summary
neovide/neovide meets our standard for a preview release. It scores 65 out of 100 and is rated Strong, and 125 of its 127 critical findings are security problems in the build pipeline and in its servers and containers.
Production Readiness, at 61, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first steps are improving the documentation and recording design decisions, each worth about 3 points.
Eighty-nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Twenty-four secrets can leak from the build pipeline, and seven pipeline steps run downloads nobody checks. Pinning each tool to an exact version, limiting each secret to its own step and checking each download against a checksum would close these risks. The five unsafe settings in infrastructure or container files need changing to safe values. The package under a licence on your banned list needs replacing, or clearing with your legal team.
The product code is 34,242 lines, about €40,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 102 findings
- Code Duplication · Edited copy of a member (22 corresponding lines) src/renderer/box_drawing/renderer.rs
- Code Duplication · Edited copy of a member (24 corresponding lines) src/bridge/api_info.rs
- Code Duplication · Edited copy of a member (28 corresponding lines) src/settings/mod.rs
- Code Duplication · Edited copy of a member (17 corresponding lines) src/bridge/events.rs
- Code Duplication · Edited copy of a member (16 corresponding lines) src/bridge/events.rs
- Code Duplication · Edited copy of a member (12 corresponding lines) src/renderer/vsync/mod.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) src/window/wrapper/windows/context_menu.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/bridge/command.rs
- Code Duplication · Edited copy of a member (15 corresponding lines) src/bridge/command.rs
- Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) src/bridge/events.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) src/channel_utils.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) src/window/wrapper/macos/scrollbar/appearance.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/renderer/mod.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) src/window/wrapper/macos/feature.rs
- Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) src/window/settings/macos.rs
- Code Duplication · Edited copy of a member (4 corresponding lines) src/bridge/handler.rs
- Code Duplication · Duplicated block (20 lines × 2) src/renderer/mod.rs
- Code Duplication · Duplicated block (14–18 lines × 2) src/window/application/mod.rs
- Code Duplication · Duplicated block (11–12 lines × 2) src/renderer/grid_renderer.rs
- Code Duplication · Duplicated block (7 lines × 2) src/renderer/rendered_window.rs
- Code Coverage · Low coverage: neovide-derive/src/lib.rs neovide-derive/src/lib.rs
- Code Coverage · Low coverage: src/bridge/api_info.rs src/bridge/api_info.rs
- Code Coverage · Low coverage: src/bridge/clipboard.rs src/bridge/clipboard.rs
- Code Coverage · Low coverage: src/bridge/events.rs src/bridge/events.rs
- Code Coverage · Low coverage: src/bridge/handler.rs src/bridge/handler.rs
- Code Coverage · Low coverage: src/bridge/mod.rs src/bridge/mod.rs
- Code Coverage · Low coverage: src/bridge/session.rs src/bridge/session.rs
- Code Coverage · Low coverage: src/bridge/setup.rs src/bridge/setup.rs
- Code Coverage · Low coverage: src/bridge/ui_commands.rs src/bridge/ui_commands.rs
- Code Coverage · Low coverage: src/channel_utils.rs src/channel_utils.rs
- Code Coverage · Low coverage: src/dimensions.rs src/dimensions.rs
- Code Coverage · Low coverage: src/editor/draw_command_batcher.rs src/editor/draw_command_batcher.rs
- Code Coverage · Low coverage: src/editor/intro.rs src/editor/intro.rs
- Code Coverage · Low coverage: src/editor/mod.rs src/editor/mod.rs
- Code Coverage · Low coverage: src/editor/window.rs src/editor/window.rs
- Code Coverage · Low coverage: src/errors/mod.rs src/errors/mod.rs
- Code Coverage · Low coverage: src/main.rs src/main.rs
- Code Coverage · Low coverage: src/profiling/profiling_disabled.rs src/profiling/profiling_disabled.rs
- Code Coverage · Low coverage: src/renderer/box_drawing/renderer.rs src/renderer/box_drawing/renderer.rs
- Code Coverage · Low coverage: src/renderer/box_drawing/settings.rs src/renderer/box_drawing/settings.rs
- Code Coverage · Low coverage: src/renderer/cursor_renderer/blink.rs src/renderer/cursor_renderer/blink.rs
- Code Coverage · Low coverage: src/renderer/cursor_renderer/cursor_vfx.rs src/renderer/cursor_renderer/cursor_vfx.rs
- Code Coverage · Low coverage: src/renderer/cursor_renderer/mod.rs src/renderer/cursor_renderer/mod.rs
- Code Coverage · Low coverage: src/renderer/grid_renderer.rs src/renderer/grid_renderer.rs
- Code Coverage · Low coverage: src/renderer/opengl.rs src/renderer/opengl.rs
- Code Coverage · Low coverage: src/renderer/profiler.rs src/renderer/profiler.rs
- Code Coverage · Low coverage: src/renderer/progress_bar.rs src/renderer/progress_bar.rs
- Code Coverage · Low coverage: src/renderer/vsync/mod.rs src/renderer/vsync/mod.rs
- Code Coverage · Low coverage: src/renderer/vsync/vsync_timer.rs src/renderer/vsync/vsync_timer.rs
- Code Coverage · Low coverage: src/running_tracker.rs src/running_tracker.rs
- Code Coverage · Low coverage: src/settings/config.rs src/settings/config.rs
- Code Coverage · Low coverage: src/settings/mod.rs src/settings/mod.rs
- Code Coverage · Low coverage: src/settings/window_size.rs src/settings/window_size.rs
- Code Coverage · Low coverage: src/units.rs src/units.rs
- Code Coverage · Low coverage: src/window/application/linux.rs src/window/application/linux.rs
- Code Coverage · Low coverage: src/window/application/mod.rs src/window/application/mod.rs
- Code Coverage · Low coverage: src/window/error_window.rs src/window/error_window.rs
- Code Coverage · Low coverage: src/window/events.rs src/window/events.rs
- Code Coverage · Low coverage: src/window/keyboard_manager.rs src/window/keyboard_manager.rs
- Code Coverage · Low coverage: src/window/mouse_manager.rs src/window/mouse_manager.rs
- Code Coverage · Low coverage: src/window/setup/linux.rs src/window/setup/linux.rs
- Code Coverage · Low coverage: src/window/setup/mod.rs src/window/setup/mod.rs
- Code Coverage · Low coverage: src/window/wrapper/linux.rs src/window/wrapper/linux.rs
- Code Coverage · Low coverage: src/window/wrapper/mod.rs src/window/wrapper/mod.rs
- Churn × Complexity Hotspots · Hotspot: src/window/application/mod.rs src/window/application/mod.rs
- Churn × Complexity Hotspots · Hotspot: src/bridge/handler.rs src/bridge/handler.rs
- Churn × Complexity Hotspots · Repeated repair: src/bridge/session.rs src/bridge/session.rs
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 14 findings
- Code Duplication · Duplicated block (19 lines × 2) src/renderer/mod.rs
- Code Duplication · Duplicated block (14–18 lines × 2) src/window/application/mod.rs
- Code Duplication · Duplicated block (11–12 lines × 2) src/renderer/grid_renderer.rs
- Code Duplication · Duplicated block (7 lines × 2) src/renderer/rendered_window.rs
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium advisory (unmaintained): RUSTSEC-2024-0436 REDACTED
- Dependency Vulnerabilities · Medium advisory (unmaintained): RUSTSEC-2026-0058 REDACTED
- Dependency Vulnerabilities · Medium advisory (unsound): RUSTSEC-2026-0097 REDACTED
- Dependency Vulnerabilities · Medium advisory (unsound): RUSTSEC-2026-0097 REDACTED
- Dependency Vulnerabilities · Medium advisory (unsound): RUSTSEC-2026-0386 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
- Supply-chain Provenance & Signing · REDACTED REDACTED
- Supply-chain Provenance & Signing · REDACTED REDACTED
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €40,000 · Estimate
| Cost to rebuild | €13,000 to €67,000, for 224 to 709 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 65. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 34,242 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 clipboard | 2 editor.style | 3 renderer.box_drawing.renderer | 4 running_tracker | 5 settings.config | 6 settings.from_value | 7 units | 8 bridge.events | 9 editor.cursor | 10 editor.draw_command_batcher | 11 renderer.fonts.font_options | 12 window.setup | 13 bridge.handler | 14 renderer.fonts.font_loader | 15 bridge.ui_commands | 16 editor | 17 renderer.fonts.caching_shaper | 18 renderer.grid_renderer | 19 renderer.cursor_renderer.cursor_vfx | 20 renderer.rendered_window | 21 editor.window | 22 editor.scrollbar | 23 renderer.vsync | 24 window.mouse_manager | 25 window.wrapper.macos.scrollbar | 26 window.wrapper.macos.scrollbar.state | 27 window.wrapper.macos.feature | 28 window.wrapper.macos | 29 window.wrapper | 30 window.application | 31 renderer.cursor_renderer | 32 renderer | 33 window.events | 34 settings | 35 cmd_line | 36 renderer.d3d | 37 renderer.metal | 38 renderer.opengl | 39 bridge.command | 40 bridge |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 clipboard | ||||||||||||||||||||||||||||||||||||||||
| 2 editor.style | ||||||||||||||||||||||||||||||||||||||||
| 3 renderer.box_drawing.renderer | ||||||||||||||||||||||||||||||||||||||||
| 4 running_tracker | ||||||||||||||||||||||||||||||||||||||||
| 5 settings.config | ||||||||||||||||||||||||||||||||||||||||
| 6 settings.from_value | ||||||||||||||||||||||||||||||||||||||||
| 7 units | ||||||||||||||||||||||||||||||||||||||||
| 8 bridge.events | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 editor.cursor | 2 | |||||||||||||||||||||||||||||||||||||||
| 10 editor.draw_command_batcher | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 renderer.fonts.font_options | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 window.setup | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 bridge.handler | 2 | 2 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 14 renderer.fonts.font_loader | 6 | |||||||||||||||||||||||||||||||||||||||
| 15 bridge.ui_commands | 1 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 16 editor | 1 | 1 | 5 | 2 | 1 | 1 | 2 | 1 | 3 | 2 | ||||||||||||||||||||||||||||||
| 17 renderer.fonts.caching_shaper | 4 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 renderer.grid_renderer | 2 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 19 renderer.cursor_renderer.cursor_vfx | 2 | 3 | 3 | 3 | ||||||||||||||||||||||||||||||||||||
| 20 renderer.rendered_window | 2 | 1 | 1 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 21 editor.window | 3 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 22 editor.scrollbar | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 23 renderer.vsync | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 window.mouse_manager | 1 | 1 | 1 | 4 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 25 window.wrapper.macos.scrollbar | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 window.wrapper.macos.scrollbar.state | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 27 window.wrapper.macos.feature | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 28 window.wrapper.macos | 1 | 1 | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 29 window.wrapper | 1 | 2 | 1 | 2 | 1 | 2 | 4 | 1 | 1 | 3 | 2 | 5 | 1 | 3 | 10 | 1 | 2 | 1 | 2 | |||||||||||||||||||||
| 30 window.application | 2 | 1 | 2 | 1 | 1 | 1 | 4 | 1 | 1 | |||||||||||||||||||||||||||||||
| 31 renderer.cursor_renderer | 2 | 2 | 2 | 2 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 32 renderer | 2 | 2 | 4 | 1 | 1 | 1 | 2 | 2 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||
| 33 window.events | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 settings | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 cmd_line | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 renderer.d3d | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 renderer.metal | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 38 renderer.opengl | 2 | 1 | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||||
| 39 bridge.command | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 bridge | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 |
8→33 bridge.events uses window.events part of a loop✕
- Connections
- 1 pair of types, where a type in bridge.events uses a type in window.events.
- The types involved
neovide.bridge.events.events$module→neovide.window.events.UserEvent
- Direction
- bridge.events uses window.events, so a change to window.events can break bridge.events, while a change to bridge.events can't break window.events.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→2 editor.cursor uses editor.style✕
- Connections
- 2 pairs of types, where a type in editor.cursor uses a type in editor.style.
- The types involved
neovide.editor.cursor.Cursor→neovide.editor.style.Colorsneovide.editor.cursor.Cursor→neovide.editor.style.Style
- Direction
- editor.cursor uses editor.style, so a change to editor.style can break editor.cursor, while a change to editor.cursor can't break editor.style.
- Position
- Below the diagonal: editor.cursor uses a module listed above it, which is the healthy direction.
10→32 editor.draw_command_batcher uses renderer part of a loop✕
- Connections
- 1 pair of types, where a type in editor.draw_command_batcher uses a type in renderer.
- The types involved
neovide.editor.draw_command_batcher.DrawCommandBatcher→neovide.renderer.DrawCommand
- Direction
- editor.draw_command_batcher uses renderer, so a change to renderer can break editor.draw_command_batcher, while a change to editor.draw_command_batcher can't break renderer.
- 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.
11→2 renderer.fonts.font_options uses editor.style✕
- Connections
- 1 pair of types, where a type in renderer.fonts.font_options uses a type in editor.style.
- The types involved
neovide.renderer.fonts.font_options.CoarseStyle→neovide.editor.style.Style
- Direction
- renderer.fonts.font_options uses editor.style, so a change to editor.style can break renderer.fonts.font_options, while a change to renderer.fonts.font_options can't break editor.style.
- Position
- Below the diagonal: renderer.fonts.font_options uses a module listed above it, which is the healthy direction.
11→6 renderer.fonts.font_options uses settings.from_value✕
- Connections
- 1 pair of types, where a type in renderer.fonts.font_options uses a type in settings.from_value.
- The types involved
neovide.renderer.fonts.font_options.PixelGeometry→neovide.settings.from_value.ParseFromValue
- Direction
- renderer.fonts.font_options uses settings.from_value, so a change to settings.from_value can break renderer.fonts.font_options, while a change to renderer.fonts.font_options can't break settings.from_value.
- Position
- Below the diagonal: renderer.fonts.font_options uses a module listed above it, which is the healthy direction.
12→32 window.setup uses renderer part of a loop✕
- Connections
- 1 pair of types, where a type in window.setup uses a type in renderer.
- The types involved
neovide.window.setup.setup$module→neovide.renderer.WindowConfig
- Direction
- window.setup uses renderer, so a change to renderer can break window.setup, while a change to window.setup can't break renderer.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→34 window.setup uses settings part of a loop✕
- Connections
- 1 pair of types, where a type in window.setup uses a type in settings.
- The types involved
neovide.window.setup.setup$module→neovide.settings.Settings
- Direction
- window.setup uses settings, so a change to settings can break window.setup, while a change to window.setup can't break settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→1 bridge.handler uses clipboard✕
- Connections
- 2 pairs of types, where a type in bridge.handler uses a type in clipboard.
- The types involved
neovide.bridge.handler.NeovimHandler→neovide.clipboard.ClipboardHandleneovide.bridge.handler.handler$module→neovide.clipboard.ClipboardHandle
- Direction
- bridge.handler uses clipboard, so a change to clipboard can break bridge.handler, while a change to bridge.handler can't break clipboard.
- Position
- Below the diagonal: bridge.handler uses a module listed above it, which is the healthy direction.
13→4 bridge.handler uses running_tracker✕
- Connections
- 2 pairs of types, where a type in bridge.handler uses a type in running_tracker.
- The types involved
neovide.bridge.handler.NeovimHandler→neovide.running_tracker.RunningTrackerneovide.bridge.handler.handler$module→neovide.running_tracker.RunningTracker
- Direction
- bridge.handler uses running_tracker, so a change to running_tracker can break bridge.handler, while a change to bridge.handler can't break running_tracker.
- Position
- Below the diagonal: bridge.handler uses a module listed above it, which is the healthy direction.
13→8 bridge.handler uses bridge.events✕
- Connections
- 2 pairs of types, where a type in bridge.handler uses a type in bridge.events.
- The types involved
neovide.bridge.handler.NeovimHandler→neovide.bridge.events.RedrawEventneovide.bridge.handler.handler$module→neovide.bridge.events.RedrawEvent
- Direction
- bridge.handler uses bridge.events, so a change to bridge.events can break bridge.handler, while a change to bridge.handler can't break bridge.events.
- Position
- Below the diagonal: bridge.handler uses a module listed above it, which is the healthy direction.
13→33 bridge.handler uses window.events part of a loop✕
- Connections
- 2 pairs of types, where a type in bridge.handler uses a type in window.events.
- The types involved
neovide.bridge.handler.NeovimHandler→neovide.window.events.RouteIdneovide.bridge.handler.NeovimHandler→neovide.window.events.WindowCommand
- Direction
- bridge.handler uses window.events, so a change to window.events can break bridge.handler, while a change to bridge.handler can't break window.events.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→34 bridge.handler uses settings part of a loop✕
- Connections
- 2 pairs of types, where a type in bridge.handler uses a type in settings.
- The types involved
neovide.bridge.handler.NeovimHandler→neovide.settings.Settingsneovide.bridge.handler.handler$module→neovide.settings.Settings
- Direction
- bridge.handler uses settings, so a change to settings can break bridge.handler, while a change to bridge.handler can't break settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→11 renderer.fonts.font_loader uses renderer.fonts.font_options✕
- Connections
- 6 pairs of types, where a type in renderer.fonts.font_loader uses a type in renderer.fonts.font_options.
- The types involved
neovide.renderer.fonts.font_loader.FontKey→neovide.renderer.fonts.font_options.FontDescriptionneovide.renderer.fonts.font_loader.FontKey→neovide.renderer.fonts.font_options.FontEdgingneovide.renderer.fonts.font_loader.FontKey→neovide.renderer.fonts.font_options.FontHintingneovide.renderer.fonts.font_loader.FontLoader→neovide.renderer.fonts.font_options.CoarseStyleneovide.renderer.fonts.font_loader.font_loader$module→neovide.renderer.fonts.font_options.FontEdgingneovide.renderer.fonts.font_loader.font_loader$module→neovide.renderer.fonts.font_options.FontHinting
- Direction
- renderer.fonts.font_loader uses renderer.fonts.font_options, so a change to renderer.fonts.font_options can break renderer.fonts.font_loader, while a change to renderer.fonts.font_loader can't break renderer.fonts.font_options.
- Position
- Below the diagonal: renderer.fonts.font_loader uses a module listed above it, which is the healthy direction.
15→8 bridge.ui_commands uses bridge.events✕
- Connections
- 1 pair of types, where a type in bridge.ui_commands uses a type in bridge.events.
- The types involved
neovide.bridge.ui_commands.ui_commands$module→neovide.bridge.events.StartupMessage
- Direction
- bridge.ui_commands uses bridge.events, so a change to bridge.events can break bridge.ui_commands, while a change to bridge.ui_commands can't break bridge.events.
- Position
- Below the diagonal: bridge.ui_commands uses a module listed above it, which is the healthy direction.
15→13 bridge.ui_commands uses bridge.handler✕
- Connections
- 2 pairs of types, where a type in bridge.ui_commands uses a type in bridge.handler.
- The types involved
neovide.bridge.ui_commands.ParallelCommand→neovide.bridge.handler.NeovimHandlerneovide.bridge.ui_commands.ui_commands$module→neovide.bridge.handler.NeovimHandler
- Direction
- bridge.ui_commands uses bridge.handler, so a change to bridge.handler can break bridge.ui_commands, while a change to bridge.ui_commands can't break bridge.handler.
- Position
- Below the diagonal: bridge.ui_commands uses a module listed above it, which is the healthy direction.
15→33 bridge.ui_commands uses window.events part of a loop✕
- Connections
- 2 pairs of types, where a type in bridge.ui_commands uses a type in window.events.
- The types involved
neovide.bridge.ui_commands.HandlerRegistry→neovide.window.events.RouteIdneovide.bridge.ui_commands.ui_commands$module→neovide.window.events.RouteId
- Direction
- bridge.ui_commands uses window.events, so a change to window.events can break bridge.ui_commands, while a change to bridge.ui_commands can't break window.events.
- 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→34 bridge.ui_commands uses settings part of a loop✕
- Connections
- 2 pairs of types, where a type in bridge.ui_commands uses a type in settings.
- The types involved
neovide.bridge.ui_commands.ParallelCommand→neovide.settings.Settingsneovide.bridge.ui_commands.ui_commands$module→neovide.settings.Settings
- Direction
- bridge.ui_commands uses settings, so a change to settings can break bridge.ui_commands, while a change to bridge.ui_commands can't break settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→1 editor uses clipboard✕
- Connections
- 1 pair of types, where a type in editor uses a type in clipboard.
- The types involved
neovide.editor.editor$module→neovide.clipboard.ClipboardHandle
- Direction
- editor uses clipboard, so a change to clipboard can break editor, while a change to editor can't break clipboard.
- Position
- Below the diagonal: editor uses a module listed above it, which is the healthy direction.
16→4 editor uses running_tracker✕
- Connections
- 1 pair of types, where a type in editor uses a type in running_tracker.
- The types involved
neovide.editor.editor$module→neovide.running_tracker.RunningTracker
- Direction
- editor uses running_tracker, so a change to running_tracker can break editor, while a change to editor can't break running_tracker.
- Position
- Below the diagonal: editor uses a module listed above it, which is the healthy direction.
16→8 editor uses bridge.events✕
- Connections
- 5 pairs of types, where a type in editor uses a type in bridge.events.
- The types involved
neovide.editor.AnchorInfo→neovide.bridge.events.WindowAnchorneovide.editor.Editor→neovide.bridge.events.EditorModeneovide.editor.Editor→neovide.bridge.events.GuiOptionneovide.editor.Editor→neovide.bridge.events.MessageKindneovide.editor.Editor→neovide.bridge.events.RedrawEvent
- Direction
- editor uses bridge.events, so a change to bridge.events can break editor, while a change to editor can't break bridge.events.
- Position
- Below the diagonal: editor uses a module listed above it, which is the healthy direction.
16→9 editor uses editor.cursor✕
- Connections
- 2 pairs of types, where a type in editor uses a type in editor.cursor.
- The types involved
neovide.editor.Editor→neovide.editor.cursor.Cursorneovide.editor.Editor→neovide.editor.cursor.CursorMode
- Direction
- editor uses editor.cursor, so a change to editor.cursor can break editor, while a change to editor can't break editor.cursor.
- Position
- Below the diagonal: editor uses a module listed above it, which is the healthy direction.
16→10 editor uses editor.draw_command_batcher✕
- Connections
- 1 pair of types, where a type in editor uses a type in editor.draw_command_batcher.
- The types involved
neovide.editor.Editor→neovide.editor.draw_command_batcher.DrawCommandBatcher
- Direction
- editor uses editor.draw_command_batcher, so a change to editor.draw_command_batcher can break editor, while a change to editor can't break editor.draw_command_batcher.
- Position
- Below the diagonal: editor uses a module listed above it, which is the healthy direction.
16→13 editor uses bridge.handler✕
- Connections
- 1 pair of types, where a type in editor uses a type in bridge.handler.
- The types involved
neovide.editor.editor$module→neovide.bridge.handler.NeovimHandler
- Direction
- editor uses bridge.handler, so a change to bridge.handler can break editor, while a change to editor can't break bridge.handler.
- Position
- Below the diagonal: editor uses a module listed above it, which is the healthy direction.
16→21 editor uses editor.window part of a loop✕
- Connections
- 2 pairs of types, where a type in editor uses a type in editor.window.
- The types involved
neovide.editor.Editor→neovide.editor.window.TiledWindowLayoutneovide.editor.Editor→neovide.editor.window.WindowViewport
- Direction
- editor uses editor.window, so a change to editor.window can break editor, while a change to editor can't break editor.window.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→32 editor uses renderer part of a loop✕
- Connections
- 1 pair of types, where a type in editor uses a type in renderer.
- The types involved
neovide.editor.Editor→neovide.renderer.DrawCommand
- Direction
- editor uses renderer, so a change to renderer can break editor, while a change to editor can't break renderer.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→33 editor uses window.events part of a loop✕
- Connections
- 3 pairs of types, where a type in editor uses a type in window.events.
- The types involved
neovide.editor.Editor→neovide.window.events.RouteIdneovide.editor.Editor→neovide.window.events.WindowCommandneovide.editor.editor$module→neovide.window.events.RouteId
- Direction
- editor uses window.events, so a change to window.events can break editor, while a change to editor can't break window.events.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→34 editor uses settings part of a loop✕
- Connections
- 2 pairs of types, where a type in editor uses a type in settings.
- The types involved
neovide.editor.Editor→neovide.settings.Settingsneovide.editor.editor$module→neovide.settings.Settings
- Direction
- editor uses settings, so a change to settings can break editor, while a change to editor can't break settings.
- 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→11 renderer.fonts.caching_shaper uses renderer.fonts.font_options✕
- Connections
- 4 pairs of types, where a type in renderer.fonts.caching_shaper uses a type in renderer.fonts.font_options.
- The types involved
neovide.renderer.fonts.caching_shaper.CachingShaper→neovide.renderer.fonts.font_options.CoarseStyleneovide.renderer.fonts.caching_shaper.CachingShaper→neovide.renderer.fonts.font_options.FontOptionsneovide.renderer.fonts.caching_shaper.ShapeKey→neovide.renderer.fonts.font_options.CoarseStyleneovide.renderer.fonts.caching_shaper.caching_shaper$module→neovide.renderer.fonts.font_options.FontOptions
- Direction
- renderer.fonts.caching_shaper uses renderer.fonts.font_options, so a change to renderer.fonts.font_options can break renderer.fonts.caching_shaper, while a change to renderer.fonts.caching_shaper can't break renderer.fonts.font_options.
- Position
- Below the diagonal: renderer.fonts.caching_shaper uses a module listed above it, which is the healthy direction.
17→14 renderer.fonts.caching_shaper uses renderer.fonts.font_loader✕
- Connections
- 2 pairs of types, where a type in renderer.fonts.caching_shaper uses a type in renderer.fonts.font_loader.
- The types involved
neovide.renderer.fonts.caching_shaper.CachingShaper→neovide.renderer.fonts.font_loader.FontLoaderneovide.renderer.fonts.caching_shaper.CachingShaper→neovide.renderer.fonts.font_loader.FontPair
- Direction
- renderer.fonts.caching_shaper uses renderer.fonts.font_loader, so a change to renderer.fonts.font_loader can break renderer.fonts.caching_shaper, while a change to renderer.fonts.caching_shaper can't break renderer.fonts.font_loader.
- Position
- Below the diagonal: renderer.fonts.caching_shaper uses a module listed above it, which is the healthy direction.
17→21 renderer.fonts.caching_shaper uses editor.window part of a loop✕
- Connections
- 1 pair of types, where a type in renderer.fonts.caching_shaper uses a type in editor.window.
- The types involved
neovide.renderer.fonts.caching_shaper.CachingShaper→neovide.editor.window.Word
- Direction
- renderer.fonts.caching_shaper uses editor.window, so a change to editor.window can break renderer.fonts.caching_shaper, while a change to renderer.fonts.caching_shaper can't break editor.window.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→2 renderer.grid_renderer uses editor.style✕
- Connections
- 2 pairs of types, where a type in renderer.grid_renderer uses a type in editor.style.
- The types involved
neovide.renderer.grid_renderer.GridRenderer→neovide.editor.style.Styleneovide.renderer.grid_renderer.GridRenderer→neovide.editor.style.UnderlineStyle
- Direction
- renderer.grid_renderer uses editor.style, so a change to editor.style can break renderer.grid_renderer, while a change to renderer.grid_renderer can't break editor.style.
- Position
- Below the diagonal: renderer.grid_renderer uses a module listed above it, which is the healthy direction.
18→3 renderer.grid_renderer uses renderer.box_drawing.renderer✕
- Connections
- 1 pair of types, where a type in renderer.grid_renderer uses a type in renderer.box_drawing.renderer.
- The types involved
neovide.renderer.grid_renderer.GridRenderer→neovide.renderer.box_drawing.renderer.Renderer
- Direction
- renderer.grid_renderer uses renderer.box_drawing.renderer, so a change to renderer.box_drawing.renderer can break renderer.grid_renderer, while a change to renderer.grid_renderer can't break renderer.box_drawing.renderer.
- Position
- Below the diagonal: renderer.grid_renderer uses a module listed above it, which is the healthy direction.
18→7 renderer.grid_renderer uses units✕
- Connections
- 1 pair of types, where a type in renderer.grid_renderer uses a type in units.
- The types involved
neovide.renderer.grid_renderer.GridRenderer→neovide.units.GridScale
- Direction
- renderer.grid_renderer uses units, so a change to units can break renderer.grid_renderer, while a change to renderer.grid_renderer can't break units.
- Position
- Below the diagonal: renderer.grid_renderer uses a module listed above it, which is the healthy direction.
18→11 renderer.grid_renderer uses renderer.fonts.font_options✕
- Connections
- 1 pair of types, where a type in renderer.grid_renderer uses a type in renderer.fonts.font_options.
- The types involved
neovide.renderer.grid_renderer.GridRenderer→neovide.renderer.fonts.font_options.FontOptions
- Direction
- renderer.grid_renderer uses renderer.fonts.font_options, so a change to renderer.fonts.font_options can break renderer.grid_renderer, while a change to renderer.grid_renderer can't break renderer.fonts.font_options.
- Position
- Below the diagonal: renderer.grid_renderer uses a module listed above it, which is the healthy direction.
18→17 renderer.grid_renderer uses renderer.fonts.caching_shaper✕
- Connections
- 1 pair of types, where a type in renderer.grid_renderer uses a type in renderer.fonts.caching_shaper.
- The types involved
neovide.renderer.grid_renderer.GridRenderer→neovide.renderer.fonts.caching_shaper.CachingShaper
- Direction
- renderer.grid_renderer uses renderer.fonts.caching_shaper, so a change to renderer.fonts.caching_shaper can break renderer.grid_renderer, while a change to renderer.grid_renderer can't break renderer.fonts.caching_shaper.
- Position
- Below the diagonal: renderer.grid_renderer uses a module listed above it, which is the healthy direction.
18→21 renderer.grid_renderer uses editor.window part of a loop✕
- Connections
- 1 pair of types, where a type in renderer.grid_renderer uses a type in editor.window.
- The types involved
neovide.renderer.grid_renderer.GridRenderer→neovide.editor.window.LineFragment
- Direction
- renderer.grid_renderer uses editor.window, so a change to editor.window can break renderer.grid_renderer, while a change to renderer.grid_renderer can't break editor.window.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→34 renderer.grid_renderer uses settings part of a loop✕
- Connections
- 1 pair of types, where a type in renderer.grid_renderer uses a type in settings.
- The types involved
neovide.renderer.grid_renderer.GridRenderer→neovide.settings.Settings
- Direction
- renderer.grid_renderer uses settings, so a change to settings can break renderer.grid_renderer, while a change to renderer.grid_renderer can't break settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→6 renderer.cursor_renderer.cursor_vfx uses settings.from_value✕
- Connections
- 2 pairs of types, where a type in renderer.cursor_renderer.cursor_vfx uses a type in settings.from_value.
- The types involved
neovide.renderer.cursor_renderer.cursor_vfx.VfxMode→neovide.settings.from_value.ParseFromValueneovide.renderer.cursor_renderer.cursor_vfx.VfxModeList→neovide.settings.from_value.ParseFromValue
- Direction
- renderer.cursor_renderer.cursor_vfx uses settings.from_value, so a change to settings.from_value can break renderer.cursor_renderer.cursor_vfx, while a change to renderer.cursor_renderer.cursor_vfx can't break settings.from_value.
- Position
- Below the diagonal: renderer.cursor_renderer.cursor_vfx uses a module listed above it, which is the healthy direction.
19→9 renderer.cursor_renderer.cursor_vfx uses editor.cursor✕
- Connections
- 3 pairs of types, where a type in renderer.cursor_renderer.cursor_vfx uses a type in editor.cursor.
- The types involved
neovide.renderer.cursor_renderer.cursor_vfx.CursorVfx→neovide.editor.cursor.Cursorneovide.renderer.cursor_renderer.cursor_vfx.ParticleTrail→neovide.editor.cursor.Cursorneovide.renderer.cursor_renderer.cursor_vfx.PointHighlight→neovide.editor.cursor.Cursor
- Direction
- renderer.cursor_renderer.cursor_vfx uses editor.cursor, so a change to editor.cursor can break renderer.cursor_renderer.cursor_vfx, while a change to renderer.cursor_renderer.cursor_vfx can't break editor.cursor.
- Position
- Below the diagonal: renderer.cursor_renderer.cursor_vfx uses a module listed above it, which is the healthy direction.
19→18 renderer.cursor_renderer.cursor_vfx uses renderer.grid_renderer✕
- Connections
- 3 pairs of types, where a type in renderer.cursor_renderer.cursor_vfx uses a type in renderer.grid_renderer.
- The types involved
neovide.renderer.cursor_renderer.cursor_vfx.CursorVfx→neovide.renderer.grid_renderer.GridRendererneovide.renderer.cursor_renderer.cursor_vfx.ParticleTrail→neovide.renderer.grid_renderer.GridRendererneovide.renderer.cursor_renderer.cursor_vfx.PointHighlight→neovide.renderer.grid_renderer.GridRenderer
- Direction
- renderer.cursor_renderer.cursor_vfx uses renderer.grid_renderer, so a change to renderer.grid_renderer can break renderer.cursor_renderer.cursor_vfx, while a change to renderer.cursor_renderer.cursor_vfx can't break renderer.grid_renderer.
- Position
- Below the diagonal: renderer.cursor_renderer.cursor_vfx uses a module listed above it, which is the healthy direction.
19→31 renderer.cursor_renderer.cursor_vfx uses renderer.cursor_renderer part of a loop✕
- Connections
- 3 pairs of types, where a type in renderer.cursor_renderer.cursor_vfx uses a type in renderer.cursor_renderer.
- The types involved
neovide.renderer.cursor_renderer.cursor_vfx.CursorVfx→neovide.renderer.cursor_renderer.CursorSettingsneovide.renderer.cursor_renderer.cursor_vfx.ParticleTrail→neovide.renderer.cursor_renderer.CursorSettingsneovide.renderer.cursor_renderer.cursor_vfx.PointHighlight→neovide.renderer.cursor_renderer.CursorSettings
- Direction
- renderer.cursor_renderer.cursor_vfx uses renderer.cursor_renderer, so a change to renderer.cursor_renderer can break renderer.cursor_renderer.cursor_vfx, while a change to renderer.cursor_renderer.cursor_vfx can't break renderer.cursor_renderer.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→7 renderer.rendered_window uses units✕
- Connections
- 2 pairs of types, where a type in renderer.rendered_window uses a type in units.
- The types involved
neovide.renderer.rendered_window.BottomFillArea→neovide.units.GridScaleneovide.renderer.rendered_window.RenderedWindow→neovide.units.GridScale
- Direction
- renderer.rendered_window uses units, so a change to units can break renderer.rendered_window, while a change to renderer.rendered_window can't break units.
- Position
- Below the diagonal: renderer.rendered_window uses a module listed above it, which is the healthy direction.
20→16 renderer.rendered_window uses editor✕
- Connections
- 1 pair of types, where a type in renderer.rendered_window uses a type in editor.
- The types involved
neovide.renderer.rendered_window.RenderedWindow→neovide.editor.AnchorInfo
- Direction
- renderer.rendered_window uses editor, so a change to editor can break renderer.rendered_window, while a change to renderer.rendered_window can't break editor.
- Position
- Below the diagonal: renderer.rendered_window uses a module listed above it, which is the healthy direction.
20→18 renderer.rendered_window uses renderer.grid_renderer✕
- Connections
- 1 pair of types, where a type in renderer.rendered_window uses a type in renderer.grid_renderer.
- The types involved
neovide.renderer.rendered_window.RenderedWindow→neovide.renderer.grid_renderer.GridRenderer
- Direction
- renderer.rendered_window uses renderer.grid_renderer, so a change to renderer.grid_renderer can break renderer.rendered_window, while a change to renderer.rendered_window can't break renderer.grid_renderer.
- Position
- Below the diagonal: renderer.rendered_window uses a module listed above it, which is the healthy direction.
20→21 renderer.rendered_window uses editor.window part of a loop✕
- Connections
- 3 pairs of types, where a type in renderer.rendered_window uses a type in editor.window.
- The types involved
neovide.renderer.rendered_window.RenderedLine→neovide.editor.window.Lineneovide.renderer.rendered_window.RenderedWindow→neovide.editor.window.WindowTypeneovide.renderer.rendered_window.WindowDrawDetails→neovide.editor.window.WindowType
- Direction
- renderer.rendered_window uses editor.window, so a change to editor.window can break renderer.rendered_window, while a change to renderer.rendered_window can't break editor.window.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→32 renderer.rendered_window uses renderer part of a loop✕
- Connections
- 1 pair of types, where a type in renderer.rendered_window uses a type in renderer.
- The types involved
neovide.renderer.rendered_window.RenderedWindow→neovide.renderer.RendererSettings
- Direction
- renderer.rendered_window uses renderer, so a change to renderer can break renderer.rendered_window, while a change to renderer.rendered_window can't break renderer.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→34 renderer.rendered_window uses settings part of a loop✕
- Connections
- 1 pair of types, where a type in renderer.rendered_window uses a type in settings.
- The types involved
neovide.renderer.rendered_window.WindowDrawDetails→neovide.settings.Settings
- Direction
- renderer.rendered_window uses settings, so a change to settings can break renderer.rendered_window, while a change to renderer.rendered_window can't break settings.
- 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→2 editor.window uses editor.style✕
- Connections
- 3 pairs of types, where a type in editor.window uses a type in editor.style.
- The types involved
neovide.editor.window.LineFragment→neovide.editor.style.Styleneovide.editor.window.LineFragmentData→neovide.editor.style.Styleneovide.editor.window.Window→neovide.editor.style.Style
- Direction
- editor.window uses editor.style, so a change to editor.style can break editor.window, while a change to editor.window can't break editor.style.
- Position
- Below the diagonal: editor.window uses a module listed above it, which is the healthy direction.
21→8 editor.window uses bridge.events✕
- Connections
- 1 pair of types, where a type in editor.window uses a type in bridge.events.
- The types involved
neovide.editor.window.Window→neovide.bridge.events.GridLineCell
- Direction
- editor.window uses bridge.events, so a change to bridge.events can break editor.window, while a change to editor.window can't break bridge.events.
- Position
- Below the diagonal: editor.window uses a module listed above it, which is the healthy direction.
21→10 editor.window uses editor.draw_command_batcher✕
- Connections
- 1 pair of types, where a type in editor.window uses a type in editor.draw_command_batcher.
- The types involved
neovide.editor.window.Window→neovide.editor.draw_command_batcher.DrawCommandBatcher
- Direction
- editor.window uses editor.draw_command_batcher, so a change to editor.draw_command_batcher can break editor.window, while a change to editor.window can't break editor.draw_command_batcher.
- Position
- Below the diagonal: editor.window uses a module listed above it, which is the healthy direction.
21→16 editor.window uses editor✕
- Connections
- 1 pair of types, where a type in editor.window uses a type in editor.
- The types involved
neovide.editor.window.Window→neovide.editor.AnchorInfo
- Direction
- editor.window uses editor, so a change to editor can break editor.window, while a change to editor.window can't break editor.
- Position
- Below the diagonal: editor.window uses a module listed above it, which is the healthy direction.
21→20 editor.window uses renderer.rendered_window✕
- Connections
- 1 pair of types, where a type in editor.window uses a type in renderer.rendered_window.
- The types involved
neovide.editor.window.Window→neovide.renderer.rendered_window.WindowDrawCommand
- Direction
- editor.window uses renderer.rendered_window, so a change to renderer.rendered_window can break editor.window, while a change to editor.window can't break renderer.rendered_window.
- Position
- Below the diagonal: editor.window uses a module listed above it, which is the healthy direction.
22→8 editor.scrollbar uses bridge.events✕
- Connections
- 2 pairs of types, where a type in editor.scrollbar uses a type in bridge.events.
- The types involved
neovide.editor.scrollbar.ScrollbarGrid→neovide.bridge.events.ScrollbarWindowMetadataneovide.editor.scrollbar.scrollbar$module→neovide.bridge.events.ScrollbarWindowMetadata
- Direction
- editor.scrollbar uses bridge.events, so a change to bridge.events can break editor.scrollbar, while a change to editor.scrollbar can't break bridge.events.
- Position
- Below the diagonal: editor.scrollbar uses a module listed above it, which is the healthy direction.
22→21 editor.scrollbar uses editor.window✕
- Connections
- 2 pairs of types, where a type in editor.scrollbar uses a type in editor.window.
- The types involved
neovide.editor.scrollbar.ScrollbarGrid→neovide.editor.window.TiledWindowLayoutneovide.editor.scrollbar.ScrollbarGrid→neovide.editor.window.WindowViewport
- Direction
- editor.scrollbar uses editor.window, so a change to editor.window can break editor.scrollbar, while a change to editor.scrollbar can't break editor.window.
- Position
- Below the diagonal: editor.scrollbar uses a module listed above it, which is the healthy direction.
23→21 renderer.vsync uses editor.window✕
- Connections
- 1 pair of types, where a type in renderer.vsync uses a type in editor.window.
- The types involved
neovide.renderer.vsync.VSync→neovide.editor.window.Window
- Direction
- renderer.vsync uses editor.window, so a change to editor.window can break renderer.vsync, while a change to renderer.vsync can't break editor.window.
- Position
- Below the diagonal: renderer.vsync uses a module listed above it, which is the healthy direction.
23→34 renderer.vsync uses settings part of a loop✕
- Connections
- 1 pair of types, where a type in renderer.vsync uses a type in settings.
- The types involved
neovide.renderer.vsync.VSync→neovide.settings.Settings
- Direction
- renderer.vsync uses settings, so a change to settings can break renderer.vsync, while a change to renderer.vsync can't break settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→3 window.mouse_manager uses renderer.box_drawing.renderer✕
- Connections
- 1 pair of types, where a type in window.mouse_manager uses a type in renderer.box_drawing.renderer.
- The types involved
neovide.window.mouse_manager.MouseManager→neovide.renderer.box_drawing.renderer.Renderer
- Direction
- window.mouse_manager uses renderer.box_drawing.renderer, so a change to renderer.box_drawing.renderer can break window.mouse_manager, while a change to window.mouse_manager can't break renderer.box_drawing.renderer.
- Position
- Below the diagonal: window.mouse_manager uses a module listed above it, which is the healthy direction.
24→7 window.mouse_manager uses units✕
- Connections
- 1 pair of types, where a type in window.mouse_manager uses a type in units.
- The types involved
neovide.window.mouse_manager.EditorState→neovide.units.GridScale
- Direction
- window.mouse_manager uses units, so a change to units can break window.mouse_manager, while a change to window.mouse_manager can't break units.
- Position
- Below the diagonal: window.mouse_manager uses a module listed above it, which is the healthy direction.
24→13 window.mouse_manager uses bridge.handler✕
- Connections
- 1 pair of types, where a type in window.mouse_manager uses a type in bridge.handler.
- The types involved
neovide.window.mouse_manager.MouseManager→neovide.bridge.handler.NeovimHandler
- Direction
- window.mouse_manager uses bridge.handler, so a change to bridge.handler can break window.mouse_manager, while a change to window.mouse_manager can't break bridge.handler.
- Position
- Below the diagonal: window.mouse_manager uses a module listed above it, which is the healthy direction.
24→20 window.mouse_manager uses renderer.rendered_window✕
- Connections
- 4 pairs of types, where a type in window.mouse_manager uses a type in renderer.rendered_window.
- The types involved
neovide.window.mouse_manager.DragDetails→neovide.renderer.rendered_window.WindowDrawDetailsneovide.window.mouse_manager.EditorState→neovide.renderer.rendered_window.WindowDrawDetailsneovide.window.mouse_manager.MessageSelectionState→neovide.renderer.rendered_window.WindowDrawDetailsneovide.window.mouse_manager.MouseManager→neovide.renderer.rendered_window.WindowDrawDetails
- Direction
- window.mouse_manager uses renderer.rendered_window, so a change to renderer.rendered_window can break window.mouse_manager, while a change to window.mouse_manager can't break renderer.rendered_window.
- Position
- Below the diagonal: window.mouse_manager uses a module listed above it, which is the healthy direction.
24→21 window.mouse_manager uses editor.window✕
- Connections
- 2 pairs of types, where a type in window.mouse_manager uses a type in editor.window.
- The types involved
neovide.window.mouse_manager.EditorState→neovide.editor.window.Windowneovide.window.mouse_manager.MouseManager→neovide.editor.window.Window
- Direction
- window.mouse_manager uses editor.window, so a change to editor.window can break window.mouse_manager, while a change to window.mouse_manager can't break editor.window.
- Position
- Below the diagonal: window.mouse_manager uses a module listed above it, which is the healthy direction.
24→34 window.mouse_manager uses settings part of a loop✕
- Connections
- 1 pair of types, where a type in window.mouse_manager uses a type in settings.
- The types involved
neovide.window.mouse_manager.MouseManager→neovide.settings.Settings
- Direction
- window.mouse_manager uses settings, so a change to settings can break window.mouse_manager, while a change to window.mouse_manager can't break settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→3 window.wrapper.macos.scrollbar uses renderer.box_drawing.renderer✕
- Connections
- 1 pair of types, where a type in window.wrapper.macos.scrollbar uses a type in renderer.box_drawing.renderer.
- The types involved
neovide.window.wrapper.macos.scrollbar.WindowScrollbars→neovide.renderer.box_drawing.renderer.Renderer
- Direction
- window.wrapper.macos.scrollbar uses renderer.box_drawing.renderer, so a change to renderer.box_drawing.renderer can break window.wrapper.macos.scrollbar, while a change to window.wrapper.macos.scrollbar can't break renderer.box_drawing.renderer.
- Position
- Below the diagonal: window.wrapper.macos.scrollbar uses a module listed above it, which is the healthy direction.
25→13 window.wrapper.macos.scrollbar uses bridge.handler✕
- Connections
- 1 pair of types, where a type in window.wrapper.macos.scrollbar uses a type in bridge.handler.
- The types involved
neovide.window.wrapper.macos.scrollbar.WindowScrollbars→neovide.bridge.handler.NeovimHandler
- Direction
- window.wrapper.macos.scrollbar uses bridge.handler, so a change to bridge.handler can break window.wrapper.macos.scrollbar, while a change to window.wrapper.macos.scrollbar can't break bridge.handler.
- Position
- Below the diagonal: window.wrapper.macos.scrollbar uses a module listed above it, which is the healthy direction.
25→22 window.wrapper.macos.scrollbar uses editor.scrollbar✕
- Connections
- 1 pair of types, where a type in window.wrapper.macos.scrollbar uses a type in editor.scrollbar.
- The types involved
neovide.window.wrapper.macos.scrollbar.WindowScrollbars→neovide.editor.scrollbar.ScrollbarSnapshot
- Direction
- window.wrapper.macos.scrollbar uses editor.scrollbar, so a change to editor.scrollbar can break window.wrapper.macos.scrollbar, while a change to window.wrapper.macos.scrollbar can't break editor.scrollbar.
- Position
- Below the diagonal: window.wrapper.macos.scrollbar uses a module listed above it, which is the healthy direction.
25→34 window.wrapper.macos.scrollbar uses settings part of a loop✕
- Connections
- 1 pair of types, where a type in window.wrapper.macos.scrollbar uses a type in settings.
- The types involved
neovide.window.wrapper.macos.scrollbar.scrollbar$module→neovide.settings.Settings
- Direction
- window.wrapper.macos.scrollbar uses settings, so a change to settings can break window.wrapper.macos.scrollbar, while a change to window.wrapper.macos.scrollbar can't break settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→13 window.wrapper.macos.scrollbar.state uses bridge.handler✕
- Connections
- 2 pairs of types, where a type in window.wrapper.macos.scrollbar.state uses a type in bridge.handler.
- The types involved
neovide.window.wrapper.macos.scrollbar.state.ScrollbarGridState→neovide.bridge.handler.NeovimHandlerneovide.window.wrapper.macos.scrollbar.state.ScrollbarState→neovide.bridge.handler.NeovimHandler
- Direction
- window.wrapper.macos.scrollbar.state uses bridge.handler, so a change to bridge.handler can break window.wrapper.macos.scrollbar.state, while a change to window.wrapper.macos.scrollbar.state can't break bridge.handler.
- Position
- Below the diagonal: window.wrapper.macos.scrollbar.state uses a module listed above it, which is the healthy direction.
26→22 window.wrapper.macos.scrollbar.state uses editor.scrollbar✕
- Connections
- 3 pairs of types, where a type in window.wrapper.macos.scrollbar.state uses a type in editor.scrollbar.
- The types involved
neovide.window.wrapper.macos.scrollbar.state.ScrollbarGridState→neovide.editor.scrollbar.ScrollbarGridneovide.window.wrapper.macos.scrollbar.state.ScrollbarViewport→neovide.editor.scrollbar.ScrollbarGridneovide.window.wrapper.macos.scrollbar.state.state$module→neovide.editor.scrollbar.ScrollbarSnapshot
- Direction
- window.wrapper.macos.scrollbar.state uses editor.scrollbar, so a change to editor.scrollbar can break window.wrapper.macos.scrollbar.state, while a change to window.wrapper.macos.scrollbar.state can't break editor.scrollbar.
- Position
- Below the diagonal: window.wrapper.macos.scrollbar.state uses a module listed above it, which is the healthy direction.
27→3 window.wrapper.macos.feature uses renderer.box_drawing.renderer✕
- Connections
- 1 pair of types, where a type in window.wrapper.macos.feature uses a type in renderer.box_drawing.renderer.
- The types involved
neovide.window.wrapper.macos.feature.MacosWindowFeature→neovide.renderer.box_drawing.renderer.Renderer
- Direction
- window.wrapper.macos.feature uses renderer.box_drawing.renderer, so a change to renderer.box_drawing.renderer can break window.wrapper.macos.feature, while a change to window.wrapper.macos.feature can't break renderer.box_drawing.renderer.
- Position
- Below the diagonal: window.wrapper.macos.feature uses a module listed above it, which is the healthy direction.
27→13 window.wrapper.macos.feature uses bridge.handler✕
- Connections
- 1 pair of types, where a type in window.wrapper.macos.feature uses a type in bridge.handler.
- The types involved
neovide.window.wrapper.macos.feature.MacosWindowFeature→neovide.bridge.handler.NeovimHandler
- Direction
- window.wrapper.macos.feature uses bridge.handler, so a change to bridge.handler can break window.wrapper.macos.feature, while a change to window.wrapper.macos.feature can't break bridge.handler.
- Position
- Below the diagonal: window.wrapper.macos.feature uses a module listed above it, which is the healthy direction.
27→21 window.wrapper.macos.feature uses editor.window✕
- Connections
- 1 pair of types, where a type in window.wrapper.macos.feature uses a type in editor.window.
- The types involved
neovide.window.wrapper.macos.feature.MacosWindowFeature→neovide.editor.window.Window
- Direction
- window.wrapper.macos.feature uses editor.window, so a change to editor.window can break window.wrapper.macos.feature, while a change to window.wrapper.macos.feature can't break editor.window.
- Position
- Below the diagonal: window.wrapper.macos.feature uses a module listed above it, which is the healthy direction.
27→25 window.wrapper.macos.feature uses window.wrapper.macos.scrollbar✕
- Connections
- 1 pair of types, where a type in window.wrapper.macos.feature uses a type in window.wrapper.macos.scrollbar.
- The types involved
neovide.window.wrapper.macos.feature.MacosWindowFeature→neovide.window.wrapper.macos.scrollbar.WindowScrollbars
- Direction
- window.wrapper.macos.feature uses window.wrapper.macos.scrollbar, so a change to window.wrapper.macos.scrollbar can break window.wrapper.macos.feature, while a change to window.wrapper.macos.feature can't break window.wrapper.macos.scrollbar.
- Position
- Below the diagonal: window.wrapper.macos.feature uses a module listed above it, which is the healthy direction.
27→33 window.wrapper.macos.feature uses window.events part of a loop✕
- Connections
- 1 pair of types, where a type in window.wrapper.macos.feature uses a type in window.events.
- The types involved
neovide.window.wrapper.macos.feature.MacosWindowFeature→neovide.window.events.ForceClickKind
- Direction
- window.wrapper.macos.feature uses window.events, so a change to window.events can break window.wrapper.macos.feature, while a change to window.wrapper.macos.feature can't break window.events.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→34 window.wrapper.macos.feature uses settings part of a loop✕
- Connections
- 1 pair of types, where a type in window.wrapper.macos.feature uses a type in settings.
- The types involved
neovide.window.wrapper.macos.feature.MacosWindowFeature→neovide.settings.Settings
- Direction
- window.wrapper.macos.feature uses settings, so a change to settings can break window.wrapper.macos.feature, while a change to window.wrapper.macos.feature can't break settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→3 window.wrapper.macos uses renderer.box_drawing.renderer✕
- Connections
- 1 pair of types, where a type in window.wrapper.macos uses a type in renderer.box_drawing.renderer.
- The types involved
neovide.window.wrapper.macos.macos$module→neovide.renderer.box_drawing.renderer.Renderer
- Direction
- window.wrapper.macos uses renderer.box_drawing.renderer, so a change to renderer.box_drawing.renderer can break window.wrapper.macos, while a change to window.wrapper.macos can't break renderer.box_drawing.renderer.
- Position
- Below the diagonal: window.wrapper.macos uses a module listed above it, which is the healthy direction.
28→13 window.wrapper.macos uses bridge.handler✕
- Connections
- 1 pair of types, where a type in window.wrapper.macos uses a type in bridge.handler.
- The types involved
neovide.window.wrapper.macos.macos$module→neovide.bridge.handler.NeovimHandler
- Direction
- window.wrapper.macos uses bridge.handler, so a change to bridge.handler can break window.wrapper.macos, while a change to window.wrapper.macos can't break bridge.handler.
- Position
- Below the diagonal: window.wrapper.macos uses a module listed above it, which is the healthy direction.
28→21 window.wrapper.macos uses editor.window✕
- Connections
- 1 pair of types, where a type in window.wrapper.macos uses a type in editor.window.
- The types involved
neovide.window.wrapper.macos.macos$module→neovide.editor.window.Window
- Direction
- window.wrapper.macos uses editor.window, so a change to editor.window can break window.wrapper.macos, while a change to window.wrapper.macos can't break editor.window.
- Position
- Below the diagonal: window.wrapper.macos uses a module listed above it, which is the healthy direction.
28→27 window.wrapper.macos uses window.wrapper.macos.feature✕
- Connections
- 1 pair of types, where a type in window.wrapper.macos uses a type in window.wrapper.macos.feature.
- The types involved
neovide.window.wrapper.macos.macos$module→neovide.window.wrapper.macos.feature.MacosWindowFeature
- Direction
- window.wrapper.macos uses window.wrapper.macos.feature, so a change to window.wrapper.macos.feature can break window.wrapper.macos, while a change to window.wrapper.macos can't break window.wrapper.macos.feature.
- Position
- Below the diagonal: window.wrapper.macos uses a module listed above it, which is the healthy direction.
28→34 window.wrapper.macos uses settings part of a loop✕
- Connections
- 2 pairs of types, where a type in window.wrapper.macos uses a type in settings.
- The types involved
neovide.window.wrapper.macos.WindowNavigationState→neovide.settings.Settingsneovide.window.wrapper.macos.macos$module→neovide.settings.Settings
- Direction
- window.wrapper.macos uses settings, so a change to settings can break window.wrapper.macos, while a change to window.wrapper.macos can't break settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→35 window.wrapper.macos uses cmd_line part of a loop✕
- Connections
- 1 pair of types, where a type in window.wrapper.macos uses a type in cmd_line.
- The types involved
neovide.window.wrapper.macos.RouteLaunchConfig→neovide.cmd_line.CmdLineSettings
- Direction
- window.wrapper.macos uses cmd_line, so a change to cmd_line can break window.wrapper.macos, while a change to window.wrapper.macos can't break cmd_line.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→39 window.wrapper.macos uses bridge.command part of a loop✕
- Connections
- 1 pair of types, where a type in window.wrapper.macos uses a type in bridge.command.
- The types involved
neovide.window.wrapper.macos.RouteLaunchConfig→neovide.bridge.command.OpenArgs
- Direction
- window.wrapper.macos uses bridge.command, so a change to bridge.command can break window.wrapper.macos, while a change to window.wrapper.macos can't break bridge.command.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→1 window.wrapper uses clipboard✕
- Connections
- 1 pair of types, where a type in window.wrapper uses a type in clipboard.
- The types involved
neovide.window.wrapper.WinitWindowWrapper→neovide.clipboard.ClipboardHandle
- Direction
- window.wrapper uses clipboard, so a change to clipboard can break window.wrapper, while a change to window.wrapper can't break clipboard.
- Position
- Below the diagonal: window.wrapper uses a module listed above it, which is the healthy direction.
29→3 window.wrapper uses renderer.box_drawing.renderer✕
- Connections
- 2 pairs of types, where a type in window.wrapper uses a type in renderer.box_drawing.renderer.
- The types involved
neovide.window.wrapper.RouteCore→neovide.renderer.box_drawing.renderer.Rendererneovide.window.wrapper.RouteWindow→neovide.renderer.box_drawing.renderer.Renderer
- Direction
- window.wrapper uses renderer.box_drawing.renderer, so a change to renderer.box_drawing.renderer can break window.wrapper, while a change to window.wrapper can't break renderer.box_drawing.renderer.
- Position
- Below the diagonal: window.wrapper uses a module listed above it, which is the healthy direction.
29→4 window.wrapper uses running_tracker✕
- Connections
- 1 pair of types, where a type in window.wrapper uses a type in running_tracker.
- The types involved
neovide.window.wrapper.WinitWindowWrapper→neovide.running_tracker.RunningTracker
- Direction
- window.wrapper uses running_tracker, so a change to running_tracker can break window.wrapper, while a change to window.wrapper can't break running_tracker.
- Position
- Below the diagonal: window.wrapper uses a module listed above it, which is the healthy direction.
29→5 window.wrapper uses settings.config✕
- Connections
- 2 pairs of types, where a type in window.wrapper uses a type in settings.config.
- The types involved
neovide.window.wrapper.WinitWindowWrapper→neovide.settings.config.RendererHotReloadConfigsneovide.window.wrapper.WinitWindowWrapper→neovide.settings.config.WindowHotReloadConfigs
- Direction
- window.wrapper uses settings.config, so a change to settings.config can break window.wrapper, while a change to window.wrapper can't break settings.config.
- Position
- Below the diagonal: window.wrapper uses a module listed above it, which is the healthy direction.
29→7 window.wrapper uses units✕
- Connections
- 1 pair of types, where a type in window.wrapper uses a type in units.
- The types involved
neovide.window.wrapper.WinitWindowWrapper→neovide.units.GridScale
- Direction
- window.wrapper uses units, so a change to units can break window.wrapper, while a change to window.wrapper can't break units.
- Position
- Below the diagonal: window.wrapper uses a module listed above it, which is the healthy direction.
29→12 window.wrapper uses window.setup✕
- Connections
- 2 pairs of types, where a type in window.wrapper uses a type in window.setup.
- The types involved
neovide.window.wrapper.Route→neovide.window.setup.WindowSizeneovide.window.wrapper.RouteCore→neovide.window.setup.WindowSize
- Direction
- window.wrapper uses window.setup, so a change to window.setup can break window.wrapper, while a change to window.wrapper can't break window.setup.
- Position
- Below the diagonal: window.wrapper uses a module listed above it, which is the healthy direction.
29→13 window.wrapper uses bridge.handler✕
- Connections
- 4 pairs of types, where a type in window.wrapper uses a type in bridge.handler.
- The types involved
neovide.window.wrapper.RouteCore→neovide.bridge.handler.NeovimHandlerneovide.window.wrapper.RouteWindow→neovide.bridge.handler.NeovimHandlerneovide.window.wrapper.WinitWindowWrapper→neovide.bridge.handler.NeovimHandlerneovide.window.wrapper.wrapper$module→neovide.bridge.handler.NeovimHandler
- Direction
- window.wrapper uses bridge.handler, so a change to bridge.handler can break window.wrapper, while a change to window.wrapper can't break bridge.handler.
- Position
- Below the diagonal: window.wrapper uses a module listed above it, which is the healthy direction.
29→21 window.wrapper uses editor.window✕
- Connections
- 1 pair of types, where a type in window.wrapper uses a type in editor.window.
- The types involved
neovide.window.wrapper.RouteWindow→neovide.editor.window.Window
- Direction
- window.wrapper uses editor.window, so a change to editor.window can break window.wrapper, while a change to window.wrapper can't break editor.window.
- Position
- Below the diagonal: window.wrapper uses a module listed above it, which is the healthy direction.
29→23 window.wrapper uses renderer.vsync✕
- Connections
- 1 pair of types, where a type in window.wrapper uses a type in renderer.vsync.
- The types involved
neovide.window.wrapper.RouteState→neovide.renderer.vsync.VSync
- Direction
- window.wrapper uses renderer.vsync, so a change to renderer.vsync can break window.wrapper, while a change to window.wrapper can't break renderer.vsync.
- Position
- Below the diagonal: window.wrapper uses a module listed above it, which is the healthy direction.
29→24 window.wrapper uses window.mouse_manager✕
- Connections
- 3 pairs of types, where a type in window.wrapper uses a type in window.mouse_manager.
- The types involved
neovide.window.wrapper.RouteWindow→neovide.window.mouse_manager.MouseManagerneovide.window.wrapper.WinitWindowWrapper→neovide.window.mouse_manager.MessageSelectionEventneovide.window.wrapper.WinitWindowWrapper→neovide.window.mouse_manager.OverlayEvent
- Direction
- window.wrapper uses window.mouse_manager, so a change to window.mouse_manager can break window.wrapper, while a change to window.wrapper can't break window.mouse_manager.
- Position
- Below the diagonal: window.wrapper uses a module listed above it, which is the healthy direction.
29→27 window.wrapper uses window.wrapper.macos.feature✕
- Connections
- 2 pairs of types, where a type in window.wrapper uses a type in window.wrapper.macos.feature.
- The types involved
neovide.window.wrapper.RouteWindow→neovide.window.wrapper.macos.feature.MacosWindowFeatureneovide.window.wrapper.WinitWindowWrapper→neovide.window.wrapper.macos.feature.MacosWindowFeature
- Direction
- window.wrapper uses window.wrapper.macos.feature, so a change to window.wrapper.macos.feature can break window.wrapper, while a change to window.wrapper can't break window.wrapper.macos.feature.
- Position
- Below the diagonal: window.wrapper uses a module listed above it, which is the healthy direction.
29→28 window.wrapper uses window.wrapper.macos✕
- Connections
- 5 pairs of types, where a type in window.wrapper uses a type in window.wrapper.macos.
- The types involved
neovide.window.wrapper.Route→neovide.window.wrapper.macos.RouteLaunchConfigneovide.window.wrapper.RouteCore→neovide.window.wrapper.macos.DocumentStateneovide.window.wrapper.RouteWindow→neovide.window.wrapper.macos.DocumentStateneovide.window.wrapper.WinitWindowWrapper→neovide.window.wrapper.macos.RouteLaunchConfigneovide.window.wrapper.WinitWindowWrapper→neovide.window.wrapper.macos.WindowNavigationState
- Direction
- window.wrapper uses window.wrapper.macos, so a change to window.wrapper.macos can break window.wrapper, while a change to window.wrapper can't break window.wrapper.macos.
- Position
- Below the diagonal: window.wrapper uses a module listed above it, which is the healthy direction.
29→30 window.wrapper uses window.application part of a loop✕
- Connections
- 1 pair of types, where a type in window.wrapper uses a type in window.application.
- The types involved
neovide.window.wrapper.WinitWindowWrapper→neovide.window.application.ShouldRender
- Direction
- window.wrapper uses window.application, so a change to window.application can break window.wrapper, while a change to window.wrapper can't break window.application.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→32 window.wrapper uses renderer part of a loop✕
- Connections
- 3 pairs of types, where a type in window.wrapper uses a type in renderer.
- The types involved
neovide.window.wrapper.WinitWindowWrapper→neovide.renderer.DrawCommandneovide.window.wrapper.WinitWindowWrapper→neovide.renderer.MessageSelectionneovide.window.wrapper.wrapper$module→neovide.renderer.DrawCommandResult
- Direction
- window.wrapper uses renderer, so a change to renderer can break window.wrapper, while a change to window.wrapper can't break renderer.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→33 window.wrapper uses window.events part of a loop✕
- Connections
- 10 pairs of types, where a type in window.wrapper uses a type in window.events.
- The types involved
neovide.window.wrapper.PendingTransitions→neovide.window.events.RouteIdneovide.window.wrapper.Route→neovide.window.events.RouteIdneovide.window.wrapper.RouteCore→neovide.window.events.RouteIdneovide.window.wrapper.WinitWindowWrapper→neovide.window.events.EventPayloadneovide.window.wrapper.WinitWindowWrapper→neovide.window.events.EventTargetneovide.window.wrapper.WinitWindowWrapper→neovide.window.events.ForceClickKindneovide.window.wrapper.WinitWindowWrapper→neovide.window.events.MacShortcutCommandneovide.window.wrapper.WinitWindowWrapper→neovide.window.events.ProgressBarUpdateneovide.window.wrapper.WinitWindowWrapper→neovide.window.events.RouteIdneovide.window.wrapper.WinitWindowWrapper→neovide.window.events.WindowCommand
- Direction
- window.wrapper uses window.events, so a change to window.events can break window.wrapper, while a change to window.wrapper can't break window.events.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→34 window.wrapper uses settings part of a loop✕
- Connections
- 1 pair of types, where a type in window.wrapper uses a type in settings.
- The types involved
neovide.window.wrapper.WinitWindowWrapper→neovide.settings.Settings
- Direction
- window.wrapper uses settings, so a change to settings can break window.wrapper, while a change to window.wrapper can't break settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→35 window.wrapper uses cmd_line part of a loop✕
- Connections
- 2 pairs of types, where a type in window.wrapper uses a type in cmd_line.
- The types involved
neovide.window.wrapper.WinitWindowWrapper→neovide.cmd_line.GeometryArgsneovide.window.wrapper.WinitWindowWrapper→neovide.cmd_line.MouseCursorIcon
- Direction
- window.wrapper uses cmd_line, so a change to cmd_line can break window.wrapper, while a change to window.wrapper can't break cmd_line.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→39 window.wrapper uses bridge.command part of a loop✕
- Connections
- 1 pair of types, where a type in window.wrapper uses a type in bridge.command.
- The types involved
neovide.window.wrapper.WinitWindowWrapper→neovide.bridge.command.OpenArgs
- Direction
- window.wrapper uses bridge.command, so a change to bridge.command can break window.wrapper, while a change to window.wrapper can't break bridge.command.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→40 window.wrapper uses bridge part of a loop✕
- Connections
- 2 pairs of types, where a type in window.wrapper uses a type in bridge.
- The types involved
neovide.window.wrapper.WinitWindowWrapper→neovide.bridge.NeovimRuntimeneovide.window.wrapper.WinitWindowWrapper→neovide.bridge.SessionTarget
- Direction
- window.wrapper uses bridge, so a change to bridge can break window.wrapper, while a change to window.wrapper can't break bridge.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→1 window.application uses clipboard✕
- Connections
- 2 pairs of types, where a type in window.application uses a type in clipboard.
- The types involved
neovide.window.application.Application→neovide.clipboard.Clipboardneovide.window.application.Application→neovide.clipboard.ClipboardHandle
- Direction
- window.application uses clipboard, so a change to clipboard can break window.application, while a change to window.application can't break clipboard.
- Position
- Below the diagonal: window.application uses a module listed above it, which is the healthy direction.
30→4 window.application uses running_tracker✕
- Connections
- 1 pair of types, where a type in window.application uses a type in running_tracker.
- The types involved
neovide.window.application.Application→neovide.running_tracker.RunningTracker
- Direction
- window.application uses running_tracker, so a change to running_tracker can break window.application, while a change to window.application can't break running_tracker.
- Position
- Below the diagonal: window.application uses a module listed above it, which is the healthy direction.
30→5 window.application uses settings.config✕
- Connections
- 2 pairs of types, where a type in window.application uses a type in settings.config.
- The types involved
neovide.window.application.Application→neovide.settings.config.AppHotReloadConfigsneovide.window.application.Application→neovide.settings.config.HotReloadConfigs
- Direction
- window.application uses settings.config, so a change to settings.config can break window.application, while a change to window.application can't break settings.config.
- Position
- Below the diagonal: window.application uses a module listed above it, which is the healthy direction.
30→12 window.application uses window.setup✕
- Connections
- 1 pair of types, where a type in window.application uses a type in window.setup.
- The types involved
neovide.window.application.Application→neovide.window.setup.WindowSize
- Direction
- window.application uses window.setup, so a change to window.setup can break window.application, while a change to window.application can't break window.setup.
- Position
- Below the diagonal: window.application uses a module listed above it, which is the healthy direction.
30→29 window.application uses window.wrapper✕
- Connections
- 1 pair of types, where a type in window.application uses a type in window.wrapper.
- The types involved
neovide.window.application.Application→neovide.window.wrapper.WinitWindowWrapper
- Direction
- window.application uses window.wrapper, so a change to window.wrapper can break window.application, while a change to window.application can't break window.wrapper.
- Position
- Below the diagonal: window.application uses a module listed above it, which is the healthy direction.
30→32 window.application uses renderer part of a loop✕
- Connections
- 1 pair of types, where a type in window.application uses a type in renderer.
- The types involved
neovide.window.application.RenderState→neovide.renderer.DrawCommand
- Direction
- window.application uses renderer, so a change to renderer can break window.application, while a change to window.application can't break renderer.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→33 window.application uses window.events part of a loop✕
- Connections
- 4 pairs of types, where a type in window.application uses a type in window.events.
- The types involved
neovide.window.application.Application→neovide.window.events.EventPayloadneovide.window.application.Application→neovide.window.events.EventTargetneovide.window.application.Application→neovide.window.events.RouteIdneovide.window.application.Application→neovide.window.events.UserEvent
- Direction
- window.application uses window.events, so a change to window.events can break window.application, while a change to window.application can't break window.events.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→34 window.application uses settings part of a loop✕
- Connections
- 1 pair of types, where a type in window.application uses a type in settings.
- The types involved
neovide.window.application.Application→neovide.settings.Settings
- Direction
- window.application uses settings, so a change to settings can break window.application, while a change to window.application can't break settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→39 window.application uses bridge.command part of a loop✕
- Connections
- 1 pair of types, where a type in window.application uses a type in bridge.command.
- The types involved
neovide.window.application.Application→neovide.bridge.command.OpenArgs
- Direction
- window.application uses bridge.command, so a change to bridge.command can break window.application, while a change to window.application can't break bridge.command.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→3 renderer.cursor_renderer uses renderer.box_drawing.renderer✕
- Connections
- 2 pairs of types, where a type in renderer.cursor_renderer uses a type in renderer.box_drawing.renderer.
- The types involved
neovide.renderer.cursor_renderer.Corner→neovide.renderer.box_drawing.renderer.Cornerneovide.renderer.cursor_renderer.CursorRenderer→neovide.renderer.box_drawing.renderer.Corner
- Direction
- renderer.cursor_renderer uses renderer.box_drawing.renderer, so a change to renderer.box_drawing.renderer can break renderer.cursor_renderer, while a change to renderer.cursor_renderer can't break renderer.box_drawing.renderer.
- Position
- Below the diagonal: renderer.cursor_renderer uses a module listed above it, which is the healthy direction.
31→7 renderer.cursor_renderer uses units✕
- Connections
- 2 pairs of types, where a type in renderer.cursor_renderer uses a type in units.
- The types involved
neovide.renderer.cursor_renderer.Corner→neovide.units.GridScaleneovide.renderer.cursor_renderer.CursorRenderer→neovide.units.GridScale
- Direction
- renderer.cursor_renderer uses units, so a change to units can break renderer.cursor_renderer, while a change to renderer.cursor_renderer can't break units.
- Position
- Below the diagonal: renderer.cursor_renderer uses a module listed above it, which is the healthy direction.
31→8 renderer.cursor_renderer uses bridge.events✕
- Connections
- 2 pairs of types, where a type in renderer.cursor_renderer uses a type in bridge.events.
- The types involved
neovide.renderer.cursor_renderer.CmdlineCtx→neovide.bridge.events.EditorModeneovide.renderer.cursor_renderer.CursorRenderer→neovide.bridge.events.EditorMode
- Direction
- renderer.cursor_renderer uses bridge.events, so a change to bridge.events can break renderer.cursor_renderer, while a change to renderer.cursor_renderer can't break bridge.events.
- Position
- Below the diagonal: renderer.cursor_renderer uses a module listed above it, which is the healthy direction.
31→9 renderer.cursor_renderer uses editor.cursor✕
- Connections
- 2 pairs of types, where a type in renderer.cursor_renderer uses a type in editor.cursor.
- The types involved
neovide.renderer.cursor_renderer.CursorRenderer→neovide.editor.cursor.Cursorneovide.renderer.cursor_renderer.CursorRenderer→neovide.editor.cursor.CursorShape
- Direction
- renderer.cursor_renderer uses editor.cursor, so a change to editor.cursor can break renderer.cursor_renderer, while a change to renderer.cursor_renderer can't break editor.cursor.
- Position
- Below the diagonal: renderer.cursor_renderer uses a module listed above it, which is the healthy direction.
31→18 renderer.cursor_renderer uses renderer.grid_renderer✕
- Connections
- 1 pair of types, where a type in renderer.cursor_renderer uses a type in renderer.grid_renderer.
- The types involved
neovide.renderer.cursor_renderer.CursorRenderer→neovide.renderer.grid_renderer.GridRenderer
- Direction
- renderer.cursor_renderer uses renderer.grid_renderer, so a change to renderer.grid_renderer can break renderer.cursor_renderer, while a change to renderer.cursor_renderer can't break renderer.grid_renderer.
- Position
- Below the diagonal: renderer.cursor_renderer uses a module listed above it, which is the healthy direction.
31→19 renderer.cursor_renderer uses renderer.cursor_renderer.cursor_vfx✕
- Connections
- 2 pairs of types, where a type in renderer.cursor_renderer uses a type in renderer.cursor_renderer.cursor_vfx.
- The types involved
neovide.renderer.cursor_renderer.CursorRenderer→neovide.renderer.cursor_renderer.cursor_vfx.VfxModeListneovide.renderer.cursor_renderer.CursorSettings→neovide.renderer.cursor_renderer.cursor_vfx.VfxModeList
- Direction
- renderer.cursor_renderer uses renderer.cursor_renderer.cursor_vfx, so a change to renderer.cursor_renderer.cursor_vfx can break renderer.cursor_renderer, while a change to renderer.cursor_renderer can't break renderer.cursor_renderer.cursor_vfx.
- Position
- Below the diagonal: renderer.cursor_renderer uses a module listed above it, which is the healthy direction.
31→30 renderer.cursor_renderer uses window.application✕
- Connections
- 1 pair of types, where a type in renderer.cursor_renderer uses a type in window.application.
- The types involved
neovide.renderer.cursor_renderer.CursorRenderer→neovide.window.application.ShouldRender
- Direction
- renderer.cursor_renderer uses window.application, so a change to window.application can break renderer.cursor_renderer, while a change to renderer.cursor_renderer can't break window.application.
- Position
- Below the diagonal: renderer.cursor_renderer uses a module listed above it, which is the healthy direction.
31→34 renderer.cursor_renderer uses settings part of a loop✕
- Connections
- 1 pair of types, where a type in renderer.cursor_renderer uses a type in settings.
- The types involved
neovide.renderer.cursor_renderer.CursorRenderer→neovide.settings.Settings
- Direction
- renderer.cursor_renderer uses settings, so a change to settings can break renderer.cursor_renderer, while a change to renderer.cursor_renderer can't break settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→5 renderer uses settings.config✕
- Connections
- 2 pairs of types, where a type in renderer uses a type in settings.config.
- The types involved
neovide.renderer.Renderer→neovide.settings.config.Configneovide.renderer.Renderer→neovide.settings.config.RendererHotReloadConfigs
- Direction
- renderer uses settings.config, so a change to settings.config can break renderer, while a change to renderer can't break settings.config.
- Position
- Below the diagonal: renderer uses a module listed above it, which is the healthy direction.
32→7 renderer uses units✕
- Connections
- 2 pairs of types, where a type in renderer uses a type in units.
- The types involved
neovide.renderer.Renderer→neovide.units.GridScaleneovide.renderer.renderer$module→neovide.units.GridScale
- Direction
- renderer uses units, so a change to units can break renderer, while a change to renderer can't break units.
- Position
- Below the diagonal: renderer uses a module listed above it, which is the healthy direction.
32→8 renderer uses bridge.events✕
- Connections
- 4 pairs of types, where a type in renderer uses a type in bridge.events.
- The types involved
neovide.renderer.DrawCommandResult→neovide.bridge.events.StartupMessageneovide.renderer.Renderer→neovide.bridge.events.EditorModeneovide.renderer.Renderer→neovide.bridge.events.StartupMessageneovide.renderer.StartupMessageFlush→neovide.bridge.events.StartupMessage
- Direction
- renderer uses bridge.events, so a change to bridge.events can break renderer, while a change to renderer can't break bridge.events.
- Position
- Below the diagonal: renderer uses a module listed above it, which is the healthy direction.
32→11 renderer uses renderer.fonts.font_options✕
- Connections
- 1 pair of types, where a type in renderer uses a type in renderer.fonts.font_options.
- The types involved
neovide.renderer.RendererSettings→neovide.renderer.fonts.font_options.PixelGeometry
- Direction
- renderer uses renderer.fonts.font_options, so a change to renderer.fonts.font_options can break renderer, while a change to renderer can't break renderer.fonts.font_options.
- Position
- Below the diagonal: renderer uses a module listed above it, which is the healthy direction.
32→15 renderer uses bridge.ui_commands✕
- Connections
- 1 pair of types, where a type in renderer uses a type in bridge.ui_commands.
- The types involved
neovide.renderer.StartupMessageFlush→neovide.bridge.ui_commands.ParallelCommand
- Direction
- renderer uses bridge.ui_commands, so a change to bridge.ui_commands can break renderer, while a change to renderer can't break bridge.ui_commands.
- Position
- Below the diagonal: renderer uses a module listed above it, which is the healthy direction.
32→18 renderer uses renderer.grid_renderer✕
- Connections
- 1 pair of types, where a type in renderer uses a type in renderer.grid_renderer.
- The types involved
neovide.renderer.Renderer→neovide.renderer.grid_renderer.GridRenderer
- Direction
- renderer uses renderer.grid_renderer, so a change to renderer.grid_renderer can break renderer, while a change to renderer can't break renderer.grid_renderer.
- Position
- Below the diagonal: renderer uses a module listed above it, which is the healthy direction.
32→20 renderer uses renderer.rendered_window✕
- Connections
- 2 pairs of types, where a type in renderer uses a type in renderer.rendered_window.
- The types involved
neovide.renderer.Renderer→neovide.renderer.rendered_window.WindowDrawDetailsneovide.renderer.renderer$module→neovide.renderer.rendered_window.RenderedWindow
- Direction
- renderer uses renderer.rendered_window, so a change to renderer.rendered_window can break renderer, while a change to renderer can't break renderer.rendered_window.
- Position
- Below the diagonal: renderer uses a module listed above it, which is the healthy direction.
32→21 renderer uses editor.window✕
- Connections
- 2 pairs of types, where a type in renderer uses a type in editor.window.
- The types involved
neovide.renderer.SkiaRenderer→neovide.editor.window.Windowneovide.renderer.WindowConfig→neovide.editor.window.Window
- Direction
- renderer uses editor.window, so a change to editor.window can break renderer, while a change to renderer can't break editor.window.
- Position
- Below the diagonal: renderer uses a module listed above it, which is the healthy direction.
32→22 renderer uses editor.scrollbar✕
- Connections
- 1 pair of types, where a type in renderer uses a type in editor.scrollbar.
- The types involved
neovide.renderer.Renderer→neovide.editor.scrollbar.ScrollbarSnapshot
- Direction
- renderer uses editor.scrollbar, so a change to editor.scrollbar can break renderer, while a change to renderer can't break editor.scrollbar.
- Position
- Below the diagonal: renderer uses a module listed above it, which is the healthy direction.
32→23 renderer uses renderer.vsync✕
- Connections
- 1 pair of types, where a type in renderer uses a type in renderer.vsync.
- The types involved
neovide.renderer.SkiaRenderer→neovide.renderer.vsync.VSync
- Direction
- renderer uses renderer.vsync, so a change to renderer.vsync can break renderer, while a change to renderer can't break renderer.vsync.
- Position
- Below the diagonal: renderer uses a module listed above it, which is the healthy direction.
32→30 renderer uses window.application✕
- Connections
- 1 pair of types, where a type in renderer uses a type in window.application.
- The types involved
neovide.renderer.Renderer→neovide.window.application.ShouldRender
- Direction
- renderer uses window.application, so a change to window.application can break renderer, while a change to renderer can't break window.application.
- Position
- Below the diagonal: renderer uses a module listed above it, which is the healthy direction.
32→31 renderer uses renderer.cursor_renderer✕
- Connections
- 1 pair of types, where a type in renderer uses a type in renderer.cursor_renderer.
- The types involved
neovide.renderer.Renderer→neovide.renderer.cursor_renderer.CursorRenderer
- Direction
- renderer uses renderer.cursor_renderer, so a change to renderer.cursor_renderer can break renderer, while a change to renderer can't break renderer.cursor_renderer.
- Position
- Below the diagonal: renderer uses a module listed above it, which is the healthy direction.
32→34 renderer uses settings part of a loop✕
- Connections
- 2 pairs of types, where a type in renderer uses a type in settings.
- The types involved
neovide.renderer.Renderer→neovide.settings.Settingsneovide.renderer.renderer$module→neovide.settings.Settings
- Direction
- renderer uses settings, so a change to settings can break renderer, while a change to renderer can't break settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→5 window.events uses settings.config✕
- Connections
- 1 pair of types, where a type in window.events uses a type in settings.config.
- The types involved
neovide.window.events.UserEvent→neovide.settings.config.HotReloadConfigs
- Direction
- window.events uses settings.config, so a change to settings.config can break window.events, while a change to window.events can't break settings.config.
- Position
- Below the diagonal: window.events uses a module listed above it, which is the healthy direction.
33→32 window.events uses renderer✕
- Connections
- 1 pair of types, where a type in window.events uses a type in renderer.
- The types involved
neovide.window.events.UserEvent→neovide.renderer.DrawCommand
- Direction
- window.events uses renderer, so a change to renderer can break window.events, while a change to window.events can't break renderer.
- Position
- Below the diagonal: window.events uses a module listed above it, which is the healthy direction.
33→34 window.events uses settings part of a loop✕
- Connections
- 1 pair of types, where a type in window.events uses a type in settings.
- The types involved
neovide.window.events.UserEvent→neovide.settings.SettingsChanged
- Direction
- window.events uses settings, so a change to settings can break window.events, while a change to window.events can't break settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→33 settings uses window.events✕
- Connections
- 1 pair of types, where a type in settings uses a type in window.events.
- The types involved
neovide.settings.Settings→neovide.window.events.RouteId
- Direction
- settings uses window.events, so a change to window.events can break settings, while a change to settings can't break window.events.
- Position
- Below the diagonal: settings uses a module listed above it, which is the healthy direction.
35→34 cmd_line uses settings✕
- Connections
- 1 pair of types, where a type in cmd_line uses a type in settings.
- The types involved
neovide.cmd_line.cmd_line$module→neovide.settings.Settings
- Direction
- cmd_line uses settings, so a change to settings can break cmd_line, while a change to cmd_line can't break settings.
- Position
- Below the diagonal: cmd_line uses a module listed above it, which is the healthy direction.
36→21 renderer.d3d uses editor.window✕
- Connections
- 1 pair of types, where a type in renderer.d3d uses a type in editor.window.
- The types involved
neovide.renderer.d3d.D3DSkiaRenderer→neovide.editor.window.Window
- Direction
- renderer.d3d uses editor.window, so a change to editor.window can break renderer.d3d, while a change to renderer.d3d can't break editor.window.
- Position
- Below the diagonal: renderer.d3d uses a module listed above it, which is the healthy direction.
36→23 renderer.d3d uses renderer.vsync✕
- Connections
- 1 pair of types, where a type in renderer.d3d uses a type in renderer.vsync.
- The types involved
neovide.renderer.d3d.D3DSkiaRenderer→neovide.renderer.vsync.VSync
- Direction
- renderer.d3d uses renderer.vsync, so a change to renderer.vsync can break renderer.d3d, while a change to renderer.d3d can't break renderer.vsync.
- Position
- Below the diagonal: renderer.d3d uses a module listed above it, which is the healthy direction.
36→32 renderer.d3d uses renderer✕
- Connections
- 1 pair of types, where a type in renderer.d3d uses a type in renderer.
- The types involved
neovide.renderer.d3d.D3DSkiaRenderer→neovide.renderer.SkiaRenderer
- Direction
- renderer.d3d uses renderer, so a change to renderer can break renderer.d3d, while a change to renderer.d3d can't break renderer.
- Position
- Below the diagonal: renderer.d3d uses a module listed above it, which is the healthy direction.
36→34 renderer.d3d uses settings✕
- Connections
- 1 pair of types, where a type in renderer.d3d uses a type in settings.
- The types involved
neovide.renderer.d3d.D3DSkiaRenderer→neovide.settings.Settings
- Direction
- renderer.d3d uses settings, so a change to settings can break renderer.d3d, while a change to renderer.d3d can't break settings.
- Position
- Below the diagonal: renderer.d3d uses a module listed above it, which is the healthy direction.
37→21 renderer.metal uses editor.window✕
- Connections
- 1 pair of types, where a type in renderer.metal uses a type in editor.window.
- The types involved
neovide.renderer.metal.MetalSkiaRenderer→neovide.editor.window.Window
- Direction
- renderer.metal uses editor.window, so a change to editor.window can break renderer.metal, while a change to renderer.metal can't break editor.window.
- Position
- Below the diagonal: renderer.metal uses a module listed above it, which is the healthy direction.
37→23 renderer.metal uses renderer.vsync✕
- Connections
- 1 pair of types, where a type in renderer.metal uses a type in renderer.vsync.
- The types involved
neovide.renderer.metal.MetalSkiaRenderer→neovide.renderer.vsync.VSync
- Direction
- renderer.metal uses renderer.vsync, so a change to renderer.vsync can break renderer.metal, while a change to renderer.metal can't break renderer.vsync.
- Position
- Below the diagonal: renderer.metal uses a module listed above it, which is the healthy direction.
37→32 renderer.metal uses renderer✕
- Connections
- 1 pair of types, where a type in renderer.metal uses a type in renderer.
- The types involved
neovide.renderer.metal.MetalSkiaRenderer→neovide.renderer.SkiaRenderer
- Direction
- renderer.metal uses renderer, so a change to renderer can break renderer.metal, while a change to renderer.metal can't break renderer.
- Position
- Below the diagonal: renderer.metal uses a module listed above it, which is the healthy direction.
37→34 renderer.metal uses settings✕
- Connections
- 2 pairs of types, where a type in renderer.metal uses a type in settings.
- The types involved
neovide.renderer.metal.MetalDrawableSurface→neovide.settings.Settingsneovide.renderer.metal.MetalSkiaRenderer→neovide.settings.Settings
- Direction
- renderer.metal uses settings, so a change to settings can break renderer.metal, while a change to renderer.metal can't break settings.
- Position
- Below the diagonal: renderer.metal uses a module listed above it, which is the healthy direction.
38→5 renderer.opengl uses settings.config✕
- Connections
- 2 pairs of types, where a type in renderer.opengl uses a type in settings.config.
- The types involved
neovide.renderer.opengl.OpenGLSkiaRenderer→neovide.settings.config.Configneovide.renderer.opengl.opengl$module→neovide.settings.config.Config
- Direction
- renderer.opengl uses settings.config, so a change to settings.config can break renderer.opengl, while a change to renderer.opengl can't break settings.config.
- Position
- Below the diagonal: renderer.opengl uses a module listed above it, which is the healthy direction.
38→21 renderer.opengl uses editor.window✕
- Connections
- 1 pair of types, where a type in renderer.opengl uses a type in editor.window.
- The types involved
neovide.renderer.opengl.OpenGLSkiaRenderer→neovide.editor.window.Window
- Direction
- renderer.opengl uses editor.window, so a change to editor.window can break renderer.opengl, while a change to renderer.opengl can't break editor.window.
- Position
- Below the diagonal: renderer.opengl uses a module listed above it, which is the healthy direction.
38→23 renderer.opengl uses renderer.vsync✕
- Connections
- 1 pair of types, where a type in renderer.opengl uses a type in renderer.vsync.
- The types involved
neovide.renderer.opengl.OpenGLSkiaRenderer→neovide.renderer.vsync.VSync
- Direction
- renderer.opengl uses renderer.vsync, so a change to renderer.vsync can break renderer.opengl, while a change to renderer.opengl can't break renderer.vsync.
- Position
- Below the diagonal: renderer.opengl uses a module listed above it, which is the healthy direction.
38→32 renderer.opengl uses renderer✕
- Connections
- 3 pairs of types, where a type in renderer.opengl uses a type in renderer.
- The types involved
neovide.renderer.opengl.OpenGLSkiaRenderer→neovide.renderer.SkiaRendererneovide.renderer.opengl.OpenGLSkiaRenderer→neovide.renderer.WindowConfigneovide.renderer.opengl.opengl$module→neovide.renderer.WindowConfig
- Direction
- renderer.opengl uses renderer, so a change to renderer can break renderer.opengl, while a change to renderer.opengl can't break renderer.
- Position
- Below the diagonal: renderer.opengl uses a module listed above it, which is the healthy direction.
38→34 renderer.opengl uses settings✕
- Connections
- 2 pairs of types, where a type in renderer.opengl uses a type in settings.
- The types involved
neovide.renderer.opengl.OpenGLSkiaRenderer→neovide.settings.Settingsneovide.renderer.opengl.opengl$module→neovide.settings.Settings
- Direction
- renderer.opengl uses settings, so a change to settings can break renderer.opengl, while a change to renderer.opengl can't break settings.
- Position
- Below the diagonal: renderer.opengl uses a module listed above it, which is the healthy direction.
39→35 bridge.command uses cmd_line✕
- Connections
- 1 pair of types, where a type in bridge.command uses a type in cmd_line.
- The types involved
neovide.bridge.command.command$module→neovide.cmd_line.CmdLineSettings
- Direction
- bridge.command uses cmd_line, so a change to cmd_line can break bridge.command, while a change to bridge.command can't break cmd_line.
- Position
- Below the diagonal: bridge.command uses a module listed above it, which is the healthy direction.
40→1 bridge uses clipboard✕
- Connections
- 1 pair of types, where a type in bridge uses a type in clipboard.
- The types involved
neovide.bridge.NeovimRuntime→neovide.clipboard.ClipboardHandle
- Direction
- bridge uses clipboard, so a change to clipboard can break bridge, while a change to bridge can't break clipboard.
- Position
- Below the diagonal: bridge uses a module listed above it, which is the healthy direction.
40→4 bridge uses running_tracker✕
- Connections
- 1 pair of types, where a type in bridge uses a type in running_tracker.
- The types involved
neovide.bridge.NeovimRuntime→neovide.running_tracker.RunningTracker
- Direction
- bridge uses running_tracker, so a change to running_tracker can break bridge, while a change to bridge can't break running_tracker.
- Position
- Below the diagonal: bridge uses a module listed above it, which is the healthy direction.
40→5 bridge uses settings.config✕
- Connections
- 1 pair of types, where a type in bridge uses a type in settings.config.
- The types involved
neovide.bridge.NeovimRuntime→neovide.settings.config.Config
- Direction
- bridge uses settings.config, so a change to settings.config can break bridge, while a change to bridge can't break settings.config.
- Position
- Below the diagonal: bridge uses a module listed above it, which is the healthy direction.
40→8 bridge uses bridge.events✕
- Connections
- 1 pair of types, where a type in bridge uses a type in bridge.events.
- The types involved
neovide.bridge.bridge$module→neovide.bridge.events.StartupMessage
- Direction
- bridge uses bridge.events, so a change to bridge.events can break bridge, while a change to bridge can't break bridge.events.
- Position
- Below the diagonal: bridge uses a module listed above it, which is the healthy direction.
40→13 bridge uses bridge.handler✕
- Connections
- 2 pairs of types, where a type in bridge uses a type in bridge.handler.
- The types involved
neovide.bridge.NeovimRuntime→neovide.bridge.handler.NeovimHandlerneovide.bridge.bridge$module→neovide.bridge.handler.NeovimHandler
- Direction
- bridge uses bridge.handler, so a change to bridge.handler can break bridge, while a change to bridge can't break bridge.handler.
- Position
- Below the diagonal: bridge uses a module listed above it, which is the healthy direction.
40→33 bridge uses window.events✕
- Connections
- 2 pairs of types, where a type in bridge uses a type in window.events.
- The types involved
neovide.bridge.NeovimRuntime→neovide.window.events.RouteIdneovide.bridge.bridge$module→neovide.window.events.RouteId
- Direction
- bridge uses window.events, so a change to window.events can break bridge, while a change to bridge can't break window.events.
- Position
- Below the diagonal: bridge uses a module listed above it, which is the healthy direction.
40→34 bridge uses settings✕
- Connections
- 2 pairs of types, where a type in bridge uses a type in settings.
- The types involved
neovide.bridge.NeovimRuntime→neovide.settings.Settingsneovide.bridge.bridge$module→neovide.settings.Settings
- Direction
- bridge uses settings, so a change to settings can break bridge, while a change to bridge can't break settings.
- Position
- Below the diagonal: bridge uses a module listed above it, which is the healthy direction.
40→39 bridge uses bridge.command✕
- Connections
- 2 pairs of types, where a type in bridge uses a type in bridge.command.
- The types involved
neovide.bridge.NeovimRuntime→neovide.bridge.command.OpenModeneovide.bridge.bridge$module→neovide.bridge.command.OpenMode
- Direction
- bridge uses bridge.command, so a change to bridge.command can break bridge, while a change to bridge can't break bridge.command.
- Position
- Below the diagonal: bridge uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Event Sourcing
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 138 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 20 | Medium |
| A02:2025 — Security Misconfiguration | 6 | High / Critical |
Roadmap
Top priorities: Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +2.9 pts | Low | Documentation Quality |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. | +2.9 pts | Low | ADR Quality |
| Resolve the 44 Low coverage finding(s) in Code Coverage — start with mod.rs (9), linux.rs (3), events.rs (2). | +2.6 pts | Medium | Code Coverage |
| Resolve the 1 Banned license finding(s) in License Compliance. | +1.5 pts | Low | License Compliance |
| 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. | +2.7 pts | Medium | Architecture documentation |
| Enable Dependabot/Renovate or a dependency-review gate. | +1.5 pts | Medium | Security & performance tooling |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +0.7 pts | Low | Bus Factor |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.3 pts | Medium | Release Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.2 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/window/wrapper/mod.rs | 5.5 | Mixed | Cyclomatic Complexity: WinitWindowWrapper::try_create_window (cyclomatic 29) |
| src/window/application/mod.rs | 5.5 | Mixed | Cyclomatic Complexity: Application::user_event (cyclomatic 37) |
| src/bridge/events.rs | 5.6 | Mixed | Cyclomatic Complexity: neovide::bridge::events::parse_redraw_event (cyclomatic 48) |
| src/bridge/api_info.rs | 5.6 | Mixed | Cyclomatic Complexity: ApiParameterType::new (cyclomatic 18) |
| src/renderer/box_drawing/renderer.rs | 5.6 | Mixed | God Classes: FileTooLong: box_drawing/renderer.rs |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium advisory (unsound): REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/bridge/handler.rs | 5.9 | Mixed | Cyclomatic Complexity: NeovimHandler::handle_notify (cyclomatic 25) |
| src/renderer/cursor_renderer/mod.rs | 5.9 | Mixed | Cyclomatic Complexity: CursorRenderer::animate (cyclomatic 18) |
| src/bridge/ui_commands.rs | 5.9 | Mixed | Cyclomatic Complexity: neovide::bridge::ui_commands::start_ui_command_handler (cyclomatic 16) |
| src/settings/mod.rs | 5.9 | Mixed | Code Duplication: Edited copy of a member (28 corresponding lines) |
| src/editor/mod.rs | 6.0 | Mixed | Explicit Debt: HackComment |
| src/settings/config.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 47 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 47 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 356 of 385 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 · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- 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: it declares a published package (Cargo.toml), but 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — 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.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence).
- ED5 Idempotency — 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Rust, lua is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Rust, lua is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — 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.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X17 Uncapped recursion over a caller-supplied document — 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — 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 Lua 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.
- X5 Nullable reference types — 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 MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Lua, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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
21 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Editor::handle_redraw_event at 48. A further 5 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being neovide::window::keyboard_manager::get_special_key at 55 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/window/keyboard_manager.rs (neovide::window::keyboard_manager::get_special_key at 55), src/window/application/macos/hotkey.rs (neovide::window::application::macos::hotkey::keycode_for_char at 37), src/renderer/box_drawing/renderer.rs (Context::draw_corner at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 21 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Editor::handle_redraw_event (cyclomatic 48), neovide::bridge::events::parse_redraw_event (cyclomatic 48), Application::user_event (cyclomatic 37). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 21 together lifts Cyclomatic Complexity from 7.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
31 method(s) exceeded the cognitive complexity threshold of 15; the worst was Application::user_event at 57.
What to do
- Bring the 6 bodies over 30 down to 30 or less in Cognitive Complexity — start with Application::user_event (cognitive 57), WinitWindowWrapper::handle_window_settings_changed (cognitive 43), WinitWindowWrapper::try_create_window (cognitive 38). — 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 6 together lifts Cognitive Complexity from 6.6 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
31 god class(es) detected.
What to do
- Resolve the 11 FileTooLong finding(s) in God Classes — start with mod.rs (4), renderer.rs, rendered_window.rs. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 7 ClassTooLong finding(s) in God Classes — start with mod.rs (3), rendered_window.rs, renderer.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 5 TooManyMethods finding(s) in God Classes — start with mod.rs (3), feature.rs, rendered_window.rs. — One of this dimension's main actionable groups (5 warning-level).
D4 · Code Duplication
17 duplicated block group(s) detected. 2.0 % of the production lines (700 of 34,242) are in a reported copy. A further 16 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 3 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with channel_utils.rs, appearance.rs, feature.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with api_info.rs, events.rs, mod.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with command.rs, mod.rs. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
2 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 83 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 22.4% — 44 file(s) below 50%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 67 production file(s), 2 test binaries and 0 doc-test binaries).
What to do
- Resolve the 44 Low coverage finding(s) in Code Coverage — start with mod.rs (9), linux.rs (3), events.rs (2). — One of this dimension's main actionable groups (44 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 33 test files): measured (0 flaky).
D12 · Dependency Hygiene
18 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
1 of 423 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, which is its own choice and is not judged here.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
Top hotspots: src/window/wrapper/mod.rs (13×23=299); src/window/application/mod.rs (8×37=296); src/bridge/handler.rs (5×25=125) Repeated repair below the complexity floor: src/bridge/session.rs (3 of 5 changes were fixes)
What to do
- Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs (2), handler.rs, ui_commands.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with session.rs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
10 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/window/wrapper/macos/switcher/ui.rs. Counted over 86 of the 122 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
9 deducted task-comment markers across 34242 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 8 TodoComment finding(s) in Explicit Debt — start with d3d.rs (2), mouse_manager.rs, shortcut.rs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with mod.rs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 20 document(s) read across 1 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
139 finding(s): 0 critical, 120 high, 19 medium, 0 low. 89 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 4 file(s) — `.github/PULL_REQUEST_TEMPLATE.yml`, `src/bridge/command.rs` (line 156, lines 157–158, line 172, …), `src/window/application/macos/hotkey.rs` (line 59, line 89), `src/window/wrapper/mod.rs` (line 1221, lines 1222–1223, lines 1224–1226, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 23 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED (8), REDACTED (6). — One of this dimension's main actionable groups (23 issue-level).
- Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (7 issue-level).
- No action in Static Analysis (SAST) — all 89 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (89 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
12 finding(s): 0 critical, 0 high, 12 medium, 0 low.
What to do
- Resolve the 6 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
6 finding(s): 0 critical, 5 high, 1 medium, 0 low.
What to do
- Resolve the 5 High IaC finding(s) in IaC & Container Security — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
13 of 86 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/profiling/d3d.rs. Counted over 86 of the 122 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 13 Orphaned file finding(s) in Knowledge Freshness — start with d3d.rs, font.rs, lib.rs. — One of this dimension's main actionable groups (13 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: opengl.rs↔mod.rs 69%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with opengl.rs. — One of this dimension's main actionable groups (1 issue-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
AC3 · Page structure
- With more than one navigation landmark, each needs an aria-label/aria-labelledby (e.g. "Primary", "Footer") so assistive tech can tell them apart. At least one nav here is unlabelled. — REDACTED:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.button-hover:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — website/theme/custom.css:53
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
ES2 · Immutable events
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- 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.
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- `https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.1/MathJax.js?config=TeX-AMS-MML_HTMLorMML` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. — REDACTED:54
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X1 · Async correctness
X21 · Side-effecting pattern guard
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 90% | Exemplary | Solid. |
| Architecture | 90% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 62% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 61% | Adequate | Largest drag on the score — prioritise here. |
| Security | 64% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| Accessibility | 68% | Strong | Solid. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 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 — 67 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~81 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.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (4755 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; comments in this repository's .rs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 16 value object(s); 3 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — Not assessed, and this one is on us: 1 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Fold determinism — not applicable — the code was read and holds no event-replay fold, so there is nothing for this check to judge
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 67 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.
- X12 Unreachable branch — X12 reached only 0% of this repository's production lines — rust (34,242 lines), lua (528 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — 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 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
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — 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
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not 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.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 127 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: nvim-rs
- REDACTED
- Boundary-crossing change coupling: opengl.rs ↔ mod.rs src/renderer/opengl.rs:1
Serious — 213 finding(s)
- Low coverage: neovide-derive/src/lib.rs neovide-derive/src/lib.rs:1
- Low coverage: src/bridge/api_info.rs src/bridge/api_info.rs:1
- Low coverage: src/bridge/clipboard.rs src/bridge/clipboard.rs:1
- Low coverage: src/bridge/events.rs src/bridge/events.rs:1
- Low coverage: src/bridge/handler.rs src/bridge/handler.rs:1
- Low coverage: src/bridge/mod.rs src/bridge/mod.rs:1
- Low coverage: src/bridge/session.rs src/bridge/session.rs:1
- Low coverage: src/bridge/setup.rs src/bridge/setup.rs:1
- Low coverage: src/bridge/ui_commands.rs src/bridge/ui_commands.rs:1
- Low coverage: src/channel_utils.rs src/channel_utils.rs:1
- Low coverage: src/dimensions.rs src/dimensions.rs:1
- Low coverage: src/editor/draw_command_batcher.rs src/editor/draw_command_batcher.rs:1
- Low coverage: src/editor/intro.rs src/editor/intro.rs:1
- Low coverage: src/editor/mod.rs src/editor/mod.rs:1
- Low coverage: src/editor/window.rs src/editor/window.rs:1
- Low coverage: src/errors/mod.rs src/errors/mod.rs:1
- Low coverage: src/main.rs src/main.rs:1
- Low coverage: src/profiling/profiling_disabled.rs src/profiling/profiling_disabled.rs:1
- Low coverage: src/renderer/box_drawing/renderer.rs src/renderer/box_drawing/renderer.rs:1
- Low coverage: src/renderer/box_drawing/settings.rs src/renderer/box_drawing/settings.rs:1
- Low coverage: src/renderer/cursor_renderer/blink.rs src/renderer/cursor_renderer/blink.rs:1
- Low coverage: src/renderer/cursor_renderer/cursor_vfx.rs src/renderer/cursor_renderer/cursor_vfx.rs:1
- Low coverage: src/renderer/cursor_renderer/mod.rs src/renderer/cursor_renderer/mod.rs:1
- Low coverage: src/renderer/grid_renderer.rs src/renderer/grid_renderer.rs:1
- Low coverage: src/renderer/opengl.rs src/renderer/opengl.rs:1
- FileTooLong: wrapper/mod.rs src/window/wrapper/mod.rs
- FileTooLong: box_drawing/renderer.rs src/renderer/box_drawing/renderer.rs
- FileTooLong: editor/mod.rs src/editor/mod.rs
- FileTooLong: renderer/rendered_window.rs src/renderer/rendered_window.rs
- FileTooLong: bridge/events.rs src/bridge/events.rs
- FileTooLong: renderer/mod.rs src/renderer/mod.rs
- FileTooLong: bridge/ui_commands.rs src/bridge/ui_commands.rs
- FileTooLong: application/mod.rs src/window/application/mod.rs
- FileTooLong: macos/feature.rs src/window/wrapper/macos/feature.rs
- FileTooLong: window/mouse_manager.rs src/window/mouse_manager.rs
- FileTooLong: switcher/ui.rs src/window/wrapper/macos/switcher/ui.rs
- TodoComment src/window/mouse_manager.rs:166
- TodoComment src/window/macos/shortcut.rs:66
- TodoComment src/settings/config.rs:276
- TodoComment src/renderer/fonts/caching_shaper.rs:295
- TodoComment src/renderer/fonts/font_loader.rs:55
- TodoComment src/renderer/fonts/font_options.rs:51
- TodoComment src/profiling/d3d.rs:209
- TodoComment src/profiling/d3d.rs:392
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- ClassTooLong: WinitWindowWrapper src/window/wrapper/mod.rs:302
- ClassTooLong: Editor src/editor/mod.rs:164
- ClassTooLong: RenderedWindow src/renderer/rendered_window.rs:143
- ClassTooLong: Context src/renderer/box_drawing/renderer.rs:69
- ClassTooLong: Application src/window/application/mod.rs:155
- ClassTooLong: MouseManager src/window/mouse_manager.rs:112
- ClassTooLong: MacosWindowFeature src/window/wrapper/macos/feature.rs:198
- WinitWindowWrapper::handle_window_settings_changed (cognitive 43) src/window/wrapper/mod.rs:596
- WinitWindowWrapper::try_create_window (cognitive 38) src/window/wrapper/mod.rs:1150
- WinitWindowWrapper::handle_window_command (cognitive 23) src/window/wrapper/mod.rs:471
- WinitWindowWrapper::prepare_frame (cognitive 23) src/window/wrapper/mod.rs:2208
- WinitWindowWrapper::copy_message_selection (cognitive 21) src/window/wrapper/mod.rs:972
- WinitWindowWrapper::handle_window_event (cognitive 16) src/window/wrapper/mod.rs:823
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- WinitWindowWrapper::try_create_window (cyclomatic 29) src/window/wrapper/mod.rs:1150
- WinitWindowWrapper::handle_window_settings_changed (cyclomatic 28) src/window/wrapper/mod.rs:596
- WinitWindowWrapper::handle_window_command (cyclomatic 23) src/window/wrapper/mod.rs:471
- WinitWindowWrapper::handle_window_event (cyclomatic 21) src/window/wrapper/mod.rs:823
- WinitWindowWrapper::prepare_frame (cyclomatic 17) src/window/wrapper/mod.rs:2208
- TooManyMethods: WinitWindowWrapper src/window/wrapper/mod.rs:302
- TooManyMethods: MacosWindowFeature src/window/wrapper/macos/feature.rs:198
- TooManyMethods: Editor src/editor/mod.rs:164
- TooManyMethods: Application src/window/application/mod.rs:155
- TooManyMethods: RenderedWindow src/renderer/rendered_window.rs:143
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- neovide::bridge::events::parse_redraw_event (cyclomatic 48) src/bridge/events.rs:1104
- neovide::settings::config::watcher_thread (cyclomatic 19) src/settings/config.rs:299
- neovide::window::wrapper::macos::switcher::handle_editor_switcher_key (cyclomatic 18) src/window/wrapper/macos/switcher/mod.rs:168
- neovide::bridge::ui_commands::start_ui_command_handler (cyclomatic 16) src/bridge/ui_commands.rs:825
- Hotspot: src/window/wrapper/mod.rs src/window/wrapper/mod.rs:471
- Hotspot: src/window/application/mod.rs src/window/application/mod.rs:715
- Hotspot: src/bridge/handler.rs src/bridge/handler.rs:310
- Hotspot: src/bridge/ui_commands.rs src/bridge/ui_commands.rs:825
- MethodTooLong: Editor.handle_redraw_event src/editor/mod.rs:257
- MethodTooLong: WinitWindowWrapper.try_create_window src/window/wrapper/mod.rs:1150
- MethodTooLong: Application.user_event src/window/application/mod.rs:715
- MethodTooLong: D3DSkiaRenderer.new src/renderer/d3d.rs:144
- neovide::bridge::ui_commands::start_ui_command_handler (cognitive 34) src/bridge/ui_commands.rs:825
- neovide::settings::config::watcher_thread (cognitive 31) src/settings/config.rs:299
- neovide::window::wrapper::macos::switcher::handle_editor_switcher_key (cognitive 20) src/window/wrapper/macos/switcher/mod.rs:168
- MouseManager::handle_touch (cognitive 30) src/window/mouse_manager.rs:556
- MouseManager::send_nvim_mouse_button (cognitive 20) src/window/mouse_manager.rs:417
- MouseManager::handle_pointer_motion (cognitive 19) src/window/mouse_manager.rs:262
- REDACTED
- REDACTED
- REDACTED
- TooManyFields: CmdLineSettings src/cmd_line.rs:41
- TooManyFields: Config src/settings/config.rs:76
- TooManyFields: WindowSettings src/window/settings/mod.rs:13
- Edited copy of a member (11 corresponding lines) src/channel_utils.rs:50
- Edited copy of a member (11 corresponding lines) src/window/wrapper/macos/scrollbar/appearance.rs:112
- Edited copy of a member (11 corresponding lines) src/window/wrapper/macos/feature.rs:184
- Duplicated block (10 lines × 2) src/bridge/api_info.rs:252
- Duplicated block (10 lines × 2) src/bridge/events.rs:833
- Duplicated block (10 lines × 2) src/settings/mod.rs:184
- Application::user_event (cognitive 57) src/window/application/mod.rs:715
- Application::prepare_and_animate (cognitive 18) src/window/application/mod.rs:560
- Editor::handle_redraw_event (cognitive 26) src/editor/mod.rs:257
- Editor::set_window_float_position (cognitive 22) src/editor/mod.rs:638
- Renderer::draw_frame (cognitive 21) src/renderer/mod.rs:285
- Renderer::draw_message_selection (cognitive 16) src/renderer/mod.rs:452
- REDACTED
- REDACTED
- Edited copy of a member (10 corresponding lines) src/bridge/command.rs:67
- Edited copy of a member (10 corresponding lines) src/renderer/mod.rs:799
- Duplicated block (7 lines × 2) src/renderer/box_drawing/renderer.rs:160
- Duplicated block (7 lines × 2) src/renderer/rendered_window.rs:361
- Multiple navigation landmarks without distinguishing labels REDACTED:2
- Focus outline removed in CSS without a :focus replacement website/theme/custom.css:53
- Editor::handle_redraw_event (cyclomatic 48) src/editor/mod.rs:257
- Application::user_event (cyclomatic 37) src/window/application/mod.rs:715
- Config::write_to_env (cyclomatic 35) src/settings/config.rs:169
- State::handle_keyboard_input (cyclomatic 30) src/window/error_window.rs:252
- NeovimHandler::handle_notify (cyclomatic 25) src/bridge/handler.rs:310
- RenderedWindow::handle_window_draw_command (cyclomatic 19) src/renderer/rendered_window.rs:770
- ApiParameterType::new (cyclomatic 18) src/bridge/api_info.rs:105
- CursorRenderer::animate (cyclomatic 18) src/renderer/cursor_renderer/mod.rs:465
- MouseManager::handle_event (cyclomatic 18) src/window/mouse_manager.rs:671
- FontDescription::as_family_and_font_style (cyclomatic 17) src/renderer/fonts/font_options.rs:410
- Window::build_line_fragment (cyclomatic 16) src/editor/window.rs:361
- Renderer::handle_draw_command (cyclomatic 16) src/renderer/mod.rs:618
- Repeated repair: src/bridge/session.rs src/bridge/session.rs:148
- HackComment src/editor/mod.rs:710
- Config::write_to_env (cognitive 34) src/settings/config.rs:169
- Window::build_line_fragment (cognitive 30) src/editor/window.rs:361
- CursorRenderer::animate (cognitive 29) src/renderer/cursor_renderer/mod.rs:465
- CachingShaper::build_clusters (cognitive 29) src/renderer/fonts/caching_shaper.rs:271
- NeovimHandler::handle_notify (cognitive 25) src/bridge/handler.rs:310
- State::handle_keyboard_input (cognitive 25) src/window/error_window.rs:252
- CharacterGrid::scroll_region (cognitive 20) src/editor/grid.rs:77
- ParticleTrail::update (cognitive 20) src/renderer/cursor_renderer/cursor_vfx.rs:285
- GlobalHotkeys::register (cognitive 18) src/window/application/macos/hotkey.rs:143
- GpuCtxD3D::gpu_collect (cognitive 17) src/profiling/d3d.rs:290
- RenderedWindow::handle_window_draw_command (cognitive 17) src/renderer/rendered_window.rs:770
- BlinkStatus::update_status (cognitive 16) src/renderer/cursor_renderer/blink.rs:52
- FontOptions::parse (cognitive 16) src/renderer/fonts/font_options.rs:136
- REDACTED
- FunctionTooLong: neovide::profiling::d3d::create_d3d_gpu_context src/profiling/d3d.rs:131
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (22 corresponding lines) src/renderer/box_drawing/renderer.rs:145
- Edited copy of a member (24 corresponding lines) src/bridge/api_info.rs:246
- Edited copy of a member (28 corresponding lines) src/settings/mod.rs:166
- Edited copy of a member (17 corresponding lines) src/bridge/events.rs:917
- Edited copy of a member (16 corresponding lines) src/bridge/events.rs:830
- Edited copy of a member (12 corresponding lines) src/renderer/vsync/mod.rs:55
- Edited copy of a member (14 corresponding lines) src/window/wrapper/windows/context_menu.rs:24
- Edited copy of a member (15 corresponding lines) src/bridge/command.rs:152
- Edited copies of one member (4 members, 11+ corresponding lines) src/bridge/events.rs:880
- Edited copies of one member (3 members, 18+ corresponding lines) src/window/settings/macos.rs:15
- Edited copy of a member (4 corresponding lines) src/bridge/handler.rs:185
- Duplicated block (20 lines × 2) src/renderer/mod.rs:454
- Duplicated block (14–18 lines × 2) src/window/application/mod.rs:771
- Duplicated block (12–13 lines × 2) src/renderer/mod.rs:311
- Duplicated block (11–12 lines × 2) src/renderer/grid_renderer.rs:145
- Duplicated block (11 lines × 2) src/editor/mod.rs:921
- Duplicated block (9–10 lines × 2) src/bridge/api_info.rs:195
- Duplicated block (9 lines × 2) src/editor/grid.rs:95
- Duplicated block (8–9 lines × 2) src/renderer/cursor_renderer/mod.rs:587
- Duplicated block (7–8 lines × 3) src/bridge/api_info.rs:198
- Duplicated block (8 lines × 3) src/renderer/box_drawing/renderer.rs:180
- Duplicated block (6 lines × 2) src/renderer/grid_renderer.rs:137
- Duplicated block (8 lines × 2) src/settings/mod.rs:169
- Third-party script without Subresource Integrity REDACTED:54
Minor — 27 finding(s)
- Orphaned file src/profiling/d3d.rs:1
- Orphaned file src/settings/font.rs:1
- Orphaned file neovide-derive/src/lib.rs:1
- Orphaned file src/renderer/vsync/vsync_win_dwm.rs:1
- Orphaned file src/renderer/animation_utils.rs:1
- Orphaned file src/settings/from_value.rs:1
- Orphaned file src/renderer/profiler.rs:1
- Orphaned file src/utils/test.rs:1
- Orphaned file src/profiling/opengl.rs:1
- Orphaned file src/renderer/cursor_renderer/blink.rs:1
- Orphaned file src/renderer/vsync/mod.rs:1
- Orphaned file src/units.rs:1
- Orphaned file src/dimensions.rs:1
- Silent fallback default on Err src/bridge/mod.rs:564
- Silent fallback default on Err src/bridge/mod.rs:407
- Off-boarding risk: anonymized user #1
- Documentation: no build, run or usage example README.md:1
- No ADRs found src/main.rs:1
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No changelog
- Duplicated predicate src/window/application/macos/hotkey.rs:346
Minor — 18 finding(s)
- Outdated: anyhow
- Outdated: backtrace
- Outdated: clap
- Outdated: flexi_logger
- Outdated: futures
- Outdated: image
- Outdated: indoc
- Outdated: log
- Outdated: mundy
- Outdated: objc2
- Outdated: quote
- Outdated: rustc-hash
- Outdated: rustix
- Outdated: serde
- Outdated: serde_json
- Outdated: swash
- Outdated: time
- Outdated: uzers
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-1ca3156e2138492cb367b416a453fc1c/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-1ca3156e2138492cb367b416a453fc1c/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 . | 139 | 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 . | 12 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 6 | artifacts/raw/trivy-config.json |
| 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 |