HTTP routing and request-handling library for Rust that focuses on ergonomics and modularity
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).
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.
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.
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.
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.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | axum-core/src/body.rs | 61 | /// This is useful in cases where a body is required to construct a | COMMENT |
| LOW | axum-core/src/lib.rs | 1 | //! Core types and traits for [`axum`]. | COMMENT |
| LOW | axum-core/src/response/append_headers.rs | 1 | use super::{IntoResponse, IntoResponseParts, Response, ResponseParts, TryIntoHeaderError}; | COMMENT |
| LOW | axum-core/src/response/append_headers.rs | 21 | /// ( | COMMENT |
| LOW | axum-core/src/response/into_response_parts.rs | 1 | use super::{IntoResponse, Response}; | COMMENT |
| LOW | axum-core/src/response/into_response_parts.rs | 21 | /// impl<'a> IntoResponseParts for SetHeader<'a> { | COMMENT |
| LOW | axum-core/src/response/into_response_parts.rs | 41 | /// } | COMMENT |
| LOW | axum-core/src/response/into_response_parts.rs | 61 | /// ( | COMMENT |
| LOW | axum-core/src/response/mod.rs | 21 | }; | COMMENT |
| LOW | axum-core/src/response/mod.rs | 41 | /// // two fallible functions with different error types | COMMENT |
| LOW | axum-core/src/response/mod.rs | 61 | /// | COMMENT |
| LOW | axum-core/src/response/mod.rs | 81 | /// ``` | COMMENT |
| LOW | axum-core/src/response/mod.rs | 141 | /// | COMMENT |
| LOW | axum-core/src/response/mod.rs | 181 | COMMENT | |
| LOW | axum-core/src/response/into_response.rs | 21 | /// # Implementing `IntoResponse` | COMMENT |
| LOW | axum-core/src/response/into_response.rs | 41 | /// } | COMMENT |
| LOW | axum-core/src/response/into_response.rs | 61 | /// # let _: Router = app; | COMMENT |
| LOW | axum-core/src/response/into_response.rs | 81 | /// pin::Pin, | COMMENT |
| LOW | axum-core/src/response/into_response.rs | 101 | /// // Now we can implement `IntoResponse` directly for `MyBody` | COMMENT |
| LOW | axum-core/src/extract/default_body_limit.rs | 1 | use self::private::DefaultBodyLimitService; | COMMENT |
| LOW | axum-core/src/extract/default_body_limit.rs | 21 | /// [`RequestExt::with_limited_body`] or [`RequestExt::into_limited_body`] | COMMENT |
| LOW | axum-core/src/extract/default_body_limit.rs | 41 | /// ``` | COMMENT |
| LOW | axum-core/src/extract/default_body_limit.rs | 61 | /// // this route has a different limit | COMMENT |
| LOW | axum-core/src/extract/default_body_limit.rs | 81 | COMMENT | |
| LOW | axum-core/src/extract/default_body_limit.rs | 101 | /// Router, | COMMENT |
| LOW | axum-core/src/extract/default_body_limit.rs | 121 | kind: DefaultBodyLimitKind::Disable, | COMMENT |
| LOW | axum-core/src/extract/default_body_limit.rs | 141 | /// let app: Router<()> = Router::new() | COMMENT |
| LOW | axum-core/src/extract/default_body_limit.rs | 161 | /// # Example | COMMENT |
| LOW | axum-core/src/extract/rejection.rs | 41 | #[status = PAYLOAD_TOO_LARGE] | COMMENT |
| LOW | axum-core/src/extract/mod.rs | 41 | /// Extractors that implement `FromRequestParts` cannot consume the request body and can thus be | COMMENT |
| LOW | axum-core/src/extract/mod.rs | 61 | state: &S, | COMMENT |
| LOW | axum-core/src/extract/from_ref.rs | 1 | /// Used to do reference-to-value conversions thus not consuming the input value. | COMMENT |
| LOW | axum-core/src/ext_traits/request.rs | 21 | /// ``` | COMMENT |
| LOW | axum-core/src/ext_traits/request.rs | 41 | /// async fn from_request(req: Request, _state: &S) -> Result<Self, Self::Rejection> { | COMMENT |
| LOW | axum-core/src/ext_traits/request.rs | 61 | /// Ok(Self(payload)) | COMMENT |
| LOW | axum-core/src/ext_traits/request.rs | 81 | /// | COMMENT |
| LOW | axum-core/src/ext_traits/request.rs | 101 | /// let requires_state = req.extract_with_state::<RequiresState, _, _>(state).await?; | COMMENT |
| LOW | axum-core/src/ext_traits/request.rs | 121 | /// ``` | COMMENT |
| LOW | axum-core/src/ext_traits/request.rs | 141 | /// Json, RequestExt, | COMMENT |
| LOW | axum-core/src/ext_traits/request.rs | 161 | /// | COMMENT |
| LOW | axum-core/src/ext_traits/request.rs | 181 | COMMENT | |
| LOW | axum-core/src/ext_traits/request.rs | 201 | /// | COMMENT |
| LOW | axum-core/src/ext_traits/request.rs | 221 | /// | COMMENT |
| LOW | axum-core/src/ext_traits/request_parts.rs | 21 | /// response::{Response, IntoResponse}, | COMMENT |
| LOW | axum-core/src/ext_traits/request_parts.rs | 41 | /// .await | COMMENT |
| LOW | axum-core/src/ext_traits/request_parts.rs | 61 | /// This is just a convenience for `E::from_request_parts(parts, state)`. | COMMENT |
| LOW | axum-core/src/ext_traits/request_parts.rs | 81 | /// { | COMMENT |
| LOW | axum/src/service_ext.rs | 1 | use crate::error_handling::HandleError; | COMMENT |
| LOW | axum/src/service_ext.rs | 21 | /// associated `ConnectInfo` in a request extension such that [`ConnectInfo`] | COMMENT |
| LOW | axum/src/lib.rs | 1 | //! axum is an HTTP routing and request-handling library that focuses on ergonomics and modularity. | COMMENT |
| LOW | axum/src/lib.rs | 21 | //! transport layer independence is not a goal, at least for the time being. | COMMENT |
| LOW | axum/src/lib.rs | 41 | //! } | COMMENT |
| LOW | axum/src/lib.rs | 61 | //! async fn root() {} | COMMENT |
| LOW | axum/src/lib.rs | 81 | //! ```rust | COMMENT |
| LOW | axum/src/lib.rs | 101 | //! Anything that implements [`IntoResponse`] can be returned from handlers. | COMMENT |
| LOW | axum/src/lib.rs | 121 | //! } | COMMENT |
| LOW | axum/src/lib.rs | 141 | //! | COMMENT |
| LOW | axum/src/lib.rs | 161 | //! use axum::{ | COMMENT |
| LOW | axum/src/lib.rs | 181 | //! // ... | COMMENT |
| LOW | axum/src/lib.rs | 201 | //! struct AppState { | COMMENT |
| 353 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | .github/workflows/release-plz.yml | 38 | # Create a PR with the new versions and changelog, preparing the next release. | COMMENT |