3.1

Adjusted Signal

3.1

Raw Pattern Score

100%

Time Factor

2026-08-24

Last Push

14.8K

Stars

Rust

Language

29.4K

Lines of Code

281

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

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

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

PR Review Velocity Impact 14.6/100 · LOW

Which changes need focused human review? 81 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 6LOW 75

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 81 distinct pattern matches across 2 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 Block75 hits · 75 pts

Severity	File	Line	Snippet	Context
LOW	solutions/compound-types/enum.md	141	fn prepend(self, elem: u32) -> List {	COMMENT
LOW	zh-CN/assets/mini-redis/examples/pub.rs	1	//! Publish to a redis channel example.	COMMENT
LOW	zh-CN/assets/mini-redis/examples/hello_world.rs	1	//! Hello world server.	COMMENT
LOW	zh-CN/assets/mini-redis/examples/sub.rs	1	//! Subscribe to a redis channel example.	COMMENT
LOW	zh-CN/assets/mini-redis/src/shutdown.rs	1	use tokio::sync::broadcast;	COMMENT
LOW	zh-CN/assets/mini-redis/src/blocking_client.rs	1	//! Minimal blocking Redis client implementation	COMMENT
LOW	zh-CN/assets/mini-redis/src/blocking_client.rs	21	inner: crate::client::Client,	COMMENT
LOW	zh-CN/assets/mini-redis/src/blocking_client.rs	41	}	COMMENT
LOW	zh-CN/assets/mini-redis/src/blocking_client.rs	61	/// ```no_run	COMMENT
LOW	zh-CN/assets/mini-redis/src/blocking_client.rs	81		COMMENT
LOW	zh-CN/assets/mini-redis/src/blocking_client.rs	101	pub fn get(&mut self, key: &str) -> crate::Result<Option<Bytes>> {	COMMENT
LOW	zh-CN/assets/mini-redis/src/blocking_client.rs	121	/// let mut client = blocking_client::connect("localhost:6379").unwrap();	COMMENT
LOW	zh-CN/assets/mini-redis/src/blocking_client.rs	141	/// If key already holds a value, it is overwritten. Any previous time to	COMMENT
LOW	zh-CN/assets/mini-redis/src/blocking_client.rs	161	///	COMMENT
LOW	zh-CN/assets/mini-redis/src/blocking_client.rs	181	}	COMMENT
LOW	zh-CN/assets/mini-redis/src/client.rs	21	///	COMMENT
LOW	zh-CN/assets/mini-redis/src/client.rs	61	///	COMMENT
LOW	zh-CN/assets/mini-redis/src/client.rs	81		COMMENT
LOW	zh-CN/assets/mini-redis/src/client.rs	101	/// #[tokio::main]	COMMENT
LOW	zh-CN/assets/mini-redis/src/client.rs	121	//	COMMENT
LOW	zh-CN/assets/mini-redis/src/client.rs	141	///	COMMENT
LOW	zh-CN/assets/mini-redis/src/client.rs	161	// used to set a value with an expiration. The common parts of both	COMMENT
LOW	zh-CN/assets/mini-redis/src/client.rs	181	/// favorable.	COMMENT
LOW	zh-CN/assets/mini-redis/src/client.rs	241	/// There is no guarantee that these subscribers receive the message as they	COMMENT
LOW	zh-CN/assets/mini-redis/src/lib.rs	1	//! A minimal (i.e. very incomplete) implementation of a Redis server and	COMMENT
LOW	zh-CN/assets/mini-redis/src/lib.rs	61	///	COMMENT
LOW	zh-CN/assets/mini-redis/src/server.rs	21	/// Contains the key / value store as well as the broadcast channels for	COMMENT
LOW	zh-CN/assets/mini-redis/src/server.rs	41	/// Broadcasts a shutdown signal to all active connections.	COMMENT
LOW	zh-CN/assets/mini-redis/src/server.rs	61	/// `shutdown_complete_rx.recv()` completing with `None`. At this point, it	COMMENT
LOW	zh-CN/assets/mini-redis/src/server.rs	81	/// When `Listener` receives an inbound connection, the `TcpStream` is	COMMENT
LOW	zh-CN/assets/mini-redis/src/server.rs	101	/// which point the connection is terminated.	COMMENT
LOW	zh-CN/assets/mini-redis/src/server.rs	121		COMMENT
LOW	zh-CN/assets/mini-redis/src/server.rs	141	// Initialize the listener state	COMMENT
LOW	zh-CN/assets/mini-redis/src/server.rs	161	//	COMMENT
LOW	zh-CN/assets/mini-redis/src/server.rs	201	// Drop final `Sender` so the `Receiver` below can complete	COMMENT
LOW	zh-CN/assets/mini-redis/src/server.rs	221	/// operating system has reached an internal limit for max number of	COMMENT
LOW	zh-CN/assets/mini-redis/src/server.rs	241	//	COMMENT
LOW	zh-CN/assets/mini-redis/src/server.rs	321	/// written back to the socket.	COMMENT
LOW	zh-CN/assets/mini-redis/src/server.rs	361	//	COMMENT
LOW	zh-CN/assets/mini-redis/src/db.rs	21	/// `Db` contains a `HashMap` storing the key/value data and all	COMMENT
LOW	zh-CN/assets/mini-redis/src/db.rs	41	/// not a Tokio mutex. This is because there are no asynchronous operations	COMMENT
LOW	zh-CN/assets/mini-redis/src/db.rs	61	struct State {	COMMENT
LOW	zh-CN/assets/mini-redis/src/db.rs	161		COMMENT
LOW	zh-CN/assets/mini-redis/src/db.rs	241	// broadcast channel and associate it with the key. If one already	COMMENT
LOW	zh-CN/assets/mini-redis/src/parse.rs	1	use crate::Frame;	COMMENT
LOW	zh-CN/assets/mini-redis/src/buffer.rs	1	use crate::client::Client;	COMMENT
LOW	zh-CN/assets/mini-redis/src/buffer.rs	41	}	COMMENT
LOW	zh-CN/assets/mini-redis/src/connection.rs	1	use crate::frame::{self, Frame};	COMMENT
LOW	zh-CN/assets/mini-redis/src/connection.rs	41	buffer: BytesMut::with_capacity(4 * 1024),	COMMENT
LOW	zh-CN/assets/mini-redis/src/connection.rs	81	}	COMMENT
LOW	zh-CN/assets/mini-redis/src/connection.rs	101	// received.	COMMENT
LOW	zh-CN/assets/mini-redis/src/connection.rs	121	let frame = Frame::parse(&mut buf)?;	COMMENT
LOW	zh-CN/assets/mini-redis/src/connection.rs	141	Err(Incomplete) => Ok(None),	COMMENT
LOW	zh-CN/assets/mini-redis/src/cmd/subscribe.rs	41	}	COMMENT
LOW	zh-CN/assets/mini-redis/src/cmd/subscribe.rs	61	/// SUBSCRIBE channel [channel ...]	COMMENT
LOW	zh-CN/assets/mini-redis/src/cmd/subscribe.rs	81	Ok(s) => channels.push(s),	COMMENT
LOW	zh-CN/assets/mini-redis/src/cmd/subscribe.rs	101	/// [here]: https://redis.io/topics/pubsub	COMMENT
LOW	zh-CN/assets/mini-redis/src/cmd/subscribe.rs	201		COMMENT
LOW	zh-CN/assets/mini-redis/src/cmd/subscribe.rs	281	}	COMMENT
LOW	zh-CN/assets/mini-redis/src/cmd/subscribe.rs	301	/// On success, the `Unsubscribe` value is returned. If the frame is	COMMENT
15 more matches not shown…

Decorative Section Separators6 hits · 16 pts

Severity	File	Line	Snippet	Context
MEDIUM⚡	solutions/lifetime/basic.md	7	let i = 3; // Lifetime for `i` starts. ────────────────┐	CODE
MEDIUM⚡	solutions/lifetime/basic.md	13	} // `borrow1 ends. ──────────────────────────────────┘│	CODE
MEDIUM⚡	solutions/lifetime/basic.md	20	} // `borrow2` ends. ─────────────────────────────────┘│	CODE
MEDIUM⚡	solutions/lifetime/basic.md	22	} // Lifetime ends. ─────────────────────────────────────┘	CODE
MEDIUM	zh-CN/src/lifetime/basic.md	20	} // `borrow1` 生命周期结束. ──────────────────────────────────┘	CODE
MEDIUM	en/src/lifetime/basic.md	20	} // `borrow1 ends. ──────────────────────────────────┘	CODE

origin-bi/rust-by-practice

Open-Source Code Quality, Security and Technical Debt Review