AI Slop Code Risk Monitor

microsoft/RustTraining

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

Beginner, advanced, expert level Rust training material

2.8 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for microsoft/RustTraining, a Rust project with 14,986 GitHub stars. SynthScan examined 77,669 lines of code across 197 source files, recording 122 pattern matches distributed across 8 syntactic categories. The legacy adjusted pattern signal is 2.8 (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.8
Adjusted Signal
2.8
Raw Pattern Score
100%
Time Factor
2026-10-24
Last Push
15.0K
Stars
Rust
Language
77.7K
Lines of Code
197
Files
122
Pattern Hits
2026-10-31
Scan Date
0.01
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 11.0/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 1.0/100 · LOW

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

Agent Over-Engineering Ratio 1.5/100 · LOW

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

PR Review Velocity Impact 9.2/100 · LOW

Which changes need focused human review? 122 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 1HIGH 0MEDIUM 9LOW 112

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 122 distinct pattern matches across 8 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.

Structural Annotation Overuse74 hits · 142 pts
SeverityFileLineSnippetContext
LOWcsharp-book/src/ch17-capstone-project.md48### Step 1: Project SetupCOMMENT
LOWcsharp-book/src/ch17-capstone-project.md78### Step 2: Define Your Data TypesCOMMENT
LOWcsharp-book/src/ch17-capstone-project.md147### Step 3: Error TypeCOMMENT
LOWcsharp-book/src/ch17-capstone-project.md168### Step 4: HTTP ClientCOMMENT
LOWcsharp-book/src/ch17-capstone-project.md219### Step 5: Display FormattingCOMMENT
LOWcsharp-book/src/ch17-capstone-project.md247### Step 6: Wire It All TogetherCOMMENT
LOWcsharp-book/src/ch17-capstone-project.md298### Step 7: TestsCOMMENT
LOWrust-patterns-book/src/ch19-capstone-project.md39## Step 1: Define the Task TypesCOMMENT
LOWrust-patterns-book/src/ch19-capstone-project.md90## Step 2: Define the Work FunctionCOMMENT
LOWrust-patterns-book/src/ch19-capstone-project.md105## Step 3: Error HandlingCOMMENT
LOWrust-patterns-book/src/ch19-capstone-project.md128## Step 4: The SchedulerCOMMENT
LOWrust-patterns-book/src/ch19-capstone-project.md184## Step 5: Integration TestCOMMENT
LOWrust-patterns-book/src/ch19-capstone-project.md235## Step 6: Put It All TogetherCOMMENT
LOW⚡…k/src/ch05-miri-valgrind-and-sanitizers-verifying-u.md112# Step 1: Run all tests under MiriCOMMENT
LOW⚡…k/src/ch05-miri-valgrind-and-sanitizers-verifying-u.md115# Step 2: If Miri reports errors, isolate themCOMMENT
LOW⚡…k/src/ch05-miri-valgrind-and-sanitizers-verifying-u.md118# Step 3: Use Miri's backtrace for diagnosisCOMMENT
LOW⚡…k/src/ch05-miri-valgrind-and-sanitizers-verifying-u.md121# Step 4: Choose a borrow modelCOMMENT
LOW⚡engineering-book/src/ch12-tricks-from-the-trenches.md199# Step 1: Find duplicatesCOMMENT
LOW⚡engineering-book/src/ch12-tricks-from-the-trenches.md202# Step 2: Find who pulls the old versionCOMMENT
LOW⚡engineering-book/src/ch12-tricks-from-the-trenches.md205# Step 3: Update the culpritCOMMENT
LOW⚡engineering-book/src/ch12-tricks-from-the-trenches.md208# Step 4: If no update available, pin in [patch]COMMENT
LOW⚡engineering-book/src/ch12-tricks-from-the-trenches.md212# Step 5: VerifyCOMMENT
LOW⚡…-book/src/ch04-code-coverage-seeing-what-tests-miss.md129# Step 1: Build with coverage instrumentationCOMMENT
LOW⚡…-book/src/ch04-code-coverage-seeing-what-tests-miss.md134# Step 2: Run tests (generates .profraw files)COMMENT
LOW⚡…-book/src/ch04-code-coverage-seeing-what-tests-miss.md137# Step 3: Aggregate with grcovCOMMENT
LOW…-book/src/ch04-code-coverage-seeing-what-tests-miss.md148# Step 4: View reportCOMMENT
LOW⚡…g-book/src/ch03-benchmarking-measuring-what-matters.md258# Step 1: Build with debug info (release speed, debug symbols)COMMENT
LOW⚡…g-book/src/ch03-benchmarking-measuring-what-matters.md264# Step 2: Record with perfCOMMENT
LOW⚡…g-book/src/ch03-benchmarking-measuring-what-matters.md267# Step 3: Generate a flamegraphCOMMENT
LOW⚡…g-book/src/ch03-benchmarking-measuring-what-matters.md292# Step 1: Build with instrumentationCOMMENT
LOW⚡…g-book/src/ch03-benchmarking-measuring-what-matters.md295# Step 2: Run representative workloadsCOMMENT
LOW⚡…g-book/src/ch03-benchmarking-measuring-what-matters.md298# Step 3: Merge profiling dataCOMMENT
LOW⚡…g-book/src/ch03-benchmarking-measuring-what-matters.md304# Step 4: Rebuild with profiling feedbackCOMMENT
LOW⚡…g-book/src/ch03-benchmarking-measuring-what-matters.md316# Step 1: Build with instrumentationCOMMENT
LOW⚡…g-book/src/ch03-benchmarking-measuring-what-matters.md319# Step 2: Run representative workloadsCOMMENT
LOW⚡…g-book/src/ch03-benchmarking-measuring-what-matters.md322# Step 3: Rebuild with profiling feedbackCOMMENT
LOW⚡…k/src/ch02-cross-compilation-one-source-many-target.md153# Step 1: Install target + cross-linkerCOMMENT
LOW⚡…k/src/ch02-cross-compilation-one-source-many-target.md157# Step 2: Configure linker in .cargo/config.toml (see above)COMMENT
LOW⚡…k/src/ch02-cross-compilation-one-source-many-target.md159# Step 3: BuildCOMMENT
LOW⚡…k/src/ch02-cross-compilation-one-source-many-target.md162# Step 4: Verify the binaryCOMMENT
LOWpython-book/src/ch15-migration-patterns.md271### Step 1: Identify HotspotsCOMMENT
LOWpython-book/src/ch15-migration-patterns.md283### Step 2: Write Rust Extension for HotspotCOMMENT
LOWpython-book/src/ch15-migration-patterns.md295### Step 3: Replace Python Call with Rust CallCOMMENT
LOWpython-book/src/ch15-migration-patterns.md308### Step 4: Expand GraduallyCOMMENT
LOWpython-book/src/ch17-capstone-project.md70## Step 1: Define the Data Model (Ch. 3, 6, 10, 11)COMMENT
LOWpython-book/src/ch17-capstone-project.md152## Step 2: Storage Layer (Ch. 9, 7)COMMENT
LOWpython-book/src/ch17-capstone-project.md190## Step 3: Command Enum (Ch. 6)COMMENT
LOWpython-book/src/ch17-capstone-project.md251## Step 4: Business Logic (Ch. 5, 12, 7)COMMENT
LOWpython-book/src/ch17-capstone-project.md335## Step 5: Wire It Together (Ch. 8)COMMENT
LOWpython-book/src/ch17-capstone-project.md401## Step 6: Cargo.toml DependenciesCOMMENT
LOWpython-book/src/ch17-capstone-project.md420## Step 7: Tests (Ch. 14)COMMENT
LOWxtask/src/main.rs323/// NOTE: This function preserves and hardens the multi-layer security from PR#18:COMMENT
LOW⚡…c/ch14-async-is-an-optimization-not-an-architecture.md52 // Step 1: Validate — pure business rules, no I/OCOMMENT
LOW⚡…c/ch14-async-is-an-optimization-not-an-architecture.md56 // Step 2: Check inventory — needs a database callCOMMENT
LOW⚡…c/ch14-async-is-an-optimization-not-an-architecture.md62 // Step 3: Calculate pricing — pure math, but async because we're already hereCOMMENT
LOW⚡…c/ch14-async-is-an-optimization-not-an-architecture.md65 // Step 4: Apply discount — needs an external service callCOMMENT
LOW⚡…c/ch14-async-is-an-optimization-not-an-architecture.md69 // Step 5: Format receipt — pureCOMMENT
LOW⚡async-book/src/ch15-exercises.md298 // Step 2: Filter evensCOMMENT
LOW⚡async-book/src/ch15-exercises.md300 // Step 3: Square eachCOMMENT
LOW⚡async-book/src/ch15-exercises.md302 // Step 4: Process concurrently (simulate async work)COMMENT
14 more matches not shown…
Over-Commented Block29 hits · 29 pts
SeverityFileLineSnippetContext
LOWcsharp-book/RustBootstrapForCSharp.md801}COMMENT
LOWcsharp-book/src/ch03-built-in-types-and-variables.md461/* Multi-lineCOMMENT
LOWcsharp-book/src/ch16-3-rust-tooling-ecosystem.md61COMMENT
LOW…p-book/src/ch15-1-essential-crates-for-c-developers.md321}COMMENT
LOW…rns-book/src/ch14-testing-and-benchmarking-patterns.md61COMMENT
LOW…book/src/ch06-concurrency-vs-parallelism-vs-threads.md401 }COMMENT
LOWrust-patterns-book/src/ch02-traits-in-depth.md381COMMENT
LOW…rns-book/src/ch15-crate-architecture-and-api-design.md481// #[arg(short, long)]COMMENT
LOW…rns-book/src/ch15-crate-architecture-and-api-design.md501# type Error = String;COMMENT
LOW…rns-book/src/ch15-crate-architecture-and-api-design.md801/// Parses a diagnostic fault code from a string.COMMENT
LOW…k/src/ch06-dependency-management-and-supply-chain-s.md21which tracks known vulnerabilities in published crates.COMMENT
LOW…k/src/ch06-dependency-management-and-supply-chain-s.md241# Shows all paths from your crate to openssl-sysCOMMENT
LOW…k/src/ch05-miri-valgrind-and-sanitizers-verifying-u.md81mod tests {COMMENT
LOW…ring-book/src/ch08-compile-time-and-developer-tools.md161# x = unsafe code used by the buildCOMMENT
LOW…g-book/src/ch10-windows-and-conditional-compilation.md41// Operating systemCOMMENT
LOWpython-book/src/ch08-crates-and-modules.md1## Rust Modules vs Python PackagesCOMMENT
LOWpython-book/src/ch08-crates-and-modules.md21# ├── user.pyCOMMENT
LOWpython-book/src/ch12-closures-and-iterators.md381COMMENT
LOWpython-book/src/ch14-unsafe-rust-and-ffi.md61```rustCOMMENT
LOWpython-book/src/ch01-introduction-and-motivation.md301# COPY requirements.txt .COMMENT
LOWasync-book/src/ch06-building-futures-by-hand.md61 } else {COMMENT
LOW…k/src/ch06-dimensional-analysis-making-the-compiler.md181# #[derive(Debug, Clone, Copy, PartialEq, PartialOrd)]COMMENT
LOW…k/src/ch06-dimensional-analysis-making-the-compiler.md281- Comparing Celsius against Volts is a **compile error**COMMENT
LOW…k/src/ch15-const-fn-compile-time-correctness-proofs.md261COMMENT
LOW…k/src/ch08-capability-mixins-compile-time-hardware-.md81```COMMENT
LOW…k/src/ch08-capability-mixins-compile-time-hardware-.md181```rust,ignoreCOMMENT
LOWtype-driven-correctness-book/src/ch12-exercises.md761 format!("{}: {}/{} passed", self.name, passed, total)COMMENT
LOW…orrectness-book/src/ch18-redfish-server-walkthrough.md301// .name("PowerEdge R750".into())COMMENT
LOWc-cpp-book/src/ch13-concurrency.md381// Output (order may vary):COMMENT
Decorative Section Separators7 hits · 21 pts
SeverityFileLineSnippetContext
MEDIUMrust-patterns-book/src/ch02-traits-in-depth.md1086// ── Bus abstractions (traits the hardware team provides) ──────────COMMENT
MEDIUMrust-patterns-book/src/ch02-traits-in-depth.md1218// ── Concrete bus implementations (Linux platform) ────────────────COMMENT
MEDIUMrust-patterns-book/src/ch02-traits-in-depth.md1250// ── Production platform — all four buses ─────────────────────────COMMENT
MEDIUMrust-patterns-book/src/ch02-traits-in-depth.md1312 // ── Partial platform: only fan-related buses ─────────────────COMMENT
MEDIUMxtask/src/main.rs99// ── build ────────────────────────────────────────────────────────────COMMENT
MEDIUMxtask/src/main.rs404// ── serve ────────────────────────────────────────────────────────────COMMENT
MEDIUMxtask/src/main.rs485// ── clean ────────────────────────────────────────────────────────────COMMENT
Hallucination Indicators1 hit · 10 pts
SeverityFileLineSnippetContext
CRITICALpython-book/src/ch08-crates-and-modules.md25from myproject.utils.helpers import format_nameCODE
Fake / Example Data5 hits · 5 pts
SeverityFileLineSnippetContext
LOWcsharp-book/RustBootstrapForCSharp.md5205 name: "John Doe".to_string(),CODE
LOWcsharp-book/RustTrainingForCSharp.md1913 "John Doe".to_string(),CODE
LOW…p-book/src/ch15-1-essential-crates-for-c-developers.md164 "John Doe".to_string(),CODE
LOW…s-book/src/ch03-the-newtype-and-type-state-patterns.md56let email = Email::new("user@example.com").unwrap();CODE
LOW…k/src/ch07-validated-boundaries-parse-dont-validate.md179 Some("Acme Corp".to_string()) // stubCODE
Modern AI Meta-Vocabulary2 hits · 5 pts
SeverityFileLineSnippetContext
MEDIUMpython-book/src/ch15-migration-patterns.md417# Same Python orchestration, same tests, same deploymentCOMMENT
MEDIUMc-cpp-book/src/ch08-crates-and-modules.md620| `#ifdef TEST` mock functions | Trait-based dependency injection |CODE
Hyper-Verbose Identifiers3 hits · 3 pts
SeverityFileLineSnippetContext
LOWcsharp-book/RustBootstrapForCSharp.md116public class DataProcessorCODE
LOWcsharp-book/RustBootstrapForCSharp.md4859public class DataProcessorCODE
LOWcsharp-book/src/ch01-introduction-and-motivation.md25public class DataProcessorCODE
TODO Padding1 hit · 2 pts
SeverityFileLineSnippetContext
LOWc-cpp-book/src/ch08-crates-and-modules.md20 // TODO: implement pub fn add(a: u32, b: u32) -> u32COMMENT