AI Slop Code Risk Monitor

rust-lang/rustup

SlopCodeMonitor badge for rust-lang/rustup Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

The Rust toolchain installer

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/rustup, a Rust project with 7,101 GitHub stars. SynthScan examined 48,853 lines of code across 150 source files, recording 57 pattern matches distributed across 7 syntactic categories. 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-31
Last Push
7.1K
Stars
Rust
Language
48.9K
Lines of Code
150
Files
57
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.1/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.1/100 · LOW

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

Agent Over-Engineering Ratio 0.7/100 · LOW

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

PR Review Velocity Impact 7.0/100 · LOW

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

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 57 distinct pattern matches across 7 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 Block42 hits · 42 pts
SeverityFileLineSnippetContext
LOWrustup-init.sh1#!/bin/shCOMMENT
LOWbuild.rs61 // Known DLLs are always loaded from the system directory whereas other DLLsCOMMENT
LOWrust-analyzer.example.toml1# Example rust-analyzer config for rustup development.COMMENT
LOWrust-analyzer.example.toml21# NOTE: may need explicit sysroot config.COMMENT
LOWci/sync-dist.py1# This script is used for syncing parts of the rustup dist serverCOMMENT
LOWci/deploy.bash1#!/bin/bashCOMMENT
LOWtests/suite/cli_rustup.rs8211.0.0 (hash-c-1)COMMENT
LOWtests/suite/cli_rustup.rs841// Windows due to some DLL issues. However, those aren't necessary anymore.COMMENT
LOWtests/suite/known_target_tuples.rs61/// For example, the parsing results of two 2-dash target tuples can be different:COMMENT
LOW.cargo/config.windows-cross.example.toml1# Windows cross-checking for #[cfg(windows)] code on UNIX clippy configCOMMENT
LOWsrc/test.rs121COMMENT
LOWsrc/toolchain.rs161 let mut new_path = vec![self.path.join("lib")];COMMENT
LOWsrc/toolchain.rs201 env_var::insert_path(sysenv::LOADER_PATH, new_path, None, cmd, self.cfg.process);COMMENT
LOWsrc/toolchain.rs221 // recursive call won't work because it is not executing theCOMMENT
LOWsrc/diskio/threaded.rs241 fn join(&mut self) -> Box<dyn Iterator<Item = CompletedIo> + '_> {COMMENT
LOWsrc/diskio/threaded.rs261 // Cheap wrap-around correctness check - we have 20k files, more thanCOMMENT
LOWsrc/diskio/mod.rs1/// Disk IO abstraction for rustup.COMMENT
LOWsrc/diskio/mod.rs21// dimensions - how much work we have queued, and how much work we executeCOMMENT
LOWsrc/diskio/mod.rs41// lets reduce this to (i) and (ii). Being unable to tell the differenceCOMMENT
LOWsrc/diskio/mod.rs141COMMENT
LOWsrc/diskio/mod.rs161// .. loop .. | writesCOMMENT
LOWsrc/diskio/mod.rs181// The implementation is done via a pair of MPSC channels. One to send data to write. InCOMMENT
LOWsrc/diskio/mod.rs541COMMENT
LOWsrc/test/clitools.rs61 /// Root for updates to rustup itself aka RUSTUP_UPDATE_ROOTCOMMENT
LOWsrc/test/clitools.rs81/// Currently, rustup utilizes [`snapbox`] (a snapshot-based testing library)COMMENT
LOWsrc/test/clitools.rs101/// # Redacting SnapshotsCOMMENT
LOWsrc/test/clitools.rs521}COMMENT
LOWsrc/test/clitools.rs781 }COMMENT
LOWsrc/bin/rustup-init.rs1//! The main Rustup command-line interfaceCOMMENT
LOWsrc/cli/job.rs1// FIXME: stolen from cargo. Should be extracted into a common crate.COMMENT
LOWsrc/cli/self_update.rs1//! Self-installation and updatingCOMMENT
LOWsrc/cli/self_update.rs21//! this happens after the update command exits.COMMENT
LOWsrc/cli/self_update.rs821 // Note that this function may not be running in the context of a freshCOMMENT
LOWsrc/cli/self_update.rs861 for tool in DUP_TOOLS {COMMENT
LOWsrc/cli/self_update.rs1221COMMENT
LOWsrc/cli/self_update/shell.rs1//! Paths and Unix shellsCOMMENT
LOWsrc/cli/self_update/shell.rs461 // executes them in a defined order.COMMENT
LOWsrc/cli/self_update/windows.rs721// executable can be deleted directly. On Windows you can't delete filesCOMMENT
LOWsrc/cli/self_update/windows.rs741// https://www.catch22.net/tuts/win32/self-deleting-executablesCOMMENT
LOWsrc/toolchain/names.rs1//! Overview of toolchain modeling.COMMENT
LOWsrc/toolchain/names.rs21//! `RUSTUP_TOOLCHAIN`: resolved or not resolved official names, custom names,COMMENT
LOWsrc/toolchain/names.rs581COMMENT
Excessive Try-Catch Wrapping5 hits · 6 pts
SeverityFileLineSnippetContext
LOW⚡ci/changelog_helper.py46 except Exception as e:STRING
MEDIUM⚡ci/changelog_helper.py47 print("An error occurred:", str(e))STRING
LOW⚡ci/changelog_helper.py56 except Exception as e:STRING
MEDIUM⚡ci/changelog_helper.py57 print("An error occurred:", str(e))STRING
MEDIUMci/changelog_helper.py50def read_file(file_name):CODE
Redundant / Tautological Comments4 hits · 6 pts
SeverityFileLineSnippetContext
LOWrustup-init.sh675 # Check if we have a broken snap curlCOMMENT
LOWrustup-init.sh822# Check if curl supports the --retry flag, then pass it to the curl invocation.COMMENT
LOWci/actions-templates/conclusion-template.yaml12 # Check if all needs were successful or skipped.COMMENT
LOW.github/workflows/ci.yaml1900 # Check if all needs were successful or skipped.COMMENT
Self-Referential Comments2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMci/shared.bash3# This file is intended to be sourced, so it is not being marked asCOMMENT
MEDIUMci/sync-dist.py109# Create the release informationCOMMENT
AI Slop Vocabulary2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMsrc/test/clitools.rs724/// Essentially we use this in `.read()` mode to gate access to `fork()`COMMENT
MEDIUMsrc/cli/completions.rs218 /// Used by completion tests to verify the completer is robustCOMMENT
Example Usage Blocks1 hit · 2 pts
SeverityFileLineSnippetContext
LOWci/deploy.bash5# Usage:COMMENT
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOWci/sync-dist.py32CODE