Main Liquibase Source
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.
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.
Can maintainers explain intent, assumptions, and trade-offs? 241 finding(s).
Are imports declared and package/API names verified? 8 finding(s).
Are wrappers, guards, and repeated structures necessary? 13 finding(s).
Which changes need focused human review? 262 finding(s).
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.
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.
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.
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.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | docker/.grype.yaml | 1 | # Grype ignore rules for the community Docker images. | COMMENT |
| LOW | docker/.grype.yaml | 21 | # package. The tracker returns an empty state for it. | COMMENT |
| LOW | .github/dependabot.yml | 1 | version: 2 | COMMENT |
| LOW | .github/util/check-release-gate.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | .github/workflows/release-notes-aggregate.yml | 1 | name: "Release notes: aggregate from Jira" | COMMENT |
| LOW | .github/workflows/codeql.yml | 1 | # For most projects, this workflow file will not need changing; you simply need | COMMENT |
| LOW | .github/workflows/trivy-scan-published-images.yml | 1 | # Vulnerability scanning for published Docker images | COMMENT |
| LOW | .github/workflows/cleanup-packages.yml | 1 | name: Cleanup Packages | COMMENT |
| LOW | .github/workflows/cleanup-packages.yml | 141 | [ -z "$id" ] && continue | COMMENT |
| LOW | .github/workflows/auto-create-jira-on-merge.yml | 1 | name: "Auto-create Jira ticket on Community PR merge" | COMMENT |
| LOW | .github/workflows/auto-create-jira-on-merge.yml | 21 | # TECHOPS-1307: trigger 1 used to be `pull_request: closed`, and that never | COMMENT |
| LOW | .github/workflows/auto-create-jira-on-merge.yml | 41 | # - dependencies label applied | COMMENT |
| LOW | .github/workflows/auto-create-jira-on-merge.yml | 381 | async function handlePush() { | COMMENT |
| LOW | .github/workflows/release-deploy-maven.yml | 161 | sed -i -e "s/<version>\(release\|main\)-SNAPSHOT<\/version>/<version>${version}<\/version>/" pom.xml | COMMENT |
| LOW | .github/workflows/create-release.yml | 101 | COMMENT | |
| LOW | .github/workflows/create-release.yml | 121 | # keep only the newest run per workflow, and require all finished and none failing. | COMMENT |
| LOW | .github/workflows/create-release.yml | 181 | # [TECHOPS-1223] Same expression release-deploy-maven.yml uses, but keyed on dry_run | COMMENT |
| LOW | .github/workflows/create-release.yml | 621 | COMMENT | |
| LOW | .github/workflows/main.yml | 1 | name: Main | COMMENT |
| LOW | .github/workflows/main.yml | 181 | # than packages, and liquibase-pro renames locally with `versions:set` instead of | COMMENT |
| LOW | …est/java/org/liquibase/maven/MavenIntegrationTest.java | 21 | } | COMMENT |
| LOW | …est/java/org/liquibase/maven/MavenIntegrationTest.java | 41 | // verifier.verifyErrorFreeLog(); | COMMENT |
| LOW | …se/maven/plugins/LiquibaseUpdateMojoExecutionTest.java | 21 | // File pom = getTestFile("src/test/resources/update/relativeClobFiles/plugin_config.xml"); | COMMENT |
| LOW | …se/maven/plugins/LiquibaseUpdateMojoExecutionTest.java | 41 | // Optional<String> overridden = getChangeLogParameter(params, "overridden"); | COMMENT |
| LOW | …g/liquibase/maven/plugins/LiquibaseUpdateMojoTest.java | 41 | DIRECTORY_PROPERTIES.put("outputFileEncoding", StandardCharsets.UTF_8.name()); | COMMENT |
| LOW | …g/liquibase/maven/plugins/LiquibaseUpdateMojoTest.java | 61 | // | COMMENT |
| LOW | …g/liquibase/maven/plugins/LiquibaseUpdateMojoTest.java | 81 | // props.setProperty("url", "properties_url_value"); | COMMENT |
| LOW | …g/liquibase/maven/plugins/LiquibaseUpdateMojoTest.java | 101 | // testCommonOverrideAllButDriverWithPropertiesFile(DIRECTORY_CONFIG_FILE, DIRECTORY_PROPERTIES); | COMMENT |
| LOW | …g/liquibase/maven/plugins/LiquibaseUpdateMojoTest.java | 121 | // | COMMENT |
| LOW | …g/liquibase/maven/plugins/LiquibaseUpdateMojoTest.java | 141 | // props.setProperty("username", "properties_user_value"); | COMMENT |
| LOW | …g/liquibase/maven/plugins/LiquibaseUpdateMojoTest.java | 161 | // /*-------------------------------------------------------------------------*\ | COMMENT |
| LOW | liquibase-maven-plugin/src/test/groovy/README.txt | 1 | # The reason this file exists is that SONAR expects either BOTH src/test/java AND src/test/groovy to exist, or NONE | COMMENT |
| LOW | …/java/liquibase/database/AbstractJdbcDatabaseTest.java | 41 | COMMENT | |
| LOW | …/java/liquibase/database/AbstractJdbcDatabaseTest.java | 81 | // protected DatabaseConnection getMockConnection() throws Exception { | COMMENT |
| LOW | …st/java/liquibase/database/core/MSSQLDatabaseTest.java | 101 | // @Test | COMMENT |
| LOW | …st/java/liquibase/database/core/MSSQLDatabaseTest.java | 121 | // dbSpy.setDefaultSchemaName(null); | COMMENT |
| LOW | …/test/java/liquibase/database/core/H2DatabaseTest.java | 61 | // DatabaseConnection mockedConnection = mock(DatabaseConnection.class); | COMMENT |
| LOW | …/test/java/liquibase/database/core/H2DatabaseTest.java | 81 | // when(mockedConnection.getDatabaseMajorVersion()).thenReturn(1); | COMMENT |
| LOW | …/test/java/liquibase/database/core/H2DatabaseTest.java | 101 | // when(mockedConnection.getDatabaseMinorVersion()).thenReturn(3); | COMMENT |
| LOW | …/test/java/liquibase/database/core/H2DatabaseTest.java | 121 | // when(mockedConnection.getDatabaseProductVersion()).thenReturn("1.4.100 (2014-08-18)"); | COMMENT |
| LOW | …/test/java/liquibase/database/core/H2DatabaseTest.java | 141 | // | COMMENT |
| LOW | …/test/java/liquibase/change/AbstractSQLChangeTest.java | 141 | // } | COMMENT |
| LOW | …/test/java/liquibase/change/AbstractSQLChangeTest.java | 181 | // public void generateStatements_keepComments() { | COMMENT |
| LOW | …/test/java/liquibase/change/AbstractSQLChangeTest.java | 201 | // assertEquals("LINE 1;\n\nLINE 2;\nLINE 3;", ((RawParameterizedSqlStatement) statements[0]).getSql()); | COMMENT |
| LOW | …/test/java/liquibase/change/AbstractSQLChangeTest.java | 301 | // when(database.getConnection()).thenReturn(connection); | COMMENT |
| LOW | …/serializer/core/yaml/YamlChangeLogSerializerTest.java | 21 | String out = new YamlChangeLogSerializer().serialize(changeSet, false); | COMMENT |
| LOW | …ibase/changelog/UnknownChangeLogFormatLoggingTest.java | 21 | // @Before | COMMENT |
| LOW | …ibase/changelog/UnknownChangeLogFormatLoggingTest.java | 41 | // | COMMENT |
| LOW | …a/liquibase/changelog/visitor/RollbackVisitorTest.java | 1 | package liquibase.changelog.visitor; | COMMENT |
| LOW | …a/liquibase/changelog/visitor/RollbackVisitorTest.java | 21 | // replay(database); | COMMENT |
| LOW | …uibase/changelog/visitor/ChangeLogSyncVisitorTest.java | 21 | // ChangeLogSyncVisitor visitor = new ChangeLogSyncVisitor(mockDatabase); | COMMENT |
| LOW | …ava/liquibase/changelog/visitor/UpdateVisitorTest.java | 1 | package liquibase.changelog.visitor; | COMMENT |
| LOW | …ava/liquibase/changelog/visitor/UpdateVisitorTest.java | 21 | // expectLastCall(); | COMMENT |
| LOW | …se/changelog/filter/AlreadyRanChangeSetFilterTest.java | 1 | package liquibase.changelog.filter; | COMMENT |
| LOW | …se/changelog/filter/AlreadyRanChangeSetFilterTest.java | 21 | // //alwaysRun | COMMENT |
| LOW | …se/changelog/filter/AlreadyRanChangeSetFilterTest.java | 41 | // AlreadyRanChangeSetFilter filter = new AlreadyRanChangeSetFilter(getRanChangeSets(), true); | COMMENT |
| LOW | …a/liquibase/verify/change/VerifyChangeClassesTest.java | 261 | COMMENT | |
| LOW | …tegration/commandline/ChangeExecListenerUtilsTest.java | 41 | // ChangeExecListenerWithProperties.class.getName(), | COMMENT |
| LOW | …tegration/commandline/ChangeExecListenerUtilsTest.java | 61 | // ChangeExecListenerNoPropertiesOrDatabase.class.getName(), null); | COMMENT |
| LOW | …tegration/commandline/ChangeExecListenerUtilsTest.java | 81 | // | COMMENT |
| 153 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| CRITICAL | …egration/ant/type/DatabaseTypeCredentialClearTest.java | 56 | org.apache.tools.ant.types.Reference ref = new org.apache.tools.ant.types.Reference(project, "mydb"); | CODE |
| CRITICAL | …egration/ant/type/DatabaseTypeCredentialClearTest.java | 146 | new org.apache.tools.ant.types.Reference(project, "no-such-ref"); | CODE |
| CRITICAL | …egration/ant/type/DatabaseTypeCredentialClearTest.java | 222 | org.apache.tools.ant.taskdefs.Property credentialProp = new org.apache.tools.ant.taskdefs.Property(); | CODE |
| CRITICAL | …egration/ant/type/DatabaseTypeCredentialClearTest.java | 228 | org.apache.tools.ant.taskdefs.Property nonCredentialProp = new org.apache.tools.ant.taskdefs.Property(); | CODE |
| CRITICAL | …egration/ant/type/DatabaseTypeCredentialClearTest.java | 311 | org.apache.tools.ant.types.Reference ref = new org.apache.tools.ant.types.Reference(project, "mydb"); | CODE |
| CRITICAL | …egration/ant/type/DatabaseTypeCredentialClearTest.java | 321 | org.apache.tools.ant.taskdefs.Property p = new org.apache.tools.ant.taskdefs.Property(); | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM⚡ | .github/dependabot.yml | 2 | # ============================================================================= | COMMENT |
| MEDIUM⚡ | .github/dependabot.yml | 4 | # ============================================================================= | COMMENT |
| MEDIUM⚡ | .github/dependabot.yml | 12 | # ============================================================================= | COMMENT |
| MEDIUM⚡ | .github/dependabot.yml | 14 | # ============================================================================= | COMMENT |
| MEDIUM⚡ | .github/dependabot.yml | 16 | # ============================================================================= | COMMENT |
| MEDIUM | .github/dependabot.yml | 39 | # ============================================================================= | COMMENT |
| MEDIUM | .github/dependabot.yml | 41 | # ============================================================================= | COMMENT |
| MEDIUM | .github/dependabot.yml | 116 | # ============================================================================= | COMMENT |
| MEDIUM | .github/dependabot.yml | 118 | # ============================================================================= | COMMENT |
| MEDIUM | .github/workflows/docker-release.yml | 72 | # ── Step 1: Bump LIQUIBASE_VERSION ARG in Dockerfiles, commit to main ──────── | COMMENT |
| MEDIUM | .github/workflows/docker-release.yml | 157 | # ── Step 2a: Build community (ubuntu) image ─────────────────────────────────── | COMMENT |
| MEDIUM | .github/workflows/docker-release.yml | 189 | # ── Step 2b: Build Alpine image ─────────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/workflows/docker-release.yml | 221 | # ── Step 3: Publish both images ─────────────────────────────────────────────── | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | .github/workflows/snapshot-branch.yml | 5 | # liquibase-sdk-maven-plugin (liquibase-pro-tests, liquibase-test-harness) | COMMENT |
| MEDIUM | .github/workflows/snapshot-branch.yml | 97 | # Full 40-char SHA: liquibase-test-harness resolves community builds by | COMMENT |
| MEDIUM | .github/workflows/main.yml | 14 | # (`install-snapshot-cli`, used by liquibase-pro-tests and the test harness) | COMMENT |
| MEDIUM | .github/workflows/main.yml | 87 | # Full 40-char SHA: liquibase-test-harness resolves community builds by | COMMENT |
| MEDIUM | .github/workflows/main.yml | 145 | # liquibase-sdk-maven-plugin contract (liquibase-pro-tests, liquibase-test-harness): | COMMENT |
| MEDIUM | .github/workflows/main.yml | 180 | # from a nightly workflow, liquibase-test-harness resolves run artifacts rather | COMMENT |
| MEDIUM | .github/workflows/main.yml | 187 | # feed dry-run-release.yml's scan of recent main.yml runs and liquibase-test-harness, | COMMENT |
| MEDIUM | …ore/helpers/AbstractDatabaseConnectionCommandStep.java | 154 | // 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.java | 44 | // 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.java | 83 | // If we only have a username, then we don't have robust enough seed data, so use a random ID. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | ISSUE_TRIAGE.md | 17 | ### Step 1: Does the issue have an attached pull request? | COMMENT |
| LOW | ISSUE_TRIAGE.md | 23 | ### Step 2: Does the issue have enough information? | COMMENT |
| LOW | ISSUE_TRIAGE.md | 35 | ### Step 3: Labeling the issue and going through Issue Triage | COMMENT |
| LOW | ISSUE_TRIAGE.md | 57 | ### Step 3: Set a Priority | COMMENT |
| LOW | ISSUE_TRIAGE.md | 72 | ### Step 4: Additional labels | COMMENT |
| LOW | docker/README.md | 113 | ### Step 1: Understand License Requirements | COMMENT |
| LOW | docker/README.md | 121 | ### Step 2: Determine Which Edition You Need | COMMENT |
| LOW | docker/README.md | 135 | ### Step 3: Update Your Image Reference | COMMENT |
| LOW | docker/README.md | 149 | ### Step 4: Update Driver Installation | COMMENT |
| LOW | docker/README.md | 168 | ### Step 5: Test in Non-Production First | COMMENT |
| LOW | docker/README.md | 180 | ### Step 6: Complete Production Migration | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW⚡ | docker/docker-entrypoint.sh | 17 | # Check if changelog directory exists (common mount point) and change to it | COMMENT |
| LOW⚡ | docker/docker-entrypoint.sh | 21 | # Check if we should change directory based on relative paths being used | COMMENT |
| LOW⚡ | docker/docker-entrypoint.sh | 26 | # Check if the changelog directory appears to be a mount point (has files or is writable) | COMMENT |
| LOW⚡ | docker/docker-entrypoint.sh | 31 | # Check if any arguments contain relative paths (not starting with / or containing :/ for URLs) | COMMENT |
| LOW | docker/docker-entrypoint.sh | 78 | # Check if user already provided a search path | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | …xtension-testing/src/main/resources/liquibase.sdk.yaml | 2 | ## This file defines the default settings to connect to test systems understood by Liquibase core. | COMMENT |
| MEDIUM | .github/workflows/release-deploy-maven.yml | 203 | # Create the bundle zip file | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …n-tests/src/test/resources/changelogs/common/lorem.txt | 1 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut sagittis feugiat velit tempus sollicitudin. Ut dapibus, tell | CODE |
| LOW | …n-tests/src/test/resources/changelogs/common/lorem.txt | 1 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut sagittis feugiat velit tempus sollicitudin. Ut dapibus, tell | CODE |