AI Slop Code Risk Monitor

pressly/goose

Name: pressly/goose — Go Code Quality & Security Review | AI Slop Code Risk Monitor
Creator: AI Slop Code Risk Monitor

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

A database migration tool. Supports SQL migrations and Go functions.

1.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for pressly/goose, a Go project with 11,644 GitHub stars. SynthScan examined 19,877 lines of code across 219 source files, recording 24 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 1.4 (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.4

Adjusted Signal

1.4

Raw Pattern Score

100%

Time Factor

2026-10-31

Last Push

11.6K

Stars

Language

19.9K

Lines of Code

219

Files

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 6.8/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 24 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 0.0/100 · LOW

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

PR Review Velocity Impact 6.3/100 · LOW

Which changes need focused human review? 24 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 1LOW 23

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 24 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 Block19 hits · 19 pts

Severity	File	Line	Snippet	Context
LOW	provider.go	41		COMMENT
LOW	provider.go	561	//	COMMENT
LOW	provider_run.go	361	return retry.Do(ctx, b, func(ctx context.Context) error {	COMMENT
LOW	migrate.go	221	return 0, multierr.Append(err, createErr)	COMMENT
LOW	migrate.go	281	if err != nil {	COMMENT
LOW	migration.go	141	// Mode is the transaction mode for the migration. When one of the run functions is set, the	COMMENT
LOW	database/store.go	21	// migration logic.	COMMENT
LOW	database/doc.go	1	// Package database defines a generic [Store] interface for goose to use when interacting with the	COMMENT
LOW	database/store_extended.go	1	package database	COMMENT
LOW	database/store_extended.go	21	// In short, it's exported to allows implementors to have a compile-time check that they are	COMMENT
LOW	database/dialect/querier_extended.go	1	package dialect	COMMENT
LOW	database/dialect/querier.go	1	package dialect	COMMENT
LOW	internal/legacystore/legacystore.go	21	// The underlying implementation does not modify the error. It is the callers	COMMENT
LOW	lock/postgres.go	21	// - Heartbeat (5s): How often the lock gets refreshed to keep it alive	COMMENT
LOW	lock/table_locker_options.go	101	}	COMMENT
LOW	lock/locktesting/locktesting.go	101	}	COMMENT
LOW	examples/README.md	1	# 1. [SQL migrations](sql-migrations)	COMMENT
LOW	.github/workflows/lint.yaml	41		COMMENT
LOW	pkg/dockermanage/doc.go	1	// Package dockermanage provides lightweight Docker container lifecycle helpers for integration	COMMENT

AI Slop Vocabulary1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	provider.go	132	// to add this once we're on go1.21 and leverage the new slog package.	COMMENT

Verbosity Indicators2 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	provider.go	562	// 1. Users have enabled out-of-order migrations, in which case we need to check if any	COMMENT
LOW	provider.go	566	// 2. Users have disabled out-of-order migrations (default), in which case we need to check if all	COMMENT

Redundant / Tautological Comments2 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	scripts/release-notes.sh	5	# Check if the required argument is provided	COMMENT
LOW	scripts/release-notes.sh	14	# Check if the changelog file exists	COMMENT