A highly customizable Changelog Generator that follows Conventional Commit specifications ⛰️
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).
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.
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 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.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | cliff.toml | 81 | # See https://www.conventionalcommits.org | COMMENT |
| LOW | cliff.toml | 121 | filter_commits = false | COMMENT |
| LOW | git-cliff-core/Cargo.toml | 41 | ## Enable integration with Gitea. | COMMENT |
| LOW | git-cliff-core/src/commit.rs | 21 | #[derive(Debug, Clone, Eq, PartialEq, Deserialize, Serialize)] | COMMENT |
| LOW | git-cliff-core/src/commit.rs | 121 | #[serde(skip_deserializing)] | COMMENT |
| LOW | git-cliff-core/src/commit.rs | 141 | /// Arbitrary data to be used with the `--from-context` CLI option. | COMMENT |
| LOW | git-cliff-core/src/error.rs | 1 | use thiserror::Error as ThisError; | COMMENT |
| LOW | git-cliff-core/src/error.rs | 21 | {0:?} is not a valid commit range. Did you provide the correct arguments?" | COMMENT |
| LOW | git-cliff-core/src/error.rs | 41 | /// Error that may occur while generating changelog. | COMMENT |
| LOW | git-cliff-core/src/error.rs | 61 | EmbeddedError(String), | COMMENT |
| LOW | git-cliff-core/src/error.rs | 81 | /// Error that may occur while parsing a `SemVer` version or version | COMMENT |
| LOW | git-cliff-core/src/error.rs | 101 | UrlParseError(#[from] url::ParseError), | COMMENT |
| LOW | git-cliff-core/src/config.rs | 81 | /// Output file path. | COMMENT |
| LOW | git-cliff-core/src/config.rs | 101 | pub filter_unconventional: bool, | COMMENT |
| LOW | git-cliff-core/src/config.rs | 121 | /// Regex to select git tags that represent releases. | COMMENT |
| LOW | git-cliff-core/src/config.rs | 141 | /// Limit the total number of commits included in the changelog. | COMMENT |
| LOW | git-cliff-core/src/config.rs | 201 | COMMENT | |
| LOW | git-cliff-core/src/config.rs | 341 | /// Version bump type. | COMMENT |
| LOW | git-cliff-core/src/config.rs | 361 | /// - A patch version update if the major version is 0. | COMMENT |
| LOW | git-cliff-core/src/config.rs | 381 | /// | COMMENT |
| LOW | git-cliff-core/src/config.rs | 441 | /// Group of the commit. | COMMENT |
| LOW | git-cliff-core/src/release.rs | 21 | pub struct Release<'a> { | COMMENT |
| LOW | git-cliff-core/src/release.rs | 41 | /// Submodule commits. | COMMENT |
| LOW | git-cliff-core/src/lib.rs | 1 | //! A highly customizable changelog generator ⛰️ | COMMENT |
| LOW | git-cliff-core/src/lib.rs | 21 | /// Config file parser. | COMMENT |
| LOW | git-cliff-core/src/lib.rs | 41 | pub mod statistics; | COMMENT |
| LOW | git-cliff-core/src/statistics.rs | 21 | /// Aggregated statistics about commits in the release. | COMMENT |
| LOW | git-cliff-core/src/repo.rs | 101 | } | COMMENT |
| LOW | git-cliff-core/src/template.rs | 61 | /// Behaves like Tera's built-in `group_by(attribute="group")` filter, but | COMMENT |
| LOW | git-cliff-core/src/changelog.rs | 201 | self.releases[release_index].previous = | COMMENT |
| LOW | git-cliff-core/src/changelog.rs | 361 | /// - Commits | COMMENT |
| LOW | git-cliff-core/src/changelog.rs | 401 | } | COMMENT |
| LOW | git-cliff-core/src/remote/azure_devops.rs | 61 | #[derive(Default, Debug, Clone, PartialEq, Serialize, Deserialize)] | COMMENT |
| LOW | git-cliff-core/src/remote/gitlab.rs | 21 | /// Optional Description of project | COMMENT |
| LOW | git-cliff-core/src/remote/bitbucket.rs | 41 | /// Bitbucket Pagination Header | COMMENT |
| LOW | git-cliff-core/src/remote/bitbucket.rs | 61 | /// Author of the commit. | COMMENT |
| LOW | config/cliff.toml | 21 | {% endfor %} | COMMENT |
| LOW | config/cliff.toml | 41 | # Exclude commits that do not match the conventional commits specification. | COMMENT |
| LOW | website/blog/git-cliff-2.2.0.md | 41 | # | COMMENT |
| LOW | examples/github.toml | 61 | # An array of regex based postprocessors to modify the changelog. | COMMENT |
| LOW | examples/azure-devops-keepachangelog.toml | 1 | # git-cliff ~ configuration file | COMMENT |
| LOW | .github/workflows/codeql.yml | 1 | # For most projects, this workflow file will not need changing; you simply need | COMMENT |
| LOW | git-cliff/src/lib.rs | 501 | /// fn main() -> Result<()> { | COMMENT |
| LOW | git-cliff/src/lib.rs | 521 | /// use git_cliff_core::error::Result; | COMMENT |
| LOW | git-cliff/src/args.rs | 221 | allow_hyphen_values = true | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| HIGH | examples/scoped.toml | 0 | # changelog\n all notable changes to this project will be documented in this file.\n | STRING |
| HIGH | examples/scopesorted.toml | 0 | # changelog\n all notable changes to this project will be documented in this file.\n | STRING |
| HIGH | examples/detailed.toml | 0 | # changelog\n all notable changes to this project will be documented in this file.\n | STRING |
| HIGH | examples/unconventional.toml | 0 | # changelog\n all notable changes to this project will be documented in this file.\n | STRING |
| HIGH | examples/statistics.toml | 0 | # changelog\n all notable changes to this project will be documented in this file.\n | STRING |
| HIGH | examples/gitlab-keepachangelog.toml | 0 | # changelog\n all notable changes to this project will be documented in this file. the format is based on [keep a change | STRING |
| HIGH | examples/keepachangelog.toml | 0 | # changelog\n all notable changes to this project will be documented in this file. the format is based on [keep a change | STRING |
| HIGH | examples/azure-devops-keepachangelog.toml | 0 | # changelog\n all notable changes to this project will be documented in this file. the format is based on [keep a change | STRING |
| HIGH | examples/github-keepachangelog.toml | 0 | # changelog\n all notable changes to this project will be documented in this file. the format is based on [keep a change | STRING |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | git-cliff-core/tests/integration_test.rs | 111 | pattern: Regex::new("John Doe").ok(), | CODE |
| LOW | git-cliff-core/tests/integration_test.rs | 149 | name: Some("John Doe".to_string()), | CODE |
| LOW | git-cliff-core/src/commit.rs | 779 | name: Some("John Doe".to_string()), | CODE |
| LOW | git-cliff-core/src/commit.rs | 841 | name: Some("John Doe".to_string()), | CODE |
| LOW | git-cliff-core/src/commit.rs | 878 | pattern: Regex::new("John Doe").ok(), | CODE |
| LOW | git-cliff-core/src/commit.rs | 1017 | name: Some("John Doe".to_string()), | CODE |
| LOW⚡ | git-cliff-core/src/statistics.rs | 157 | name: Some(String::from("John Doe")), | CODE |
| LOW⚡ | git-cliff-core/src/statistics.rs | 167 | name: Some(String::from("John Doe")), | CODE |
| LOW⚡ | git-cliff-core/src/statistics.rs | 177 | name: Some(String::from("John Doe")), | CODE |
| LOW⚡ | git-cliff-core/src/statistics.rs | 187 | name: Some(String::from("John Doe")), | CODE |
| LOW⚡ | git-cliff-core/src/statistics.rs | 199 | name: Some(String::from("John Doe")), | CODE |
| LOW⚡ | git-cliff-core/src/statistics.rs | 209 | name: Some(String::from("John Doe")), | CODE |
| LOW⚡ | git-cliff-core/src/statistics.rs | 219 | name: Some(String::from("John Doe")), | CODE |
| LOW | git-cliff-core/src/statistics.rs | 264 | name: Some(String::from("John Doe")), | CODE |
| LOW | website/docs/configuration/git.md | 236 | - `{ field = "author.name", pattern = "John Doe", group = "John's stuff" }` | CODE |
| LOW | website/docs/configuration/git.md | 237 | - If the author's name attribute of the commit matches the pattern "John Doe" (as a regex), override the scope with "J | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | .github/workflows/test-fixtures.yml | 153 | # NOTE: The following four include-path tests all use identical | COMMENT |