Repository Analysis

crossbeam-rs/crossbeam

Tools for concurrent programming in Rust

8.2 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of crossbeam-rs/crossbeam, a Rust project with 8,536 GitHub stars. SynthScan v2.0 examined 49,369 lines of code across 160 source files, recording 450 pattern matches distributed across 2 syntactic categories. The overall adjusted score of 8.2 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).

8.2
Adjusted Score
8.2
Raw Score
100%
Time Factor
2026-08-01
Last Push
8.5K
Stars
Rust
Language
49.4K
Lines of Code
160
Files
450
Pattern Hits
2026-08-02
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 450

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 450 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 Block449 hits · 402 pts
SeverityFileLineSnippetContext
LOWcrossbeam-epoch/src/collector.rs1/// Epoch-based garbage collector.COMMENT
LOWcrossbeam-epoch/src/lib.rs1//! Epoch-based memory reclamation.COMMENT
LOWcrossbeam-epoch/src/lib.rs21//!COMMENT
LOWcrossbeam-epoch/src/lib.rs41//!COMMENT
LOWcrossbeam-epoch/src/internal.rs1//! The global data and participant for garbage collection.COMMENT
LOWcrossbeam-epoch/src/internal.rs21//! Objects that get unlinked from concurrent data structures must be stashed away until the globalCOMMENT
LOWcrossbeam-epoch/src/internal.rs241 // For ThreadSanitizer that does not understand fences, we simulate the equivalent effect.COMMENT
LOWcrossbeam-epoch/src/internal.rs321// https://github.com/crossbeam-rs/crossbeam/issues/551COMMENT
LOWcrossbeam-epoch/src/internal.rs421 // a `SeqCst` fence.COMMENT
LOWcrossbeam-epoch/src/atomic.rs101/// qualifies such types that are pointed to by a single word.COMMENT
LOWcrossbeam-epoch/src/atomic.rs121 /// The type for initializers.COMMENT
LOWcrossbeam-epoch/src/atomic.rs141 ///COMMENT
LOWcrossbeam-epoch/src/atomic.rs181}COMMENT
LOWcrossbeam-epoch/src/atomic.rs281COMMENT
LOWcrossbeam-epoch/src/atomic.rs341 ///COMMENT
LOWcrossbeam-epoch/src/atomic.rs361 ///COMMENT
LOWcrossbeam-epoch/src/atomic.rs381 /// ```COMMENT
LOWcrossbeam-epoch/src/atomic.rs401 /// # unsafe { drop(a.into_owned()); } // avoid leakCOMMENT
LOWcrossbeam-epoch/src/atomic.rs421 /// let p = a.swap(Shared::null(), SeqCst, guard);COMMENT
LOWcrossbeam-epoch/src/atomic.rs441 /// the comparison fails. Using `Acquire` as success ordering makes the store partCOMMENT
LOWcrossbeam-epoch/src/atomic.rs481 CompareExchangeError {COMMENT
LOWcrossbeam-epoch/src/atomic.rs501 /// read-modify-write operation that takes place if the comparison with `current` succeeds.COMMENT
LOWcrossbeam-epoch/src/atomic.rs521 /// # unsafe { drop(a.load(SeqCst, guard).into_owned()); } // avoid leakCOMMENT
LOWcrossbeam-epoch/src/atomic.rs581 /// when the operation finally succeeds while the second describes theCOMMENT
LOWcrossbeam-epoch/src/atomic.rs601 ///COMMENT
LOWcrossbeam-epoch/src/atomic.rs641 ///COMMENT
LOWcrossbeam-epoch/src/atomic.rs661 #[cfg(not(miri))]COMMENT
LOWcrossbeam-epoch/src/atomic.rs681 /// use crossbeam_epoch::{self as epoch, Atomic, Shared};COMMENT
LOWcrossbeam-epoch/src/atomic.rs701 Shared::from_ptr(COMMENT
LOWcrossbeam-epoch/src/atomic.rs721 ///COMMENT
LOWcrossbeam-epoch/src/atomic.rs741 as *mut (),COMMENT
LOWcrossbeam-epoch/src/atomic.rs761 /// # ExamplesCOMMENT
LOWcrossbeam-epoch/src/atomic.rs781 unsafe { Owned::from_ptr(self.data.into_inner()) }COMMENT
LOWcrossbeam-epoch/src/atomic.rs801 /// ptr: Atomic<usize>,COMMENT
LOWcrossbeam-epoch/src/atomic.rs901 ///COMMENT
LOWcrossbeam-epoch/src/atomic.rs981 /// the same raw pointer.COMMENT
LOWcrossbeam-epoch/src/atomic.rs1001 ensure_aligned::<T>(raw);COMMENT
LOWcrossbeam-epoch/src/atomic.rs1021COMMENT
LOWcrossbeam-epoch/src/atomic.rs1041 /// ```COMMENT
LOWcrossbeam-epoch/src/atomic.rs1061 /// ```COMMENT
LOWcrossbeam-epoch/src/atomic.rs1081 /// Returns the same pointer, but tagged with `tag`. `tag` is truncated to be fit into theCOMMENT
LOWcrossbeam-epoch/src/atomic.rs1141COMMENT
LOWcrossbeam-epoch/src/atomic.rs1221 _marker: PhantomData,COMMENT
LOWcrossbeam-epoch/src/atomic.rs1241 /// assert_eq!(p.as_raw(), raw);COMMENT
LOWcrossbeam-epoch/src/atomic.rs1261 pub const fn null() -> Self {COMMENT
LOWcrossbeam-epoch/src/atomic.rs1301 ///COMMENT
LOWcrossbeam-epoch/src/atomic.rs1321 ///COMMENT
LOWcrossbeam-epoch/src/atomic.rs1341 /// actual object at the same time.COMMENT
LOWcrossbeam-epoch/src/atomic.rs1361 /// b.push(5);COMMENT
LOWcrossbeam-epoch/src/atomic.rs1381 /// Dereferencing a pointer is unsafe because it could be pointing to invalid memory.COMMENT
LOWcrossbeam-epoch/src/atomic.rs1401 /// let p = a.load(SeqCst, guard);COMMENT
LOWcrossbeam-epoch/src/atomic.rs1421 ///COMMENT
LOWcrossbeam-epoch/src/atomic.rs1441 debug_assert!(!self.is_null(), "converting a null `Shared` into `Owned`");COMMENT
LOWcrossbeam-epoch/src/atomic.rs1461 /// let p = a.load(SeqCst, guard);COMMENT
LOWcrossbeam-epoch/src/atomic.rs1481 /// use std::sync::atomic::Ordering::SeqCst;COMMENT
LOWcrossbeam-epoch/src/atomic.rs1501 /// use std::sync::atomic::Ordering::SeqCst;COMMENT
LOWcrossbeam-epoch/src/atomic.rs1521 /// # PanicsCOMMENT
LOWcrossbeam-epoch/src/guard.rs1use core::{fmt, mem};COMMENT
LOWcrossbeam-epoch/src/guard.rs21/// let guard = &epoch::pin();COMMENT
LOWcrossbeam-epoch/src/guard.rs41/// // Load the heap-allocated object and create pointer `p` on the stack.COMMENT
389 more matches not shown…
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOWcrossbeam-channel/benchmarks/plot.py2CODE