AI Slop Code Risk Monitor

orhun/git-cliff

SlopCodeMonitor badge for orhun/git-cliff Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

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

3.6 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for orhun/git-cliff, a Rust project with 12,353 GitHub stars. SynthScan examined 33,036 lines of code across 189 source files, recording 78 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 3.6 (Low pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

3.6
Adjusted Signal
3.6
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
12.4K
Stars
Rust
Language
33.0K
Lines of Code
189
Files
78
Pattern Hits
2026-10-31
Scan Date
0.05
HC Hit Rate

Risk Review · Payload v1

Use each vector to guide manual verification of the underlying findings.

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 7.8/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 53 finding(s).

Hallucinated Dependency & Supply Chain Risk 2.9/100 · LOW

Are imports declared and package/API names verified? 16 finding(s).

Agent Over-Engineering Ratio 6.6/100 · LOW

Are wrappers, guards, and repeated structures necessary? 9 finding(s).

PR Review Velocity Impact 17.0/100 · LOW

Which changes need focused human review? 78 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 9MEDIUM 0LOW 69

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 78 distinct pattern matches across 4 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. 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 configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Over-Commented Block52 hits · 52 pts
SeverityFileLineSnippetContext
LOWcliff.toml81[git]COMMENT
LOWcliff.toml121protect_breaking_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 #[cfg(feature = "repo")]COMMENT
LOWgit-cliff-core/src/error.rs41 /// Error that may occur while grouping commits.COMMENT
LOWgit-cliff-core/src/error.rs61 ArgumentError(String),COMMENT
LOWgit-cliff-core/src/error.rs81 /// value matchers.COMMENT
LOWgit-cliff-core/src/error.rs101 HttpHeaderError(#[from] reqwest::header::InvalidHeaderValue),COMMENT
LOWgit-cliff-core/src/config.rs121 ///COMMENT
LOWgit-cliff-core/src/config.rs141 pub commit_parsers: Vec<CommitParser>,COMMENT
LOWgit-cliff-core/src/config.rs161 /// Regex to count matched tags.COMMENT
LOWgit-cliff-core/src/config.rs181 /// Exclude unrelated commits with changes at the specified paths.COMMENT
LOWgit-cliff-core/src/config.rs241 /// GitHub remote.COMMENT
LOWgit-cliff-core/src/config.rs401 /// Configures automatic minor version increments for feature changes.COMMENT
LOWgit-cliff-core/src/config.rs421 ///COMMENT
LOWgit-cliff-core/src/config.rs441 pub custom_minor_increment_regex: Option<String>,COMMENT
LOWgit-cliff-core/src/config.rs481 #[serde(with = "serde_regex", default)]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 repo;COMMENT
LOWgit-cliff-core/src/embed.rs1use std::path::{Component, Path};COMMENT
LOWgit-cliff-core/src/statistics.rs21 pub count: usize,COMMENT
LOWgit-cliff-core/src/markdown.rs1//! Markdown post-processing for the generated changelog.COMMENT
LOWgit-cliff-core/src/template.rs61 /// Behaves like Tera's built-in `group_by(attribute="group")` filter, butCOMMENT
LOWgit-cliff-core/src/contributor.rs1use std::hash::{Hash, Hasher};COMMENT
LOWgit-cliff-core/src/changelog.rs241 } else if release_index == self.releases.len() - 1 {COMMENT
LOWgit-cliff-core/src/changelog.rs341 tracing::debug!("Number of GitLab commits: {}", commits.len());COMMENT
LOWgit-cliff-core/src/changelog.rs441 /// Returns the Azure DevOps metadata needed for the changelog.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 a commit or a pull request.COMMENT
LOWgit-cliff-core/src/remote/github.rs61/// Label of the pull request.COMMENT
LOWconfig/cliff.toml41# See https://www.conventionalcommits.orgCOMMENT
LOWwebsite/blog/git-cliff-2.2.0.md41#COMMENT
LOWexamples/github.toml1# git-cliff ~ configuration fileCOMMENT
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
LOW.github/workflows/test-fixtures.yml161 previous-release-timestamp: "2022-04-06 01:25:12"COMMENT
LOWgit-cliff/src/config_path.rs1//! Resolution of the configuration file path.COMMENT
LOWgit-cliff/src/lib.rs321COMMENT
LOWgit-cliff/src/lib.rs581 .rfind(|release| !release.commits.is_empty())COMMENT
LOWgit-cliff/src/lib.rs601/// Ok(())COMMENT
LOWgit-cliff/src/lib.rs621/// let args = Opt::parse();COMMENT
LOWgit-cliff/src/args.rs161 // `value_delimiter` here: a commit message legitimately contains spacesCOMMENT
LOWgit-cliff/src/args.rs241 value_name = "TEMPLATE",COMMENT
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.rs118 pattern: Regex::new("John Doe").ok(),CODE
LOWgit-cliff-core/tests/integration_test.rs157 name: Some("John Doe".to_string()),CODE
LOWgit-cliff-core/src/commit.rs840 name: Some("John Doe".to_string()),CODE
LOWgit-cliff-core/src/commit.rs904 name: Some("John Doe".to_string()),CODE
LOWgit-cliff-core/src/commit.rs943 pattern: Regex::new("John Doe").ok(),CODE
LOWgit-cliff-core/src/commit.rs1545 name: Some("John Doe".to_string()),CODE
LOW⚡git-cliff-core/src/statistics.rs160 name: Some(String::from("John Doe")),CODE
LOW⚡git-cliff-core/src/statistics.rs170 name: Some(String::from("John Doe")),CODE
LOW⚡git-cliff-core/src/statistics.rs180 name: Some(String::from("John Doe")),CODE
LOW⚡git-cliff-core/src/statistics.rs190 name: Some(String::from("John Doe")),CODE
LOW⚡git-cliff-core/src/statistics.rs202 name: Some(String::from("John Doe")),CODE
LOW⚡git-cliff-core/src/statistics.rs212 name: Some(String::from("John Doe")),CODE
LOW⚡git-cliff-core/src/statistics.rs222 name: Some(String::from("John Doe")),CODE
LOWgit-cliff-core/src/statistics.rs267 name: Some(String::from("John Doe")),CODE
LOWwebsite/docs/configuration/git.md291- `{ field = "author.name", pattern = "John Doe", group = "John's stuff" }`CODE
LOWwebsite/docs/configuration/git.md292 - 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.yml176 # NOTE: The following four include-path tests all use identicalCOMMENT