AI Slop Code Risk Monitor

rust-lang/rustlings

Name: rust-lang/rustlings — 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).

:crab: Small exercises to get you used to reading and writing Rust code!

1.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for rust-lang/rustlings, a Rust project with 64,517 GitHub stars. SynthScan examined 16,051 lines of code across 285 source files, recording 22 pattern matches distributed across 1 syntactic category. The legacy adjusted pattern signal is 1.4 (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.

1.4

Adjusted Signal

1.4

Raw Pattern Score

100%

Time Factor

2026-10-26

Last Push

64.5K

Stars

Rust

Language

16.1K

Lines of Code

285

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

Can maintainers explain intent, assumptions, and trade-offs? 22 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.0/100 · LOW

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

PR Review Velocity Impact 6.6/100 · LOW

Which changes need focused human review? 22 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 0LOW 22

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 22 distinct pattern matches across 1 syntactic category. 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 Block22 hits · 22 pts

Severity	File	Line	Snippet	Context
LOW	triagebot.toml	1	# Enable comments linking to triagebot range-diff when a PR is rebased	COMMENT
LOW	solutions/24_async/async1.rs	1	// Alice is an elementary school teacher who needs to calculate the mean test	COMMENT
LOW	solutions/19_smart_pointers/smart_pointers3.rs	1	// In this exercise, we are given a `Vec` of `u32` called `numbers` with values	COMMENT
LOW	solutions/19_smart_pointers/smart_pointers1.rs	1	// At compile time, Rust needs to know how much space a type takes up. This	COMMENT
LOW	solutions/18_iterators/iterators4.rs	21	// Case num==2: The iterator 2..=2 contains one element	COMMENT
LOW	solutions/quizzes/quiz2.rs	1	// Let's build a little machine in the form of a function. As input, we're going	COMMENT
LOW	solutions/quizzes/quiz3.rs	1	// An imaginary magical school has a new report card generation system written	COMMENT
LOW	solutions/13_error_handling/errors2.rs	1	// Say we're writing a game where you can buy items with tokens. All items cost	COMMENT
LOW	solutions/13_error_handling/errors5.rs	1	// This exercise is an altered version of the `errors4` exercise. It uses some	COMMENT
LOW	exercises/24_async/async1.rs	1	// Alice is an elementary school teacher who needs to calculate the mean test	COMMENT
LOW	exercises/19_smart_pointers/smart_pointers3.rs	1	// In this exercise, we are given a `Vec` of `u32` called `numbers` with values	COMMENT
LOW	exercises/19_smart_pointers/smart_pointers1.rs	1	// At compile time, Rust needs to know how much space a type takes up. This	COMMENT
LOW	exercises/23_conversions/conversions3.rs	21	// Incorrect number of fields	COMMENT
LOW	exercises/18_iterators/iterators4.rs	1	fn factorial(num: u64) -> u64 {	COMMENT
LOW	exercises/quizzes/quiz1.rs	1	// This is a quiz for the following sections:	COMMENT
LOW	exercises/quizzes/quiz2.rs	1	// This is a quiz for the following sections:	COMMENT
LOW	exercises/quizzes/quiz3.rs	1	// This quiz tests:	COMMENT
LOW	exercises/13_error_handling/errors2.rs	1	// Say we're writing a game where you can buy items with tokens. All items cost	COMMENT
LOW	exercises/13_error_handling/errors5.rs	1	// This exercise is an altered version of the `errors4` exercise. It uses some	COMMENT
LOW	src/cli.rs	1	use clap::{Parser, Subcommand};	COMMENT
LOW	src/cli.rs	21	///	COMMENT
LOW	src/dev/new.rs	101	# Optional multi-line message to be shown to users after finishing all exercises.	COMMENT