AI Slop Code Risk Monitor

sunface/rust-course

Name: sunface/rust-course — 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).

什么？你敢放心的把后背交给 AI? 我赌你不敢，那就来学学 AI 时代最酷、最安全、最快的语言吧。本书拥有全面且深入的讲解、生动贴切的示例、德芙般丝滑的内容，这可能是目前最用心的 Rust 中文学习教程 / Book

0.5 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for sunface/rust-course, a Rust project with 31,079 GitHub stars. SynthScan examined 67,627 lines of code across 524 source files, recording 31 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 0.5 (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.

0.5

Adjusted Signal

0.5

Raw Pattern Score

100%

Time Factor

2026-10-30

Last Push

31.1K

Stars

Rust

Language

67.6K

Lines of Code

524

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

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

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

PR Review Velocity Impact 2.3/100 · LOW

Which changes need focused human review? 31 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 31

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 31 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 Block25 hits · 25 pts

Severity	File	Line	Snippet	Context
LOW	assets/rustlings-zh/exercises/quiz1.rs	1	// quiz1.rs	COMMENT
LOW	assets/rustlings-zh/exercises/conversions/from_str.rs	21	// Incorrect number of fields	COMMENT
LOW	assets/rustlings-zh/exercises/conversions/from_into.rs	21	// Your task is to complete this implementation	COMMENT
LOW	assets/rustlings-zh/exercises/error_handling/errors2.rs	1	// errors2.rs	COMMENT
LOW	…stlings-zh/exercises/advanced_errors/advanced_errs2.rs	1	// advanced_errs2.rs	COMMENT
LOW	assets/rustlings-zh/exercises/variables/variables1.rs	1	// variables1.rs	COMMENT
LOW	…/rustlings-zh/exercises/standard_library_types/arc1.rs	1	// arc1.rs	COMMENT
LOW	…/rustlings-zh/exercises/standard_library_types/box1.rs	1	// box1.rs	COMMENT
LOW	…ings-zh/exercises/standard_library_types/iterators4.rs	1	// iterators4.rs	COMMENT
LOW	…ings-zh/exercises/standard_library_types/iterators5.rs	1	// iterators5.rs	COMMENT
LOW	assets/rustlings-zh/src/main.rs	61		COMMENT
LOW	assets/rustlings-zh/src/main.rs	81	#[argh(subcommand, name = "list")]	COMMENT
LOW	assets/writing-material/posts/tests/doc_test.md	1	## Documentation testing	COMMENT
LOW	assets/writing-material/posts/tests/doc_test.md	21	/// The next function divides two numbers.	COMMENT
LOW	assets/writing-material/posts/tests/doc_test.md	41	}	COMMENT
LOW	…c/too-many-lists/production-unsafe-deque/final-code.md	521	//	COMMENT
LOW	…c/too-many-lists/production-unsafe-deque/final-code.md	581	// cur	COMMENT
LOW	…c/too-many-lists/production-unsafe-deque/final-code.md	641	// input.front -> 1 <-> 2 <- input.back	COMMENT
LOW	…c/too-many-lists/production-unsafe-deque/final-code.md	701	// We have this:	COMMENT
LOW	…-lists/production-unsafe-deque/implementing-cursors.md	521	// We have this:	COMMENT
LOW	…-lists/production-unsafe-deque/implementing-cursors.md	581		COMMENT
LOW	…-lists/production-unsafe-deque/implementing-cursors.md	641	}	COMMENT
LOW	…-lists/production-unsafe-deque/implementing-cursors.md	701		COMMENT
LOW	src/basic/comment.md	61	当查看一个 `crates.io` 上的包时，往往需要通过它提供的文档来浏览相关的功能特性、使用方式，这种文档就是通过文档注释实现的。	COMMENT
LOW	src/basic/crate-module/use.md	441	my_mod::indirect_access();	COMMENT

Verbosity Indicators2 hits · 4 pts

Severity	File	Line	Snippet	Context
LOW⚡	…/rustlings-zh/exercises/standard_library_types/box1.rs	12	// Step 1: use a `Box` in the enum definition to make the code compile	COMMENT
LOW⚡	…/rustlings-zh/exercises/standard_library_types/box1.rs	13	// Step 2: create both empty and non-empty cons lists by replacing `unimplemented!()`	COMMENT

Structural Annotation Overuse2 hits · 4 pts

Severity	File	Line	Snippet	Context
LOW⚡	…/rustlings-zh/exercises/standard_library_types/box1.rs	12	// Step 1: use a `Box` in the enum definition to make the code compile	COMMENT
LOW⚡	…/rustlings-zh/exercises/standard_library_types/box1.rs	13	// Step 2: create both empty and non-empty cons lists by replacing `unimplemented!()`	COMMENT

TODO Padding1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	…stlings-zh/exercises/advanced_errors/advanced_errs1.rs	30	// TODO: implement another instance of the `From` trait here so that the	COMMENT

Fake / Example Data1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	assets/rustlings-zh/CONTRIBUTING.md	123	BREAKING CHANGE: This has to be done because lorem ipsum dolor	CODE