Repository Analysis

GitoxideLabs/gitoxide

An idiomatic, lean, fast & safe pure Rust implementation of Git

2.5 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of GitoxideLabs/gitoxide, a Rust project with 11,699 GitHub stars. SynthScan v2.0 examined 386,872 lines of code across 1890 source files, recording 922 pattern matches distributed across 8 syntactic categories. The overall adjusted score of 2.5 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).

2.5
Adjusted Score
2.5
Raw Score
100%
Time Factor
2026-07-14
Last Push
11.7K
Stars
Rust
Language
386.9K
Lines of Code
1.9K
Files
922
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 1MEDIUM 22LOW 899

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 922 distinct pattern matches across 8 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 Block881 hits · 879 pts
SeverityFileLineSnippetContext
LOWCargo.toml41## Can be amended with the `http-client-curl-rustls` feature to avoid `openssl` as backend.COMMENT
LOWCargo.toml61COMMENT
LOWCargo.toml81## Due to async client-networking not being implemented for most transports, this one supports only the 'git+tcp' and HTCOMMENT
LOWCargo.toml141COMMENT
LOWCargo.toml321[workspace.lints.rust]COMMENT
LOWdeny.toml41# The higher the value, the more closely the license text must be to theCOMMENT
LOWgix-zlib/src/lib.rs1#![deny(missing_docs)]COMMENT
LOWgix-zlib/src/lib.rs61#[derive(Copy, Clone, PartialEq, Eq, Debug)]COMMENT
LOWgix-zlib/src/stream/deflate.rs101#[derive(Copy, Clone, PartialEq, Eq, Debug)]COMMENT
LOWgix-zlib/src/stream/deflate.rs121 /// aligned on a byte boundary so that the decompressor can get all inputCOMMENT
LOWgix-sec/src/lib.rs1//! A shared trust model for `gitoxide` crates.COMMENT
LOWgix-negotiate/src/lib.rs1//! An implementation of negotiation algorithms to help the server figure out what we have in common so it can optimizeCOMMENT
LOWgix-negotiate/src/lib.rs21 ///COMMENT
LOWgix-negotiate/src/lib.rs121}COMMENT
LOWgix-transport/Cargo.toml41## NOTE: `https://` is NOT supported by default. You must enable one of the `http-client-reqwest-rust-tls`COMMENT
LOWgix-transport/tests/client/blocking_io/http/mod.rs241 "the authentication information is used in subsequent calls"COMMENT
LOWgix-transport/tests/client/blocking_io/http/mod.rs261/// Location: http://attacker.example/repo/info/refs?service=git-upload-packCOMMENT
LOWgix-transport/src/lib.rs1//! An implementation of the `git` transport layer, abstracting over all of its [versions][Protocol].COMMENT
LOWgix-transport/src/lib.rs21COMMENT
LOWgix-transport/src/client/non_io_types.rs1/// Configure how a `RequestWriter` behaves when writing bytes.COMMENT
LOWgix-transport/src/client/non_io_types.rs41 #[cfg(feature = "blocking-client")]COMMENT
LOWgix-transport/src/client/traits.rs21 Err(Error::AuthenticationUnsupported)COMMENT
LOWgix-transport/src/client/capabilities.rs21 #[error("An IO error occurred while reading V2 lines")]COMMENT
LOWgix-transport/src/client/capabilities.rs181 /// The information provided by the server upon first connection.COMMENT
LOWgix-transport/src/client/async_io/request.rs101 /// Doing so will also write the message type this instance was initialized with.COMMENT
LOWgix-transport/src/client/async_io/bufread_ext.rs21/// but leave support for reading lines directly without forcing them through `String`.COMMENT
LOWgix-transport/src/client/async_io/bufread_ext.rs41 /// Making this a trait method allows to handle differences between async and blocking.COMMENT
LOWgix-transport/src/client/async_io/traits.rs21 /// In protocol version one, this is set to a list of refs and their peeled counterparts.COMMENT
LOWgix-transport/src/client/blocking_io/request.rs101 /// Dissolve this instance into its write and read handles without any message-writing side-effect as in [`RequestWrCOMMENT
LOWgix-transport/src/client/blocking_io/connect.rs1pub use crate::client::non_io_types::connect::{Error, Options};COMMENT
LOWgix-transport/src/client/blocking_io/bufread_ext.rs21 /// Read a packet line into the internal buffer and return it.COMMENT
LOWgix-transport/src/client/blocking_io/traits.rs21}COMMENT
LOWgix-transport/src/client/blocking_io/http/mod.rs121// TODO: testing most of these fields requires a lot of effort, unless special flags to introspect ongoing requests are COMMENT
LOWgix-transport/src/client/blocking_io/http/mod.rs141 /// Refers to `http.lowSpeedTime`.COMMENT
LOWgix-transport/src/client/blocking_io/http/mod.rs161 /// more correctly.COMMENT
LOWgix-diff/src/lib.rs1//! Algorithms for diffing various git object types and for generating patches, highly optimized for performance.COMMENT
LOWgix-diff/src/lib.rs21pub struct Rewrites {COMMENT
LOWgix-diff/src/rewrites/mod.rs21/// Determine in which set of files to search for copies.COMMENT
LOWgix-diff/src/rewrites/tracker.rs41 /// Return the relation that this change may have with other changes.COMMENT
LOWgix-diff/src/rewrites/tracker.rs201 /// the destination of a copy or rename, or with `None` for source if no relation to otherCOMMENT
LOWgix-diff/src/tree/visit.rs1use gix_hash::ObjectId;COMMENT
LOWgix-diff/src/tree/mod.rs21/// A trait to allow responding to a traversal designed to figure out the [changes](visit::Change)COMMENT
LOWgix-diff/src/tree/function.rs1use std::{borrow::BorrowMut, collections::VecDeque};COMMENT
LOWgix-diff/src/tree_with_rewrites/change.rs21 relation: Option<tree::visit::Relation>,COMMENT
LOWgix-diff/src/tree_with_rewrites/change.rs41 /// a file into a symbolic link adjusts its mode.COMMENT
LOWgix-diff/src/tree_with_rewrites/change.rs61 /// [`Addition`](ChangeRef::Addition) acting as destination.COMMENT
LOWgix-diff/src/tree_with_rewrites/change.rs81 /// Note that this is the same as `id` if we require the [similarity to be 100%](super::Rewrites::percentage), bCOMMENT
LOWgix-diff/src/tree_with_rewrites/change.rs121 },COMMENT
LOWgix-diff/src/tree_with_rewrites/change.rs141 /// It may be empty if [file names](super::Options::location) is `None`.COMMENT
LOWgix-diff/src/tree_with_rewrites/change.rs161 ///COMMENT
LOWgix-diff/src/tree_with_rewrites/change.rs181 /// The mode of the entry after the rename.COMMENT
LOWgix-diff/src/tree_with_rewrites/function.rs1use bstr::BStr;COMMENT
LOWgix-diff/src/index/mod.rs81 id: Cow<'rhs, gix_hash::oid>,COMMENT
LOWgix-diff/src/index/function.rs1use std::{borrow::Cow, cell::RefCell, cmp::Ordering};COMMENT
LOWgix-diff/src/blob/mod.rs1//! For using text diffs, please have a look at the [`imara-diff` documentation](https://docs.rs/imara-diff),COMMENT
LOWgix-diff/src/blob/mod.rs21/// ```COMMENT
LOWgix-diff/src/blob/mod.rs61}COMMENT
LOWgix-diff/src/blob/mod.rs81 /// Please note that we don't make this call ourselves, but use it to determine that we should not run the our standCOMMENT
LOWgix-diff/src/blob/mod.rs101/// the content is considered binary.COMMENT
LOWgix-diff/src/blob/mod.rs121 path: PathBuf,COMMENT
821 more matches not shown…
AI Slop Vocabulary15 hits · 50 pts
SeverityFileLineSnippetContext
MEDIUMCargo.toml45## When used in conjunction with `http-client-curl-rustls`, the `openssl` crates will still be compiled, but won't be usCOMMENT
MEDIUMgix-transport/Cargo.toml32## If used in conjunction with other blocking implementations like `http-client-reqwest`, this one takes precedence.COMMENT
MEDIUMgix-transport/Cargo.toml35## If used in conjunction with `http-client-curl-openssl`, this feature will take precedence.COMMENT
MEDIUMgix-transport/Cargo.toml38## If used in conjunction with `http-client-curl-rust-tls`, the `rust-tls` feature will take precedence.COMMENT
MEDIUMgix-transport/Cargo.toml58## Suitable for implementing your own transports while using git's way of communication, typically in conjunction with aCOMMENT
MEDIUMgix-transport/Cargo.toml130## If used in conjunction with `async-client`, the `connect()` method will become available along with supporting the giCOMMENT
MEDIUMgix-imara-diff/Cargo.toml36# harness = falseCOMMENT
MEDIUMgix/Cargo.toml267## Make certain data structure threadsafe (or `Sync`) to facilitate multithreading. Further, many algorithms will now usCOMMENT
MEDIUMgix/Cargo.toml286## All [`gix::Error`](crate::Error) will produce error chains, which makes them work as expected in conjunction with `anCOMMENT
MEDIUMgix/src/lib.rs53//! to understand which cache levels exist and how to leverage them.COMMENT
MEDIUMgix/src/revision/walk.rs151/// **Note that we automatically leverage the commitgraph data structure**, but if you know that additional information COMMENT
MEDIUMgix-hashtable/src/lib.rs54 /// A Hasher for usage with `HashMap` keys that are already robust hashes (like an `ObjectId`).COMMENT
MEDIUMgix-hashtable/src/lib.rs94 /// A Hasher for usage with `HashMap` keys that are already robust hashes (like an `ObjectId`).COMMENT
MEDIUMgix-hashtable/src/lib.rs107/// A `HashMap` for usage with keys that are already robust hashes (like an `ObjectId`).COMMENT
MEDIUMgix-hashtable/src/lib.rs110/// A `HashSet` for usage with keys that are already robust hashes (like an `ObjectId`).COMMENT
Fake / Example Data13 hits · 19 pts
SeverityFileLineSnippetContext
LOWgix-imara-diff/src/lib.rs113//! let after = r#"// lorem ipsumCOMMENT
LOWgix-imara-diff/src/lib.rs134//! +// lorem ipsumCOMMENT
LOWgix/tests/gix/repository/object.rs927 config.set_value(&gix::config::tree::User::EMAIL, "user@example.com")?;CODE
LOWgix-mailmap/tests/snapshot/mod.rs22 Some(signature("Jane Doe", "jane@example.com")),CODE
LOWgix-mailmap/tests/snapshot/mod.rs27 Some(signature("Jane Doe", "jane@example.com")),CODE
LOWgix-mailmap/tests/snapshot/mod.rs33 Some(signature("Jane Doe", "jane@example.com")),CODE
LOWgix-mailmap/tests/snapshot/mod.rs62 Entry::change_name_and_email_by_name_and_email("Jane Doe", "jane@example.com", "Jane", "bugs@example.com"),CODE
LOWgix-mailmap/tests/snapshot/mod.rs69 Entry::change_name_and_email_by_email("Jane Doe", "jane@example.com", "jane@desktop.(none)"),CODE
LOWgix-mailmap/tests/snapshot/mod.rs71 Entry::change_name_and_email_by_email("Jane Doe", "jane@example.com", "jane@laptop.(none)"),CODE
LOWgix-mailmap/tests/parse/mod.rs33 Entry::change_name_and_email_by_email("Jane Doe", "jane@example.com", "jane@laptop.(none)"),CODE
LOWgix-mailmap/tests/parse/mod.rs34 Entry::change_name_and_email_by_email("Jane Doe", "jane@example.com", "jane@desktop.(none)"),CODE
LOWgix-mailmap/tests/parse/mod.rs35 Entry::change_name_and_email_by_name_and_email("Jane Doe", "jane@example.com", "Jane", "bugs@example.com"),CODE
LOWgix-mailmap/src/lib.rs24//! assert_eq!(resolved.name, "Jane Doe");COMMENT
Self-Referential Comments4 hits · 12 pts
SeverityFileLineSnippetContext
MEDIUM.github/workflows/release.yml30 # Create a draft release, initially with no binary assets attached.COMMENT
MEDIUM.github/workflows/ci.yml141 # Define the wrapper script for a compiler driver (for cc1 or cc1plus). This wrapperCOMMENT
MEDIUM.github/workflows/ci.yml157 # Define the script that performs the wrapping. This script shall be run once for eachCOMMENT
MEDIUM.github/workflows/ci.yml170 # Define a helper file that, when sourced, wires up the `~/display` symlink `wrapper1`COMMENT
Slop Phrases5 hits · 12 pts
SeverityFileLineSnippetContext
LOWgix-merge/tests/merge/tree/mod.rs15/// 1. Add it to the `tree_baseline.sh` script and don't forget to call theCOMMENT
LOWgix-merge/tests/merge/tree/mod.rs206 "BUG: update this number, and don't forget to remove a filter in the end"CODE
MEDIUMgix/src/repository/worktree.rs12 /// It's worth noting that a *bare* repository may have one or more linked worktrees, but has no *main* worktree,COMMENT
MEDIUMgix/src/revision/walk.rs207 /// It interacts with [`use_commit_graph`][Platform::use_commit_graph()] as one would expect, but it's worth noting COMMENT
MEDIUM.github/workflows/codeql.yml65 # If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize howCOMMENT
Synthetic Comment Markers1 hit · 8 pts
SeverityFileLineSnippetContext
HIGHgix-protocol/src/fetch/response/mod.rs70 /// The name of the ref, as requested by the client as a `want-ref` argument.COMMENT
TODO Padding2 hits · 3 pts
SeverityFileLineSnippetContext
LOWgix-url/src/parse.rs260 // TODO: implement UNC path special caseCOMMENT
LOWgix-object/src/commit/mod.rs33// TODO: implement `std::io::Read` to avoid allocationsCOMMENT
Redundant / Tautological Comments1 hit · 2 pts
SeverityFileLineSnippetContext
LOWetc/corpus/clone-repos.sh3# Check if there is input on stdinCOMMENT