Repository Analysis

tokio-rs/axum

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

7.4 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of tokio-rs/axum, a Rust project with 26,513 GitHub stars. SynthScan v2.0 examined 55,186 lines of code across 421 source files, recording 414 pattern matches distributed across 2 syntactic categories. The overall adjusted score of 7.4 places this repository in the Low AI signal band.

The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).

7.4
Adjusted Score
7.4
Raw Score
100%
Time Factor
2026-07-07
Last Push
26.5K
Stars
Rust
Language
55.2K
Lines of Code
421
Files
414
Pattern Hits
2026-07-14
Scan Date
0.00
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.

Severity Breakdown

Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.

CRITICAL 0HIGH 0MEDIUM 1LOW 413

Directory Score Breakdown

This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.

Pattern Findings

The scanner identified 414 distinct pattern matches across 2 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. 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 diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.

Over-Commented Block413 hits · 404 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/rejection.rs41 #[status = PAYLOAD_TOO_LARGE]COMMENT
LOWaxum-core/src/extract/mod.rs41/// Extractors that implement `FromRequestParts` cannot consume the request body and can thus beCOMMENT
LOWaxum-core/src/extract/mod.rs61 state: &S,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//! struct AppState {COMMENT
353 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