AI Slop Code Risk Monitor

liquibase/liquibase

SlopCodeMonitor badge for liquibase/liquibase Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Main Liquibase Source

1.6 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for liquibase/liquibase, a Java project with 5,639 GitHub stars. SynthScan examined 247,847 lines of code across 2857 source files, recording 262 pattern matches distributed across 8 syntactic categories. The legacy adjusted pattern signal is 1.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.

1.6
Adjusted Signal
1.6
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
5.6K
Stars
Java
Language
247.8K
Lines of Code
2.9K
Files
262
Pattern Hits
2026-10-31
Scan Date
0.00
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 5.4/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 1.2/100 · LOW

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

Agent Over-Engineering Ratio 0.9/100 · LOW

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

PR Review Velocity Impact 7.1/100 · LOW

Which changes need focused human review? 262 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 6HIGH 0MEDIUM 25LOW 231

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 262 distinct pattern matches across 8 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 Block213 hits · 213 pts
SeverityFileLineSnippetContext
LOWdocker/.grype.yaml1# Grype ignore rules for the community Docker images.COMMENT
LOWdocker/.grype.yaml21 # package. The tracker returns an empty state for it.COMMENT
LOW.github/dependabot.yml1version: 2COMMENT
LOW.github/util/check-release-gate.sh1#!/usr/bin/env bashCOMMENT
LOW.github/workflows/release-notes-aggregate.yml1name: "Release notes: aggregate from Jira"COMMENT
LOW.github/workflows/codeql.yml1# For most projects, this workflow file will not need changing; you simply needCOMMENT
LOW.github/workflows/trivy-scan-published-images.yml1# Vulnerability scanning for published Docker imagesCOMMENT
LOW.github/workflows/cleanup-packages.yml1name: Cleanup PackagesCOMMENT
LOW.github/workflows/cleanup-packages.yml141 [ -z "$id" ] && continueCOMMENT
LOW.github/workflows/auto-create-jira-on-merge.yml1name: "Auto-create Jira ticket on Community PR merge"COMMENT
LOW.github/workflows/auto-create-jira-on-merge.yml21# TECHOPS-1307: trigger 1 used to be `pull_request: closed`, and that neverCOMMENT
LOW.github/workflows/auto-create-jira-on-merge.yml41# - dependencies label appliedCOMMENT
LOW.github/workflows/auto-create-jira-on-merge.yml381 async function handlePush() {COMMENT
LOW.github/workflows/release-deploy-maven.yml161 sed -i -e "s/<version>\(release\|main\)-SNAPSHOT<\/version>/<version>${version}<\/version>/" pom.xmlCOMMENT
LOW.github/workflows/create-release.yml101COMMENT
LOW.github/workflows/create-release.yml121 # keep only the newest run per workflow, and require all finished and none failing.COMMENT
LOW.github/workflows/create-release.yml181 # [TECHOPS-1223] Same expression release-deploy-maven.yml uses, but keyed on dry_runCOMMENT
LOW.github/workflows/create-release.yml621COMMENT
LOW.github/workflows/main.yml1name: MainCOMMENT
LOW.github/workflows/main.yml181 # than packages, and liquibase-pro renames locally with `versions:set` instead ofCOMMENT
LOW…est/java/org/liquibase/maven/MavenIntegrationTest.java21 }COMMENT
LOW…est/java/org/liquibase/maven/MavenIntegrationTest.java41// verifier.verifyErrorFreeLog();COMMENT
LOW…se/maven/plugins/LiquibaseUpdateMojoExecutionTest.java21// File pom = getTestFile("src/test/resources/update/relativeClobFiles/plugin_config.xml");COMMENT
LOW…se/maven/plugins/LiquibaseUpdateMojoExecutionTest.java41// Optional<String> overridden = getChangeLogParameter(params, "overridden");COMMENT
LOW…g/liquibase/maven/plugins/LiquibaseUpdateMojoTest.java41 DIRECTORY_PROPERTIES.put("outputFileEncoding", StandardCharsets.UTF_8.name());COMMENT
LOW…g/liquibase/maven/plugins/LiquibaseUpdateMojoTest.java61//COMMENT
LOW…g/liquibase/maven/plugins/LiquibaseUpdateMojoTest.java81// props.setProperty("url", "properties_url_value");COMMENT
LOW…g/liquibase/maven/plugins/LiquibaseUpdateMojoTest.java101// testCommonOverrideAllButDriverWithPropertiesFile(DIRECTORY_CONFIG_FILE, DIRECTORY_PROPERTIES);COMMENT
LOW…g/liquibase/maven/plugins/LiquibaseUpdateMojoTest.java121//COMMENT
LOW…g/liquibase/maven/plugins/LiquibaseUpdateMojoTest.java141// props.setProperty("username", "properties_user_value");COMMENT
LOW…g/liquibase/maven/plugins/LiquibaseUpdateMojoTest.java161// /*-------------------------------------------------------------------------*\COMMENT
LOWliquibase-maven-plugin/src/test/groovy/README.txt1# The reason this file exists is that SONAR expects either BOTH src/test/java AND src/test/groovy to exist, or NONECOMMENT
LOW…/java/liquibase/database/AbstractJdbcDatabaseTest.java41COMMENT
LOW…/java/liquibase/database/AbstractJdbcDatabaseTest.java81// protected DatabaseConnection getMockConnection() throws Exception {COMMENT
LOW…st/java/liquibase/database/core/MSSQLDatabaseTest.java101// @TestCOMMENT
LOW…st/java/liquibase/database/core/MSSQLDatabaseTest.java121// dbSpy.setDefaultSchemaName(null);COMMENT
LOW…/test/java/liquibase/database/core/H2DatabaseTest.java61// DatabaseConnection mockedConnection = mock(DatabaseConnection.class);COMMENT
LOW…/test/java/liquibase/database/core/H2DatabaseTest.java81// when(mockedConnection.getDatabaseMajorVersion()).thenReturn(1);COMMENT
LOW…/test/java/liquibase/database/core/H2DatabaseTest.java101// when(mockedConnection.getDatabaseMinorVersion()).thenReturn(3);COMMENT
LOW…/test/java/liquibase/database/core/H2DatabaseTest.java121// when(mockedConnection.getDatabaseProductVersion()).thenReturn("1.4.100 (2014-08-18)");COMMENT
LOW…/test/java/liquibase/database/core/H2DatabaseTest.java141//COMMENT
LOW…/test/java/liquibase/change/AbstractSQLChangeTest.java141// }COMMENT
LOW…/test/java/liquibase/change/AbstractSQLChangeTest.java181// public void generateStatements_keepComments() {COMMENT
LOW…/test/java/liquibase/change/AbstractSQLChangeTest.java201// assertEquals("LINE 1;\n\nLINE 2;\nLINE 3;", ((RawParameterizedSqlStatement) statements[0]).getSql());COMMENT
LOW…/test/java/liquibase/change/AbstractSQLChangeTest.java301// when(database.getConnection()).thenReturn(connection);COMMENT
LOW…/serializer/core/yaml/YamlChangeLogSerializerTest.java21 String out = new YamlChangeLogSerializer().serialize(changeSet, false);COMMENT
LOW…ibase/changelog/UnknownChangeLogFormatLoggingTest.java21// @BeforeCOMMENT
LOW…ibase/changelog/UnknownChangeLogFormatLoggingTest.java41//COMMENT
LOW…a/liquibase/changelog/visitor/RollbackVisitorTest.java1package liquibase.changelog.visitor;COMMENT
LOW…a/liquibase/changelog/visitor/RollbackVisitorTest.java21// replay(database);COMMENT
LOW…uibase/changelog/visitor/ChangeLogSyncVisitorTest.java21// ChangeLogSyncVisitor visitor = new ChangeLogSyncVisitor(mockDatabase);COMMENT
LOW…ava/liquibase/changelog/visitor/UpdateVisitorTest.java1package liquibase.changelog.visitor;COMMENT
LOW…ava/liquibase/changelog/visitor/UpdateVisitorTest.java21// expectLastCall();COMMENT
LOW…se/changelog/filter/AlreadyRanChangeSetFilterTest.java1package liquibase.changelog.filter;COMMENT
LOW…se/changelog/filter/AlreadyRanChangeSetFilterTest.java21// //alwaysRunCOMMENT
LOW…se/changelog/filter/AlreadyRanChangeSetFilterTest.java41// AlreadyRanChangeSetFilter filter = new AlreadyRanChangeSetFilter(getRanChangeSets(), true);COMMENT
LOW…a/liquibase/verify/change/VerifyChangeClassesTest.java261COMMENT
LOW…tegration/commandline/ChangeExecListenerUtilsTest.java41// ChangeExecListenerWithProperties.class.getName(),COMMENT
LOW…tegration/commandline/ChangeExecListenerUtilsTest.java61// ChangeExecListenerNoPropertiesOrDatabase.class.getName(), null);COMMENT
LOW…tegration/commandline/ChangeExecListenerUtilsTest.java81//COMMENT
153 more matches not shown…
Hallucination Indicators6 hits · 60 pts
SeverityFileLineSnippetContext
CRITICAL…egration/ant/type/DatabaseTypeCredentialClearTest.java56 org.apache.tools.ant.types.Reference ref = new org.apache.tools.ant.types.Reference(project, "mydb");CODE
CRITICAL…egration/ant/type/DatabaseTypeCredentialClearTest.java146 new org.apache.tools.ant.types.Reference(project, "no-such-ref");CODE
CRITICAL…egration/ant/type/DatabaseTypeCredentialClearTest.java222 org.apache.tools.ant.taskdefs.Property credentialProp = new org.apache.tools.ant.taskdefs.Property();CODE
CRITICAL…egration/ant/type/DatabaseTypeCredentialClearTest.java228 org.apache.tools.ant.taskdefs.Property nonCredentialProp = new org.apache.tools.ant.taskdefs.Property();CODE
CRITICAL…egration/ant/type/DatabaseTypeCredentialClearTest.java311 org.apache.tools.ant.types.Reference ref = new org.apache.tools.ant.types.Reference(project, "mydb");CODE
CRITICAL…egration/ant/type/DatabaseTypeCredentialClearTest.java321 org.apache.tools.ant.taskdefs.Property p = new org.apache.tools.ant.taskdefs.Property();CODE
Decorative Section Separators13 hits · 46 pts
SeverityFileLineSnippetContext
MEDIUM⚡.github/dependabot.yml2# =============================================================================COMMENT
MEDIUM⚡.github/dependabot.yml4# =============================================================================COMMENT
MEDIUM⚡.github/dependabot.yml12# =============================================================================COMMENT
MEDIUM⚡.github/dependabot.yml14 # =============================================================================COMMENT
MEDIUM⚡.github/dependabot.yml16 # =============================================================================COMMENT
MEDIUM.github/dependabot.yml39 # =============================================================================COMMENT
MEDIUM.github/dependabot.yml41 # =============================================================================COMMENT
MEDIUM.github/dependabot.yml116 # =============================================================================COMMENT
MEDIUM.github/dependabot.yml118 # =============================================================================COMMENT
MEDIUM.github/workflows/docker-release.yml72 # ── Step 1: Bump LIQUIBASE_VERSION ARG in Dockerfiles, commit to main ────────COMMENT
MEDIUM.github/workflows/docker-release.yml157 # ── Step 2a: Build community (ubuntu) image ───────────────────────────────────COMMENT
MEDIUM.github/workflows/docker-release.yml189 # ── Step 2b: Build Alpine image ───────────────────────────────────────────────COMMENT
MEDIUM.github/workflows/docker-release.yml221 # ── Step 3: Publish both images ───────────────────────────────────────────────COMMENT
AI Slop Vocabulary10 hits · 30 pts
SeverityFileLineSnippetContext
MEDIUM.github/workflows/snapshot-branch.yml5# liquibase-sdk-maven-plugin (liquibase-pro-tests, liquibase-test-harness)COMMENT
MEDIUM.github/workflows/snapshot-branch.yml97 # Full 40-char SHA: liquibase-test-harness resolves community builds byCOMMENT
MEDIUM.github/workflows/main.yml14# (`install-snapshot-cli`, used by liquibase-pro-tests and the test harness)COMMENT
MEDIUM.github/workflows/main.yml87 # Full 40-char SHA: liquibase-test-harness resolves community builds byCOMMENT
MEDIUM.github/workflows/main.yml145 # liquibase-sdk-maven-plugin contract (liquibase-pro-tests, liquibase-test-harness):COMMENT
MEDIUM.github/workflows/main.yml180 # from a nightly workflow, liquibase-test-harness resolves run artifacts ratherCOMMENT
MEDIUM.github/workflows/main.yml187 # feed dry-run-release.yml's scan of recent main.yml runs and liquibase-test-harness,COMMENT
MEDIUM…ore/helpers/AbstractDatabaseConnectionCommandStep.java154 // This the more robust (IMO) way of stripping parameters, but doesn't work for all path formats.COMMENT
MEDIUM…d/src/main/java/liquibase/analytics/AnonymousSeed.java44 // Only check for MAC addresses if machineId is null. Machine ID is more robust (and likely faster to calculate COMMENT
MEDIUM…d/src/main/java/liquibase/analytics/AnonymousSeed.java83 // If we only have a username, then we don't have robust enough seed data, so use a random ID.COMMENT
Structural Annotation Overuse11 hits · 16 pts
SeverityFileLineSnippetContext
LOWISSUE_TRIAGE.md17### Step 1: Does the issue have an attached pull request?COMMENT
LOWISSUE_TRIAGE.md23### Step 2: Does the issue have enough information?COMMENT
LOWISSUE_TRIAGE.md35### Step 3: Labeling the issue and going through Issue TriageCOMMENT
LOWISSUE_TRIAGE.md57### Step 3: Set a PriorityCOMMENT
LOWISSUE_TRIAGE.md72### Step 4: Additional labelsCOMMENT
LOWdocker/README.md113### Step 1: Understand License RequirementsCOMMENT
LOWdocker/README.md121### Step 2: Determine Which Edition You NeedCOMMENT
LOWdocker/README.md135### Step 3: Update Your Image ReferenceCOMMENT
LOWdocker/README.md149### Step 4: Update Driver InstallationCOMMENT
LOWdocker/README.md168### Step 5: Test in Non-Production FirstCOMMENT
LOWdocker/README.md180### Step 6: Complete Production MigrationCOMMENT
Redundant / Tautological Comments5 hits · 10 pts
SeverityFileLineSnippetContext
LOW⚡docker/docker-entrypoint.sh17 # Check if changelog directory exists (common mount point) and change to itCOMMENT
LOW⚡docker/docker-entrypoint.sh21 # Check if we should change directory based on relative paths being usedCOMMENT
LOW⚡docker/docker-entrypoint.sh26 # Check if the changelog directory appears to be a mount point (has files or is writable)COMMENT
LOW⚡docker/docker-entrypoint.sh31 # Check if any arguments contain relative paths (not starting with / or containing :/ for URLs)COMMENT
LOWdocker/docker-entrypoint.sh78 # Check if user already provided a search pathCOMMENT
Self-Referential Comments2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUM…xtension-testing/src/main/resources/liquibase.sdk.yaml2## This file defines the default settings to connect to test systems understood by Liquibase core.COMMENT
MEDIUM.github/workflows/release-deploy-maven.yml203 # Create the bundle zip fileCOMMENT
Fake / Example Data2 hits · 2 pts
SeverityFileLineSnippetContext
LOW…n-tests/src/test/resources/changelogs/common/lorem.txt1Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut sagittis feugiat velit tempus sollicitudin. Ut dapibus, tellCODE
LOW…n-tests/src/test/resources/changelogs/common/lorem.txt1Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut sagittis feugiat velit tempus sollicitudin. Ut dapibus, tellCODE