AI Slop Code RIsk Monitor

tokio-rs/axum

HTTP routing and request-handling library for Rust that focuses on ergonomics and modularity

7.4 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for tokio-rs/axum, a Rust project with 27,441 GitHub stars. SynthScan examined 57,464 lines of code across 425 source files, recording 435 pattern matches distributed across 2 syntactic categories. The legacy adjusted pattern signal is 7.4 (Moderate 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.

7.4
Adjusted Signal
7.4
Raw Pattern Score
100%
Time Factor
2026-10-09
Last Push
27.4K
Stars
Rust
Language
57.5K
Lines of Code
425
Files
435
Pattern Hits
2026-10-12
Scan Date
0.00
HC Hit Rate

Risk Review · v3

Use each vector to guide manual verification of the underlying findings.

Cognitive Ownership Risk 30.9/100 · MEDIUM

Can maintainers explain intent, assumptions, and trade-offs? 435 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 31.6/100 · MEDIUM

Which changes need focused human review? 435 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 1LOW 434

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 435 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 Block434 hits · 422 pts
SeverityFileLineSnippetContext
LOWaxum-core/src/body.rs61 /// This is useful in cases where a body is required to construct aCOMMENT
LOWaxum-core/src/lib.rs1//! Core types and traits for [`axum`].COMMENT
LOWaxum-core/src/response/append_headers.rs1use super::{IntoResponse, IntoResponseParts, Response, ResponseParts, TryIntoHeaderError};COMMENT
LOWaxum-core/src/response/append_headers.rs21/// (COMMENT
LOWaxum-core/src/response/into_response_parts.rs1use super::{IntoResponse, Response};COMMENT
LOWaxum-core/src/response/into_response_parts.rs21/// impl<'a> IntoResponseParts for SetHeader<'a> {COMMENT
LOWaxum-core/src/response/into_response_parts.rs41/// }COMMENT
LOWaxum-core/src/response/into_response_parts.rs61/// (COMMENT
LOWaxum-core/src/response/mod.rs21};COMMENT
LOWaxum-core/src/response/mod.rs41/// // two fallible functions with different error typesCOMMENT
LOWaxum-core/src/response/mod.rs61///COMMENT
LOWaxum-core/src/response/mod.rs81/// ```COMMENT
LOWaxum-core/src/response/mod.rs141///COMMENT
LOWaxum-core/src/response/mod.rs181COMMENT
LOWaxum-core/src/response/into_response.rs21/// # Implementing `IntoResponse`COMMENT
LOWaxum-core/src/response/into_response.rs41/// }COMMENT
LOWaxum-core/src/response/into_response.rs61/// # let _: Router = app;COMMENT
LOWaxum-core/src/response/into_response.rs81/// pin::Pin,COMMENT
LOWaxum-core/src/response/into_response.rs101/// // Now we can implement `IntoResponse` directly for `MyBody`COMMENT
LOWaxum-core/src/extract/default_body_limit.rs1use self::private::DefaultBodyLimitService;COMMENT
LOWaxum-core/src/extract/default_body_limit.rs21/// [`RequestExt::with_limited_body`] or [`RequestExt::into_limited_body`]COMMENT
LOWaxum-core/src/extract/default_body_limit.rs41/// ```COMMENT
LOWaxum-core/src/extract/default_body_limit.rs61/// // this route has a different limitCOMMENT
LOWaxum-core/src/extract/default_body_limit.rs81COMMENT
LOWaxum-core/src/extract/default_body_limit.rs101 /// Router,COMMENT
LOWaxum-core/src/extract/default_body_limit.rs121 kind: DefaultBodyLimitKind::Disable,COMMENT
LOWaxum-core/src/extract/default_body_limit.rs141 /// let app: Router<()> = Router::new()COMMENT
LOWaxum-core/src/extract/default_body_limit.rs161 /// # ExampleCOMMENT
LOWaxum-core/src/extract/mod.rs41/// Types that can be created from request parts.COMMENT
LOWaxum-core/src/extract/mod.rs61 fn from_request_parts(COMMENT
LOWaxum-core/src/extract/from_ref.rs1/// Used to do reference-to-value conversions thus not consuming the input value.COMMENT
LOWaxum-core/src/ext_traits/request.rs21 /// ```COMMENT
LOWaxum-core/src/ext_traits/request.rs41 /// async fn from_request(req: Request, _state: &S) -> Result<Self, Self::Rejection> {COMMENT
LOWaxum-core/src/ext_traits/request.rs61 /// Ok(Self(payload))COMMENT
LOWaxum-core/src/ext_traits/request.rs81 ///COMMENT
LOWaxum-core/src/ext_traits/request.rs101 /// let requires_state = req.extract_with_state::<RequiresState, _, _>(state).await?;COMMENT
LOWaxum-core/src/ext_traits/request.rs121 /// ```COMMENT
LOWaxum-core/src/ext_traits/request.rs141 /// Json, RequestExt,COMMENT
LOWaxum-core/src/ext_traits/request.rs161 ///COMMENT
LOWaxum-core/src/ext_traits/request.rs181COMMENT
LOWaxum-core/src/ext_traits/request.rs201 ///COMMENT
LOWaxum-core/src/ext_traits/request.rs221 ///COMMENT
LOWaxum-core/src/ext_traits/request_parts.rs21 /// response::{Response, IntoResponse},COMMENT
LOWaxum-core/src/ext_traits/request_parts.rs41 /// .awaitCOMMENT
LOWaxum-core/src/ext_traits/request_parts.rs61 /// This is just a convenience for `E::from_request_parts(parts, state)`.COMMENT
LOWaxum-core/src/ext_traits/request_parts.rs81 /// {COMMENT
LOWaxum/src/service_ext.rs1use crate::error_handling::HandleError;COMMENT
LOWaxum/src/service_ext.rs21 /// associated `ConnectInfo` in a request extension such that [`ConnectInfo`]COMMENT
LOWaxum/src/lib.rs1//! axum is an HTTP routing and request-handling library that focuses on ergonomics and modularity.COMMENT
LOWaxum/src/lib.rs21//! transport layer independence is not a goal, at least for the time being.COMMENT
LOWaxum/src/lib.rs41//! }COMMENT
LOWaxum/src/lib.rs61//! async fn root() {}COMMENT
LOWaxum/src/lib.rs81//! ```rustCOMMENT
LOWaxum/src/lib.rs101//! Anything that implements [`IntoResponse`] can be returned from handlers.COMMENT
LOWaxum/src/lib.rs121//! }COMMENT
LOWaxum/src/lib.rs141//!COMMENT
LOWaxum/src/lib.rs161//! use axum::{COMMENT
LOWaxum/src/lib.rs181//! // ...COMMENT
LOWaxum/src/lib.rs201//! `Box::leak` for state initialized in `main`, including when state initializationCOMMENT
LOWaxum/src/lib.rs221//! fn main() {COMMENT
374 more matches not shown…
Self-Referential Comments1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUM.github/workflows/release-plz.yml38 # Create a PR with the new versions and changelog, preparing the next release.COMMENT