AI Slop Code Risk Monitor

ariga/atlas

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

Declarative schema migrations with schema-as-code workflows

0.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for ariga/atlas, a Go project with 8,804 GitHub stars. SynthScan examined 155,761 lines of code across 469 source files, recording 43 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 0.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.

0.4
Adjusted Signal
0.4
Raw Pattern Score
100%
Time Factor
2026-10-28
Last Push
8.8K
Stars
Go
Language
155.8K
Lines of Code
469
Files
43
Pattern Hits
2026-10-31
Scan Date
0.01
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 1.3/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.1/100 · LOW

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

Agent Over-Engineering Ratio 0.5/100 · LOW

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

PR Review Velocity Impact 1.9/100 · LOW

Which changes need focused human review? 43 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 3MEDIUM 1LOW 39

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 43 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 Block37 hits · 37 pts
SeverityFileLineSnippetContext
LOWcmd/atlas/internal/cmdext/cmdext.go181 return cty.NilVal, errorf("getting token: %v", err)COMMENT
LOWcmd/atlas/internal/cmdext/cmdext.go281 return cty.ObjectVal(obj), nilCOMMENT
LOWcmd/atlas/internal/cmdext/cmdext.go341// vars = {COMMENT
LOWcmd/atlas/internal/sqlparse/sqlparse.go21type Parser interface {COMMENT
LOWcmd/atlas/internal/migrate/ent/revision_query.go261 }COMMENT
LOWcmd/atlas/internal/migrate/ent/revision_query.go281 grbuild.flds = &_q.ctx.FieldsCOMMENT
LOWcmd/atlas/internal/migrate/ent/revision_create.go321// ).COMMENT
LOWcmd/atlas/internal/migrate/ent/revision_create.go501 u.Set(revision.FieldOperatorVersion, v)COMMENT
LOWcmd/atlas/internal/migrate/ent/revision_create.go861 }COMMENT
LOWcmd/atlas/internal/migrate/ent/revision_create.go901type RevisionUpsertBulk struct {COMMENT
LOWcmd/atlas/internal/migrate/ent/tx.go41 CommitFunc func(context.Context, *Tx) errorCOMMENT
LOWcmd/atlas/internal/migrate/ent/tx.go101 //COMMENT
LOWcmd/atlas/internal/migrate/ent/tx.go161// of them in order to commit or rollback the transaction.COMMENT
LOWcmd/atlas/internal/migrate/ent/migrate/migrate.go21 // for the ids of each entity (table).COMMENT
LOWcmd/atlas/internal/migrate/ent/migrate/migrate.go61// WriteTo writes the schema changes to w instead of running them against the database.COMMENT
LOWcmd/atlas/internal/cmdapi/project.go301 return r.As(&e.Format)COMMENT
LOWcmd/atlas/internal/cmdapi/project.go381//COMMENT
LOWcmd/atlas/internal/cmdapi/project.go501// a global one. For example:COMMENT
LOWschemahcl/stdlib_test.go341 // cty.NumberIntVal(1)COMMENT
LOWschemahcl/spec.go61COMMENT
LOWschemahcl/schemahcl.go81// WithScopedEnums configured a list of allowed ENUMs to be used inCOMMENT
LOWschemahcl/schemahcl.go141// the string defined in the data source block.COMMENT
LOWschemahcl/schemahcl.go161 c.datasrc = make(map[string]BlockFunc)COMMENT
LOWschemahcl/schemahcl.go201// WithInitBlock("atlas", func(ctx *hcl.EvalContext, b *hclsyntax.Block) (cty.Value, hcl.Diagnostics) {COMMENT
LOWatlasexec/atlas.go141//COMMENT
LOWsql/internal/sqlx/sqlx.go301}COMMENT
LOWsql/internal/sqlx/diff.go21COMMENT
LOWsql/sqlite/inspect.go381 // AutoIncrement describes the `AUTOINCREMENT` configuration.COMMENT
LOWsql/schema/migrate_test.go121 // Output:COMMENT
LOWsql/schema/inspect.go81 //COMMENT
LOWsql/schema/inspect.go101 //COMMENT
LOWsql/schema/inspect.go121 // s.t // include table 't' under schema 's'.COMMENT
LOWsql/schema/schema.go361)COMMENT
LOWsql/schema/schema.go481 //COMMENT
LOWsql/schema/migrate.go21 // type RenameType struct {COMMENT
LOWsql/schema/migrate.go261COMMENT
LOWsql/sqltool/doc.go1// Copyright 2021-present The Atlas Authors. All rights reserved.COMMENT
Cross-File Repetition3 hits · 15 pts
SeverityFileLineSnippetContext
HIGH…dapi/testdata/import/goose_gold/2_second_migration.sql0|| to_char(d + interval '1 month', 'yyyy-mm-dd 00:00:00') ||STRING
HIGH…al/cmdapi/testdata/import/goose/2_second_migration.sql0|| to_char(d + interval '1 month', 'yyyy-mm-dd 00:00:00') ||STRING
HIGHsql/sqltool/testdata/goose/2_second_migration.sql0|| to_char(d + interval '1 month', 'yyyy-mm-dd 00:00:00') ||STRING
Modern AI Meta-Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMskills/atlas/references/drift.md122## Schema Monitoring (Atlas Cloud, agent-based)COMMENT
Fake / Example Data2 hits · 2 pts
SeverityFileLineSnippetContext
LOWsql/migrate/testdata/lex/15_dollar_quote.sql118UPDATE table SET description = $$Lorem ipsum dolor sit amet$$ WHERE id = 123;CODE
LOWsql/migrate/testdata/lex/15_dollar_quote.sql118UPDATE table SET description = $$Lorem ipsum dolor sit amet$$ WHERE id = 123;CODE