AI Slop Code RIsk Monitor

olivierlacan/keep-a-changelog

If you build software, keep a changelog.

5.7 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for olivierlacan/keep-a-changelog, a Haml project with 6,730 GitHub stars. SynthScan examined 11,756 lines of code across 56 source files, recording 38 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 5.7 (Moderate 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.

5.7
Adjusted Signal
5.7
Raw Pattern Score
100%
Time Factor
2026-09-07
Last Push
6.7K
Stars
Haml
Language
11.8K
Lines of Code
56
Files
38
Pattern Hits
2026-10-12
Scan Date
0.00
HC Hit Rate

Risk Review · v3

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

Cognitive Ownership Risk 16.5/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

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

Agent Over-Engineering Ratio 11.2/100 · LOW

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

PR Review Velocity Impact 24.5/100 · LOW

Which changes need focused human review? 38 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 0MEDIUM 14LOW 24

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 38 distinct pattern matches across 6 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.

Decorative Section Separators8 hits · 24 pts
SeverityFileLineSnippetContext
MEDIUMconfig.rb1# --------------------------------------COMMENT
MEDIUMconfig.rb3# --------------------------------------COMMENT
MEDIUMconfig.rb270# --------------------------------------COMMENT
MEDIUMconfig.rb272# --------------------------------------COMMENT
MEDIUMconfig.rb394# --------------------------------------COMMENT
MEDIUMconfig.rb396# --------------------------------------COMMENT
MEDIUMconfig.rb412# --------------------------------------COMMENT
MEDIUMconfig.rb414# --------------------------------------COMMENT
Over-Commented Block19 hits · 19 pts
SeverityFileLineSnippetContext
LOWconfig.rb1# --------------------------------------COMMENT
LOWconfig.rb21# Last version should be the latest English version since Keep a Changelog isCOMMENT
LOWconfig.rb201# selectors offer *every* version for *every* language (issue #719): pick one weCOMMENT
LOWtranslation_coverage.rb21 # `new` / `updated` CSS markers in the English LATEST_VERSION file describe howCOMMENT
LOWtools/setup.sh1#!/usr/bin/env bashCOMMENT
LOWtools/changelog_pin.rb1# frozen_string_literal: trueCOMMENT
LOWtools/changelog_pin.rb21# taught) but is emptied — its contents describe work newer than the trackCOMMENT
LOWtools/requirements.txt1# Dependencies for the LaBSE translation-QA triage (tools/labse_triage.py).COMMENT
LOWtools/changelog_release.rb1#!/usr/bin/env rubyCOMMENT
LOWtools/version_routing.rb1# frozen_string_literal: trueCOMMENT
LOWtools/version_routing.rb41 .max_by { |v| Gem::Version.new(v) }COMMENT
LOWtools/prose_lint.rb1# frozen_string_literal: trueCOMMENT
LOWtest/changelog_pin_test.rb1require "minitest/autorun"COMMENT
LOWtest/visual/responsive.spec.js1const { test, expect } = require("@playwright/test");COMMENT
LOWtest/visual/routing.spec.js1const { test, expect } = require("@playwright/test");COMMENT
LOW.github/workflows/release.yml1name: Release from changelogCOMMENT
LOW.github/workflows/deploy.yml1name: Deploy site (manual)COMMENT
LOW.github/workflows/ci.yml1name: CI checksCOMMENT
LOWdata/interstitial.yml1# Localized copy for the "translation missing" interstitial (source/missing.html.haml).COMMENT
Self-Referential Comments4 hits · 12 pts
SeverityFileLineSnippetContext
MEDIUMtools/changelog_release.rb7# This file is both a library (require it and the classes below are testable inCOMMENT
MEDIUMtools/changelog_release.rb11# Create a release for every dated version that doesn't have one yet.COMMENT
MEDIUMtools/changelog_release.rb228 # Create an annotated tag at +sha+, dated to the changelog entry so the tagCOMMENT
MEDIUMtools/changelog_release.rb279 # Create a release for every dated version that doesn't have one yet, oldestCOMMENT
Modern AI Meta-Vocabulary2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMtools/changelog_release.rb26# the orchestration can be tested against a fake without touching the network.COMMENT
MEDIUMtest/changelog_release_test.rb6# and simulates release/tag state in memory, so the orchestration in Runner canCOMMENT
Hyper-Verbose Identifiers4 hits · 4 pts
SeverityFileLineSnippetContext
LOWtranslation_coverage.rb214 def extract_markdown_anchor_sections(content)CODE
LOWtranslation_coverage.rb343 def extract_markdown_section_texts(file_path)CODE
LOWtranslation_coverage.rb379 def normalize_markdown_fragment(line)CODE
LOWtranslation_coverage.rb897 def markdown_section_link_counts(path)CODE
Redundant / Tautological Comments1 hit · 2 pts
SeverityFileLineSnippetContext
LOWtranslation_coverage.rb114 # Check if this version uses markdown (0.3.0) - sections won't have explicit IDsCOMMENT