Repository Analysis

serde-rs/serde

Serialization framework for Rust

3.6 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of serde-rs/serde, a Rust project with 10,720 GitHub stars. SynthScan v2.0 examined 43,952 lines of code across 229 source files, recording 219 pattern matches distributed across 1 syntactic category. The overall adjusted score of 3.6 places this repository in the Likely human-written 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).

3.6
Adjusted Score
3.6
Raw Score
100%
Time Factor
2026-07-11
Last Push
10.7K
Stars
Rust
Language
44.0K
Lines of Code
229
Files
219
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

Longitudinal tracking requires multiple scan runs. Once this repository is re-scanned after new commits land, this chart will visualise how the synthetic code signal evolves over time — enabling you to detect whether AI authorship is growing, stabilising, or being actively corrected by human engineers.

No multi-scan history yet — run the scanner again to build trend data.

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 0LOW 219

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 219 distinct pattern matches across 1 syntactic category. 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 Block219 hits · 158 pts
SeverityFileLineSnippetContext
LOWserde_core/src/std_error.rs1use crate::lib::{Debug, Display};COMMENT
LOWserde_core/src/std_error.rs21/// impl std::error::Error for MySerError {}COMMENT
LOWserde_core/src/lib.rs1//! Serde is a framework for ***ser***ializing and ***de***serializing Rust dataCOMMENT
LOWserde_core/src/lib.rs21//! <br>COMMENT
LOWserde_core/src/lib.rs41// Show which crate feature enables conditionally compiled APIs in documentation.COMMENT
LOWserde_core/src/macros.rs1// Super explicit first paragraph because this shows up at the top level andCOMMENT
LOWserde_core/src/macros.rs21/// #COMMENT
LOWserde_core/src/macros.rs41/// # }COMMENT
LOWserde_core/src/macros.rs61/// {COMMENT
LOWserde_core/src/macros.rs81/// # use serde::forward_to_deserialize_any;COMMENT
LOWserde_core/src/macros.rs101/// tuple_struct map struct enum identifier ignored_anyCOMMENT
LOWserde_core/src/private/string.rs1use crate::lib::*;COMMENT
LOWserde_core/src/de/mod.rs1//! Generic data structure deserialization framework.COMMENT
LOWserde_core/src/de/mod.rs21//! In rare cases it may be necessary to implement [`Deserialize`] manually forCOMMENT
LOWserde_core/src/de/mod.rs41//! serialization. Some types can be serialized by Serde but not deserialized.COMMENT
LOWserde_core/src/de/mod.rs61//! - Box\<str\>COMMENT
LOWserde_core/src/de/mod.rs81//! - **FFI types**:COMMENT
LOWserde_core/src/de/mod.rs101//! - SocketAddrV6COMMENT
LOWserde_core/src/de/mod.rs141 /// currently running.COMMENT
LOWserde_core/src/de/mod.rs161 diagnostic::on_unimplemented(COMMENT
LOWserde_core/src/de/mod.rs181 /// # }COMMENT
LOWserde_core/src/de/mod.rs201 ///COMMENT
LOWserde_core/src/de/mod.rs221 /// This is the value that was present in the input file or other sourceCOMMENT
LOWserde_core/src/de/mod.rs301}COMMENT
LOWserde_core/src/de/mod.rs321/// #COMMENT
LOWserde_core/src/de/mod.rs421 StructVariant => formatter.write_str("struct variant"),COMMENT
LOWserde_core/src/de/mod.rs441/// # use serde::de::{self, Unexpected, Visitor};COMMENT
LOWserde_core/src/de/mod.rs461///COMMENT
LOWserde_core/src/de/mod.rs521/// automatically generate `Deserialize` implementations for structs and enumsCOMMENT
LOWserde_core/src/de/mod.rs541/// deserializer lifetimes] for a more detailed explanation of these lifetimes.COMMENT
LOWserde_core/src/de/mod.rs561 fn deserialize<D>(deserializer: D) -> Result<Self, D::Error>COMMENT
LOWserde_core/src/de/mod.rs581 /// documentation because it is almost never what newbies are looking for.COMMENT
LOWserde_core/src/de/mod.rs601/// owned data.COMMENT
LOWserde_core/src/de/mod.rs621/// The relationship between `Deserialize` and `DeserializeOwned` in traitCOMMENT
LOWserde_core/src/de/mod.rs641/// deserialize a JSON array into a `Vec<T>` but it would be a freshly allocatedCOMMENT
LOWserde_core/src/de/mod.rs661///COMMENT
LOWserde_core/src/de/mod.rs681/// borrowed by `Self::Value` when deserialized. See the page [UnderstandingCOMMENT
LOWserde_core/src/de/mod.rs701/// // append array elements onto the end of an existing vector. The preexistingCOMMENT
LOWserde_core/src/de/mod.rs721/// // input.COMMENT
LOWserde_core/src/de/mod.rs741/// }COMMENT
LOWserde_core/src/de/mod.rs761/// T: Deserialize<'de>,COMMENT
LOWserde_core/src/de/mod.rs781/// }COMMENT
LOWserde_core/src/de/mod.rs821 fn deserialize<D>(self, deserializer: D) -> Result<T, D::Error>COMMENT
LOWserde_core/src/de/mod.rs841/// these various types.COMMENT
LOWserde_core/src/de/mod.rs861/// - The type of `()` in Rust. It represents an anonymous value containingCOMMENT
LOWserde_core/src/de/mod.rs881/// `[u64; 10]`.COMMENT
LOWserde_core/src/de/mod.rs901/// know that it is seeing a map. If the data format supportsCOMMENT
LOWserde_core/src/de/mod.rs921/// others.COMMENT
LOWserde_core/src/de/mod.rs941 diagnostic::on_unimplemented(COMMENT
LOWserde_core/src/de/mod.rs1041 fn deserialize_char<V>(self, visitor: V) -> Result<V::Value, Self::Error>COMMENT
LOWserde_core/src/de/mod.rs1061 /// data, indicate that to the `Deserializer` by using `deserialize_str`COMMENT
LOWserde_core/src/de/mod.rs1181 /// Deserializers for non-self-describing formats may not support this mode.COMMENT
LOWserde_core/src/de/mod.rs1201 /// # impl Timestamp {COMMENT
LOWserde_core/src/de/mod.rs1221 /// # unimplemented!()COMMENT
LOWserde_core/src/de/mod.rs1241 /// }COMMENT
LOWserde_core/src/de/mod.rs1261 whereCOMMENT
LOWserde_core/src/de/mod.rs1281///COMMENT
LOWserde_core/src/de/mod.rs1301/// E: de::Error,COMMENT
LOWserde_core/src/de/mod.rs1321 /// Format a message stating what data this Visitor expects to receive.COMMENT
LOWserde_core/src/de/mod.rs1501 /// The input contains a `char`.COMMENT
159 more matches not shown…