AI Slop Code Risk Monitor

mtkennerly/ludusavi

Name: mtkennerly/ludusavi — 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).

Backup tool for PC game saves

2.2 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for mtkennerly/ludusavi, a Rust project with 6,514 GitHub stars. SynthScan examined 47,617 lines of code across 162 source files, recording 48 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 2.2 (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.

2.2

Adjusted Signal

2.2

Raw Pattern Score

100%

Time Factor

2026-10-18

Last Push

6.5K

Stars

Rust

Language

47.6K

Lines of Code

162

Files

Pattern Hits

2026-10-31

Scan Date

0.04

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 3.9/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 6.1/100 · LOW

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

Agent Over-Engineering Ratio 0.6/100 · LOW

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

PR Review Velocity Impact 10.6/100 · LOW

Which changes need focused human review? 48 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 6HIGH 1MEDIUM 0LOW 41

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 48 distinct pattern matches across 4 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.

Hallucination Indicators6 hits · 60 pts

Severity	File	Line	Snippet	Context
CRITICAL	src/gui/app.rs	1830	self.config.backup.filter.ignored_paths.remove(index);	CODE
CRITICAL	src/gui/app.rs	1835	self.config.backup.filter.ignored_paths.swap(index, offset);	CODE
CRITICAL	src/gui/app.rs	1857	self.config.backup.filter.ignored_registry.remove(index);	CODE
CRITICAL	src/gui/app.rs	1862	self.config.backup.filter.ignored_registry.swap(index, offset);	CODE
CRITICAL	src/gui/app.rs	2011	self.config.apps.rclone.path.reset(text);	CODE
CRITICAL	src/gui/app.rs	2459	BrowseFileSubject::RcloneExecutable => self.config.apps.rclone.path.clone(),	CODE

Over-Commented Block40 hits · 38 pts

Severity	File	Line	Snippet	Context
LOW	src/lang.rs	61	/// Czech	COMMENT
LOW	src/lang.rs	81	#[serde(rename = "fr-FR")]	COMMENT
LOW	src/lang.rs	101	/// Brazilian Portuguese	COMMENT
LOW	src/report.rs	81	pub error: Option<SaveError>,	COMMENT
LOW	src/report.rs	101	/// Manifest tags describing the kind of data, such as `save` or `config`.	COMMENT
LOW	src/report.rs	121	/// Any other games that also have the same registry path.	COMMENT
LOW	src/report.rs	201	}	COMMENT
LOW	src/main.rs	101	}	COMMENT
LOW	src/main.rs	121	/// * Windows Console Host	COMMENT
LOW	src/api.rs	541	/// Extra Wine/Proton prefix to check for saves.	COMMENT
LOW	src/api.rs	561	pub finality: Finality,	COMMENT
LOW	src/cli/parse.rs	141		COMMENT
LOW	src/cli/parse.rs	161	wine_prefix: Option<StrictPath>,	COMMENT
LOW	src/cli/parse.rs	181		COMMENT
LOW	src/cli/parse.rs	201	/// When not specified, this defers to the config file.	COMMENT
LOW	src/cli/parse.rs	221	dump_registry: bool,	COMMENT
LOW	src/cli/parse.rs	241	#[clap()]	COMMENT
LOW	src/cli/parse.rs	261	/// rather than ignoring it and continuing silently.	COMMENT
LOW	src/cli/parse.rs	281	#[clap(long)]	COMMENT
LOW	src/cli/parse.rs	301	/// By default, disabled games are skipped unless you name them explicitly.	COMMENT
LOW	src/cli/parse.rs	341	/// Only report these specific games.	COMMENT
LOW	src/cli/parse.rs	361	/// Print information to stdout in machine-readable JSON.	COMMENT
LOW	src/cli/parse.rs	381	#[clap(long)]	COMMENT
LOW	src/cli/parse.rs	401		COMMENT
LOW	src/cli/parse.rs	461	/// Even if another `--force` option has been specified,	COMMENT
LOW	src/cli/parse.rs	481		COMMENT
LOW	src/cli/parse.rs	501	/// When not specified, this defers to the config file.	COMMENT
LOW	src/cli/parse.rs	521	#[clap(long)]	COMMENT
LOW	src/cli/parse.rs	541	/// However, exit code zero will always use JSON output.	COMMENT
LOW	src/cli/parse.rs	601	}	COMMENT
LOW	src/cli/parse.rs	701	/// Use GUI dialogs for prompts and some information.	COMMENT
LOW	src/cli/parse.rs	721		COMMENT
LOW	src/cli/parse.rs	781	#[clap(name = "onedrive")]	COMMENT
LOW	src/cli/parse.rs	801	#[clap(long)]	COMMENT
LOW	src/cli/parse.rs	861	#[derive(clap::Parser, Clone, Debug, PartialEq, Eq)]	COMMENT
LOW	src/cli/api.rs	61	CheckAppUpdate(response::CheckAppUpdate),	COMMENT
LOW	src/cli/api.rs	81	/// instead of stopping at the first match.	COMMENT
LOW	src/cli/api.rs	101	pub disabled: bool,	COMMENT
LOW	src/scan/title.rs	341	/// Search for exact titles or aliases.	COMMENT
LOW	src/resource/config.rs	1241	#[serde(skip_serializing_if = "std::ops::Not::not")]	COMMENT

Empty Error Handlers1 hit · 5 pts

Severity	File	Line	Snippet	Context
HIGH	tasks.py	48	except Exception:	CODE

Excessive Try-Catch Wrapping1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	tasks.py	48	except Exception:	CODE