AI Slop Code RIsk Monitor

gyscos/cursive

A Text User Interface library for the Rust programming language

6.1 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for gyscos/cursive, a Rust project with 4,856 GitHub stars. SynthScan examined 46,104 lines of code across 225 source files, recording 278 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 6.1 (Moderate 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.

6.1
Adjusted Signal
6.1
Raw Pattern Score
100%
Time Factor
2026-09-25
Last Push
4.9K
Stars
Rust
Language
46.1K
Lines of Code
225
Files
278
Pattern Hits
2026-10-12
Scan Date
0.00
HC Hit Rate

Risk Review · v3

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

Cognitive Ownership Risk 25.6/100 · MEDIUM

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

Hallucinated Dependency & Supply Chain Risk 0.4/100 · LOW

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

Agent Over-Engineering Ratio 0.3/100 · LOW

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

PR Review Velocity Impact 26.2/100 · MEDIUM

Which changes need focused human review? 278 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 1LOW 277

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 278 distinct pattern matches across 5 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 Block270 hits · 268 pts
SeverityFileLineSnippetContext
LOWcursive/examples/colors.rs1use cursive::Printer;COMMENT
LOWcursive/examples/builder.rs1use cursive::views::{BoxedView, Button, EditView, Panel, TextView};COMMENT
LOWcursive/examples/assets/style.toml1# Every field in a theme file is optional.COMMENT
LOWcursive/src/cursive_runnable.rs81COMMENT
LOWcursive/src/cursive_runnable.rs121 /// Used to manually control the event loop. In most cases, runningCOMMENT
LOWcursive/src/cursive_runnable.rs161COMMENT
LOWcursive/src/cursive_ext.rs1/// Extension trait for the `Cursive` root to simplify initialization.COMMENT
LOWcursive/src/cursive_ext.rs21/// #[cfg(feature = "termion-backend")]COMMENT
LOWcursive/src/cursive_ext.rs41 fn run_ncurses(&mut self) -> std::io::Result<()>;COMMENT
LOWcursive/src/lib.rs1//! # CursiveCOMMENT
LOWcursive/src/lib.rs21//! use cursive::{Cursive, CursiveExt};COMMENT
LOWcursive/src/lib.rs41//! Cursive is callback-driven: it reacts to events generated by user input.COMMENT
LOWcursive/src/lib.rs81///COMMENT
LOWcursive/src/backends/mod.rs1//! Define backends using common libraries.COMMENT
LOWcursive/src/backends/termion.rs41 events: Events<File>,COMMENT
LOWcursive/src/backends/termion.rs61/// Permission is hereby granted, free of charge, to any person obtaining a copyCOMMENT
LOWcursive/src/backends/curses/mod.rs101 Color::Light(BaseColor::Yellow) => 11 % max_colors,COMMENT
LOWcursive-macros/src/lib.rs1use proc_macro::TokenStream;COMMENT
LOWcursive-macros/src/lib.rs21/// to be cloneable).COMMENT
LOWcursive-macros/src/lib.rs41/// constructor method.COMMENT
LOWcursive-macros/src/lib.rs61/// }COMMENT
LOWcursive-macros/src/lib.rs81COMMENT
LOWcursive-macros/src/builder/blueprint.rs641 // Then, from the body, we can get:COMMENT
LOWcursive-macros/src/builder/callback_helper.rs281///COMMENT
LOWcursive-macros/src/builder/callback_helper.rs301///COMMENT
LOWcursive-macros/src/builder/callback_helper.rs321///COMMENT
LOWcursive-macros/src/builder/callback_helper.rs341///COMMENT
LOWcursive-core/src/logger.rs1//! Logging utilities.COMMENT
LOWcursive-core/src/logger.rs21///COMMENT
LOWcursive-core/src/logger.rs121///COMMENT
LOWcursive-core/src/direction.rs1//! Direction-related structures.COMMENT
LOWcursive-core/src/direction.rs21//! Usually, "front" refers to the "forward" direction, or the "next"COMMENT
LOWcursive-core/src/direction.rs81 // }COMMENT
LOWcursive-core/src/direction.rs121COMMENT
LOWcursive-core/src/backend.rs1//! Define the backend trait for actual terminal interaction.COMMENT
LOWcursive-core/src/backend.rs21/// or termion, or it can entirely simulate a terminal and show it as aCOMMENT
LOWcursive-core/src/backend.rs41 ///COMMENT
LOWcursive-core/src/backend.rs61 /// The next call to `print()` will start at this place.COMMENT
LOWcursive-core/src/xy.rs61 /// Returns `f(self.x, self.y)`COMMENT
LOWcursive-core/src/xy.rs81 ///COMMENT
LOWcursive-core/src/xy.rs101 ///COMMENT
LOWcursive-core/src/xy.rs121 /// Returns `None` otherwise.COMMENT
LOWcursive-core/src/xy.rs141 /// # ExamplesCOMMENT
LOWcursive-core/src/xy.rs161 /// # use cursive_core::XY;COMMENT
LOWcursive-core/src/xy.rs181 /// assert_eq!((x, y), (1, 2));COMMENT
LOWcursive-core/src/xy.rs201 /// let xy = XY::new(String::from("a"), String::from("bbb"));COMMENT
LOWcursive-core/src/xy.rs221 /// let vec: Vec<bool> = xy.iter().map(|&i| i > 1).collect();COMMENT
LOWcursive-core/src/xy.rs241 Orientation::Horizontal => &self.x,COMMENT
LOWcursive-core/src/xy.rs261 Orientation::Vertical => &mut self.y,COMMENT
LOWcursive-core/src/xy.rs281 ///COMMENT
LOWcursive-core/src/xy.rs301 /// # use cursive_core::XY;COMMENT
LOWcursive-core/src/xy.rs321 /// # use cursive_core::XY;COMMENT
LOWcursive-core/src/xy.rs341COMMENT
LOWcursive-core/src/xy.rs361 ///COMMENT
LOWcursive-core/src/xy.rs381 ///COMMENT
LOWcursive-core/src/xy.rs401 /// # use cursive_core::XY;COMMENT
LOWcursive-core/src/xy.rs421 /// # use cursive_core::direction::Orientation;COMMENT
LOWcursive-core/src/xy.rs441 /// ```COMMENT
LOWcursive-core/src/xy.rs481 }COMMENT
LOWcursive-core/src/xy.rs501COMMENT
210 more matches not shown…
Fake / Example Data4 hits · 4 pts
SeverityFileLineSnippetContext
LOWcursive/examples/assets/lorem.txt1Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus sit amet porttitor ex. Vivamus ultricies nec massa egCODE
LOWcursive/examples/assets/lorem.txt1Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus sit amet porttitor ex. Vivamus ultricies nec massa egCODE
LOWcursive/examples/assets/lorem.txt15Praesent dui lectus, commodo eget nulla ut, maximus facilisis ligula. Aliquam ultricies augue ac pellentesque pellentesqCODE
LOWcursive/examples/assets/lorem.txt15Praesent dui lectus, commodo eget nulla ut, maximus facilisis ligula. Aliquam ultricies augue ac pellentesque pellentesqCODE
TODO Padding2 hits · 3 pts
SeverityFileLineSnippetContext
LOWcursive/src/backends/blt.rs280 // TODO: implement this correctly.COMMENT
LOWcursive-macros/src/builder/callback_helper.rs403 // TODO: implement itCOMMENT
Decorative Section Separators1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMcursive-core/src/views/linear_layout.rs991 // ── Cache invalidation ───────────────────────────────────────────────────COMMENT
Verbosity Indicators1 hit · 2 pts
SeverityFileLineSnippetContext
LOWcursive-core/src/utils/lines/spans/chunk_iterator.rs97 // We need to check if the last segment ended with a space.COMMENT