AI Slop Code Risk Monitor

neovide/neovide

Name: neovide/neovide — Rust Code Quality & Security Review | AI Slop Code Risk Monitor
Creator: AI Slop Code Risk Monitor

Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

No Nonsense Neovim Client in Rust

0.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for neovide/neovide, a Rust project with 15,290 GitHub stars. SynthScan examined 45,806 lines of code across 172 source files, recording 28 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 0.7 (Low pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

0.7

Adjusted Signal

0.7

Raw Pattern Score

100%

Time Factor

2026-10-31

Last Push

15.3K

Stars

Rust

Language

45.8K

Lines of Code

172

Files

Pattern Hits

2026-10-31

Scan Date

0.00

HC Hit Rate

Risk Review · Payload v1

Use each vector to guide manual verification of the underlying findings.

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 2.9/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 26 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

Are imports declared and package/API names verified? 0 finding(s).

Agent Over-Engineering Ratio 0.7/100 · LOW

Are wrappers, guards, and repeated structures necessary? 2 finding(s).

PR Review Velocity Impact 3.4/100 · LOW

Which changes need focused human review? 28 finding(s).

What These Metrics Mean

Adjusted Signal: Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score: Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor: A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits: Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate: High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files: Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 0MEDIUM 2LOW 26

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 28 distinct pattern matches across 3 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Over-Commented Block25 hits · 25 pts

Severity	File	Line	Snippet	Context
LOW	src/cmd_line.rs	61		COMMENT
LOW	src/cmd_line.rs	101	/// Be "blocking" and let the shell persist as parent process. Takes precedence over `--fork`. [DEFAULT]	COMMENT
LOW	src/main.rs	201		COMMENT
LOW	src/main.rs	221	// redraw events responsible for updating the gui state, and custom neovide specific	COMMENT
LOW	src/main.rs	241	// for drawing and is responsible for maintaining the various draw surfaces which are stored	COMMENT
LOW	src/main.rs	261	//	COMMENT
LOW	src/renderer/box_drawing/renderer.rs	1621	'╦' -> Horizontal, Right	COMMENT
LOW	src/renderer/fonts/font_options.rs	381	PixelGeometry::BGRH => Self::BGRH,	COMMENT
LOW	src/bridge/session.rs	261	#[cfg(target_os = "windows")] cmd: Command,	COMMENT
LOW	src/bridge/events.rs	201	cursor_modes: Vec<CursorMode>,	COMMENT
LOW	src/bridge/events.rs	221	mode: EditorMode,	COMMENT
LOW	src/bridge/events.rs	241	grid: u64,	COMMENT
LOW	src/bridge/events.rs	361	},	COMMENT
LOW	src/bridge/events.rs	381	/// Indicates the range of buffer text displayed in the window, as well as the cursor position	COMMENT
LOW	src/bridge/transition.rs	21	/// Which connection neovim asked this route to use after its old session exits.	COMMENT
LOW	src/bridge/handler.rs	121	/// `v:servername`. An embedded WSL session or a missing answer leaves this	COMMENT
LOW	src/bridge/ui_commands.rs	201	/// Terminal-mode was asked to exit. Retry this buffer after the mode barrier.	COMMENT
LOW	src/bridge/ui_commands.rs	221	///	COMMENT
LOW	src/window/keyboard_manager.rs	221	format!("<{modifiers}{text}>")	COMMENT
LOW	src/window/keyboard_manager.rs	321	_ => None,	COMMENT
LOW	src/window/keyboard_manager.rs	341	// the physical key labeled 'alt' always maps to the virtual key 'meta'.)	COMMENT
LOW	src/window/keyboard_manager.rs	361	// get_special_key() above), we may as well treat it as 'meta' because:	COMMENT
LOW	src/window/wrapper/macos/scrollbar/layout.rs	21	/// slot is only the part reported by rectForPart(KnobSlot), where the track and	COMMENT
LOW	src/window/wrapper/macos/scrollbar/mod.rs	1	//! Split-aware scrollbars in the outer window padding.	COMMENT
LOW	src/window/wrapper/macos/scrollbar/mod.rs	21	//!	COMMENT

Decorative Section Separators2 hits · 6 pts

Severity	File	Line	Snippet	Context
MEDIUM	src/renderer/box_drawing/renderer.rs	1419	// ╭──────────╮	COMMENT
MEDIUM	src/renderer/box_drawing/renderer.rs	1421	// ╰──────────╯	COMMENT

Structural Annotation Overuse1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	src/utils/test.rs	15	/// NOTE: This function returns rectangles that CONTAIN the labels. So when using this function in	COMMENT