AI Slop Code Risk Monitor

vale-cli/vale

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

:pencil: A markup-aware linter for prose built with speed and extensibility in mind.

1.3 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for vale-cli/vale, a Go project with 6,313 GitHub stars. SynthScan examined 68,202 lines of code across 518 source files, recording 83 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 1.3 (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.3
Adjusted Signal
1.3
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
6.3K
Stars
Go
Language
68.2K
Lines of Code
518
Files
83
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.1/100 · LOW

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

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

PR Review Velocity Impact 6.2/100 · LOW

Which changes need focused human review? 83 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 2LOW 81

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 83 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 Block80 hits · 80 pts
SeverityFileLineSnippetContext
LOW.goreleaser.yml161 # Defaults to empty, which includes all artifacts.COMMENT
LOW.goreleaser.yml201 # Your apps's require license acceptance:COMMENT
LOW.goreleaser.yml241 #COMMENT
LOWcmd/vale/pkgver.go21// when the release it fetched needs a newer Vale than this one, the newestCOMMENT
LOWtestdata/comments/in/1.rs1// This module defines the set of command line arguments that ripgrep supports,COMMENT
LOWtestdata/comments/in/1.rs21impl Person {COMMENT
LOWinternal/lint/adoc.go61 "listing-caption!",COMMENT
LOWinternal/lint/adoc.go81// Asciidoctor processes the pool keeps warm.COMMENT
LOWinternal/lint/proc_pool.go21// These processes stay up for the run and convert documents as they arrive.COMMENT
LOWinternal/lint/html.go41//COMMENT
LOWinternal/lint/lint_test.go201 }COMMENT
LOWinternal/lint/ast.go241 // Found before `update` masks it out of the context.COMMENT
LOWinternal/lint/ast.go261 // block entirely. The whole paragraph is linted at once (on theCOMMENT
LOWinternal/lint/ast.go281 padComment = ""COMMENT
LOWinternal/lint/ast.go301 if strings.HasPrefix(txt, " ") && endsWithUnicodeSpace(buf) {COMMENT
LOWinternal/lint/ast.go421 // existing for paragraphs alone, so any rule scoped to a sentence --COMMENT
LOWinternal/lint/ast.go481}COMMENT
LOWinternal/lint/qdoc.go241}COMMENT
LOWinternal/lint/walk.go61 // linear in the document rather than linear per block.COMMENT
LOWinternal/lint/walk.go81 // idsHistory holds the selections marked on the tags in tagHistory, andCOMMENT
LOWinternal/lint/walk.go101COMMENT
LOWinternal/lint/walk.go121 // itself: an autolink's `href` and its text are the same source bytes, soCOMMENT
LOWinternal/lint/lint.go61 //COMMENT
LOWinternal/lint/lint.go481 //COMMENT
LOWinternal/lint/lint.go581// files are already linted in parallel, and a pool per block would multiply byCOMMENT
LOWinternal/lint/rst.go41// Python's text layer, which on Windows decodes with the console's code page,COMMENT
LOWinternal/lint/rst.go281// interpreter, or nil when that could not be established.COMMENT
LOWinternal/lint/myst.go21// targets, comments, and block breaks -- that a Markdown parser reads asCOMMENT
LOWinternal/lint/selection.go21const markAttr = "data-vale-doc"COMMENT
LOWinternal/lint/code/lang.go21 // Prefix matches a block comment's per-line decoration -- the ` *` thatCOMMENT
LOWinternal/lint/code/lang.go41 // Doc masks what the language's documentation convention marks as code:COMMENT
LOWinternal/lint/code/comments.go21 // front of the matching Source line: the opener, the dedent, and a lineCOMMENT
LOWinternal/lint/code/comments.go61 return falseCOMMENT
LOWinternal/lint/code/ex.go1package codeCOMMENT
LOWinternal/lint/code/ex.go21// a different standard than an implementation note, or excluded on its own.COMMENT
LOWinternal/core/markup.go1// The MIT License (MIT)COMMENT
LOWinternal/core/util.go201 }COMMENT
LOWinternal/core/file.go581 if old, ok := f.ChkToCtx[a.Check]; ok {COMMENT
LOWinternal/core/file.go601 case strings.HasPrefix(blk.Scope, "raw") && a.Match != "" &&COMMENT
LOWinternal/core/file.go681 }COMMENT
LOWinternal/core/file.go741 f.Alerts = keptCOMMENT
LOWinternal/core/view.go41// structured content. It is defined by a set of queries that can beCOMMENT
LOWinternal/core/location.go21 return s != ""COMMENT
LOWinternal/core/location.go201// search runs once per alert over the whole context, and spelling reportsCOMMENT
LOWinternal/core/source.go181 var sources []stringCOMMENT
LOWinternal/core/ini.go21COMMENT
LOWinternal/core/ini.go181// so `Vale.Spelling = warning` for Markdown quietly downgraded HTML too. SeeCOMMENT
LOWinternal/core/ini.go661 // Nothing reads a key we don't recognize here, so leaving it beCOMMENT
LOWinternal/spell/gospell.go41 segments map[string]segmentUseCOMMENT
LOWinternal/spell/gospell.go981 }COMMENT
LOWinternal/testsuite/suite.go41 // View names a View, found under a search path's `config/views`, toCOMMENT
LOWinternal/testsuite/run.go41 // paths is the configuration's StylesPath search list, read once and onlyCOMMENT
LOWinternal/regex/prefilter.go1package regexCOMMENT
LOWinternal/regex/prefilter.go21// Correctness rests on only ever returning literals that are genuinelyCOMMENT
LOWinternal/regex/regex.go1// Package regex adapts github.com/dlclark/regexp2 to the API Vale uses.COMMENT
LOWinternal/system/file.go21//COMMENT
LOWinternal/nlp/provider.go21 Scope string // section selectorCOMMENT
LOWinternal/nlp/provider.go41 // finds the first occurrence rather than the one that matched. A sentenceCOMMENT
LOWinternal/nlp/prose.go121//COMMENT
LOWinternal/nlp/tokenize.go81// begins, as a byte index into `text`.COMMENT
20 more matches not shown…
Self-Referential Comments1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUM.goreleaser.yml145# Create the GitHub release as a draft and upload assets to it *before* it'sCOMMENT
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMinternal/nlp/provider.go282// allow (fairly) seamless integration with non-Go libraries too (such asCOMMENT
Excessive Try-Catch Wrapping1 hit · 1 pts
SeverityFileLineSnippetContext
LOWinternal/lint/rst.go180 except Exception as e:CODE