Repository Analysis

orhun/git-cliff

A highly customizable Changelog Generator that follows Conventional Commit specifications ⛰️

3.8 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of orhun/git-cliff, a Rust project with 12,018 GitHub stars. SynthScan v2.0 examined 29,326 lines of code across 184 source files, recording 71 pattern matches distributed across 4 syntactic categories. The overall adjusted score of 3.8 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.8
Adjusted Score
3.8
Raw Score
100%
Time Factor
2026-07-12
Last Push
12.0K
Stars
Rust
Language
29.3K
Lines of Code
184
Files
71
Pattern Hits
2026-07-14
Scan Date
0.05
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 9MEDIUM 0LOW 62

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 71 distinct pattern matches across 4 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 Block45 hits · 45 pts
SeverityFileLineSnippetContext
LOWcliff.toml81# See https://www.conventionalcommits.orgCOMMENT
LOWcliff.toml121filter_commits = falseCOMMENT
LOWgit-cliff-core/Cargo.toml41## Enable integration with Gitea.COMMENT
LOWgit-cliff-core/src/commit.rs21#[derive(Debug, Clone, Eq, PartialEq, Deserialize, Serialize)]COMMENT
LOWgit-cliff-core/src/commit.rs121 #[serde(skip_deserializing)]COMMENT
LOWgit-cliff-core/src/commit.rs141 /// Arbitrary data to be used with the `--from-context` CLI option.COMMENT
LOWgit-cliff-core/src/error.rs1use thiserror::Error as ThisError;COMMENT
LOWgit-cliff-core/src/error.rs21{0:?} is not a valid commit range. Did you provide the correct arguments?"COMMENT
LOWgit-cliff-core/src/error.rs41 /// Error that may occur while generating changelog.COMMENT
LOWgit-cliff-core/src/error.rs61 EmbeddedError(String),COMMENT
LOWgit-cliff-core/src/error.rs81 /// Error that may occur while parsing a `SemVer` version or versionCOMMENT
LOWgit-cliff-core/src/error.rs101 UrlParseError(#[from] url::ParseError),COMMENT
LOWgit-cliff-core/src/config.rs81 /// Output file path.COMMENT
LOWgit-cliff-core/src/config.rs101 pub filter_unconventional: bool,COMMENT
LOWgit-cliff-core/src/config.rs121 /// Regex to select git tags that represent releases.COMMENT
LOWgit-cliff-core/src/config.rs141 /// Limit the total number of commits included in the changelog.COMMENT
LOWgit-cliff-core/src/config.rs201COMMENT
LOWgit-cliff-core/src/config.rs341/// Version bump type.COMMENT
LOWgit-cliff-core/src/config.rs361 /// - A patch version update if the major version is 0.COMMENT
LOWgit-cliff-core/src/config.rs381 ///COMMENT
LOWgit-cliff-core/src/config.rs441 /// Group of the commit.COMMENT
LOWgit-cliff-core/src/release.rs21pub struct Release<'a> {COMMENT
LOWgit-cliff-core/src/release.rs41 /// Submodule commits.COMMENT
LOWgit-cliff-core/src/lib.rs1//! A highly customizable changelog generator ⛰️COMMENT
LOWgit-cliff-core/src/lib.rs21/// Config file parser.COMMENT
LOWgit-cliff-core/src/lib.rs41pub mod statistics;COMMENT
LOWgit-cliff-core/src/statistics.rs21/// Aggregated statistics about commits in the release.COMMENT
LOWgit-cliff-core/src/repo.rs101 }COMMENT
LOWgit-cliff-core/src/template.rs61 /// Behaves like Tera's built-in `group_by(attribute="group")` filter, butCOMMENT
LOWgit-cliff-core/src/changelog.rs201 self.releases[release_index].previous =COMMENT
LOWgit-cliff-core/src/changelog.rs361 /// - CommitsCOMMENT
LOWgit-cliff-core/src/changelog.rs401 }COMMENT
LOWgit-cliff-core/src/remote/azure_devops.rs61#[derive(Default, Debug, Clone, PartialEq, Serialize, Deserialize)]COMMENT
LOWgit-cliff-core/src/remote/gitlab.rs21 /// Optional Description of projectCOMMENT
LOWgit-cliff-core/src/remote/bitbucket.rs41/// Bitbucket Pagination HeaderCOMMENT
LOWgit-cliff-core/src/remote/bitbucket.rs61/// Author of the commit.COMMENT
LOWconfig/cliff.toml21{% endfor %}COMMENT
LOWconfig/cliff.toml41# Exclude commits that do not match the conventional commits specification.COMMENT
LOWwebsite/blog/git-cliff-2.2.0.md41#COMMENT
LOWexamples/github.toml61# An array of regex based postprocessors to modify the changelog.COMMENT
LOWexamples/azure-devops-keepachangelog.toml1# git-cliff ~ configuration fileCOMMENT
LOW.github/workflows/codeql.yml1# For most projects, this workflow file will not need changing; you simply needCOMMENT
LOWgit-cliff/src/lib.rs501/// fn main() -> Result<()> {COMMENT
LOWgit-cliff/src/lib.rs521/// use git_cliff_core::error::Result;COMMENT
LOWgit-cliff/src/args.rs221 allow_hyphen_values = trueCOMMENT
Cross-File Repetition9 hits · 45 pts
SeverityFileLineSnippetContext
HIGHexamples/scoped.toml0# changelog\n all notable changes to this project will be documented in this file.\nSTRING
HIGHexamples/scopesorted.toml0# changelog\n all notable changes to this project will be documented in this file.\nSTRING
HIGHexamples/detailed.toml0# changelog\n all notable changes to this project will be documented in this file.\nSTRING
HIGHexamples/unconventional.toml0# changelog\n all notable changes to this project will be documented in this file.\nSTRING
HIGHexamples/statistics.toml0# changelog\n all notable changes to this project will be documented in this file.\nSTRING
HIGHexamples/gitlab-keepachangelog.toml0# changelog\n all notable changes to this project will be documented in this file. the format is based on [keep a changeSTRING
HIGHexamples/keepachangelog.toml0# changelog\n all notable changes to this project will be documented in this file. the format is based on [keep a changeSTRING
HIGHexamples/azure-devops-keepachangelog.toml0# changelog\n all notable changes to this project will be documented in this file. the format is based on [keep a changeSTRING
HIGHexamples/github-keepachangelog.toml0# changelog\n all notable changes to this project will be documented in this file. the format is based on [keep a changeSTRING
Fake / Example Data16 hits · 20 pts
SeverityFileLineSnippetContext
LOWgit-cliff-core/tests/integration_test.rs111 pattern: Regex::new("John Doe").ok(),CODE
LOWgit-cliff-core/tests/integration_test.rs149 name: Some("John Doe".to_string()),CODE
LOWgit-cliff-core/src/commit.rs779 name: Some("John Doe".to_string()),CODE
LOWgit-cliff-core/src/commit.rs841 name: Some("John Doe".to_string()),CODE
LOWgit-cliff-core/src/commit.rs878 pattern: Regex::new("John Doe").ok(),CODE
LOWgit-cliff-core/src/commit.rs1017 name: Some("John Doe".to_string()),CODE
LOWgit-cliff-core/src/statistics.rs157 name: Some(String::from("John Doe")),CODE
LOWgit-cliff-core/src/statistics.rs167 name: Some(String::from("John Doe")),CODE
LOWgit-cliff-core/src/statistics.rs177 name: Some(String::from("John Doe")),CODE
LOWgit-cliff-core/src/statistics.rs187 name: Some(String::from("John Doe")),CODE
LOWgit-cliff-core/src/statistics.rs199 name: Some(String::from("John Doe")),CODE
LOWgit-cliff-core/src/statistics.rs209 name: Some(String::from("John Doe")),CODE
LOWgit-cliff-core/src/statistics.rs219 name: Some(String::from("John Doe")),CODE
LOWgit-cliff-core/src/statistics.rs264 name: Some(String::from("John Doe")),CODE
LOWwebsite/docs/configuration/git.md236- `{ field = "author.name", pattern = "John Doe", group = "John's stuff" }`CODE
LOWwebsite/docs/configuration/git.md237 - If the author's name attribute of the commit matches the pattern "John Doe" (as a regex), override the scope with "JCODE
Structural Annotation Overuse1 hit · 2 pts
SeverityFileLineSnippetContext
LOW.github/workflows/test-fixtures.yml153 # NOTE: The following four include-path tests all use identicalCOMMENT