AI Slop Code Risk Monitor

Jguer/yay

Name: Jguer/yay — 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).

Yet another Yogurt - An AUR Helper written in Go

1.3 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for Jguer/yay, a Go project with 13,813 GitHub stars. SynthScan examined 37,095 lines of code across 201 source files, recording 21 pattern matches distributed across 5 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-28

Last Push

13.8K

Stars

Language

37.1K

Lines of Code

201

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

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

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

PR Review Velocity Impact 6.6/100 · LOW

Which changes need focused human review? 21 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 15LOW 6

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 21 distinct pattern matches across 5 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.

Modern AI Meta-Vocabulary8 hits · 21 pts

Severity	File	Line	Snippet	Context
MEDIUM	.github/agents/agentic-workflows.md	45	- Configuration: `https://raw.githubusercontent.com/github/gh-aw/main/.github/aw/github-agentic-workflows.md`	CODE
MEDIUM⚡	.github/agents/agentic-workflows.md	69	Prompt file: `https://raw.githubusercontent.com/github/gh-aw/main/.github/aw/create-agentic-workflow.md`	CODE
MEDIUM⚡	.github/agents/agentic-workflows.md	79	Prompt file: `https://raw.githubusercontent.com/github/gh-aw/main/.github/aw/update-agentic-workflow.md`	CODE
MEDIUM⚡	.github/agents/agentic-workflows.md	89	Prompt file: `https://raw.githubusercontent.com/github/gh-aw/main/.github/aw/debug-agentic-workflow.md`	CODE
MEDIUM⚡	.github/agents/agentic-workflows.md	99	Prompt file: `https://raw.githubusercontent.com/github/gh-aw/main/.github/aw/upgrade-agentic-workflows.md`	CODE
MEDIUM	.github/agents/agentic-workflows.md	119	Prompt file: `https://raw.githubusercontent.com/github/gh-aw/main/.github/aw/create-shared-agentic-workflow.md`	CODE
MEDIUM	.github/agents/agentic-workflows.md	193	# Initialize repository for agentic workflows	COMMENT
MEDIUM	.github/agents/agentic-workflows.md	225	- Always reference the instructions file at `https://raw.githubusercontent.com/github/gh-aw/main/.github/aw/github-agent	CODE

Decorative Section Separators5 hits · 15 pts

Severity	File	Line	Snippet	Context
MEDIUM	scripts/gendocs/main.go	60	// ── HTML template ─────────────────────────────────────────────────────────────	COMMENT
MEDIUM	scripts/gendocs/main.go	143	// ── Lua page: TOC + version badges ────────────────────────────────────────────	COMMENT
MEDIUM	scripts/gendocs/main.go	191	// ── Markdown → HTML ───────────────────────────────────────────────────────────	COMMENT
MEDIUM	scripts/gendocs/main.go	204	// ── troff man page → Markdown ─────────────────────────────────────────────────	COMMENT
MEDIUM	scripts/gendocs/main.go	428	// ── helpers ───────────────────────────────────────────────────────────────────	COMMENT

Self-Referential Comments2 hits · 6 pts

Severity	File	Line	Snippet	Context
MEDIUM	.github/workflows/builder-image.yml	119	# Create a manifest list using the image digests from /tmp/digests/*	COMMENT
MEDIUM	.github/workflows/builder-image.yml	124	# Create the manifest list for GitHub Container Registry	COMMENT

Over-Commented Block5 hits · 5 pts

Severity	File	Line	Snippet	Context
LOW	scripts/gendocs/main.go	1	// Command gendocs renders yay's doc/ directory into a static HTML site	COMMENT
LOW	.github/workflows/repo-assist.lock.yml	1	# gh-aw-metadata: {"schema_version":"v4","frontmatter_hash":"835c908bcbe7b71835e9e038dd3fbdf12e0b1561097634b99d2b9cf4ade	COMMENT
LOW	.github/workflows/repo-assist.lock.yml	21	# gh aw compile	COMMENT
LOW	.github/workflows/repo-assist.lock.yml	41	# Secrets used:	COMMENT
LOW	pkg/dep/topo/dep.go	241	}	COMMENT

Slop Phrases1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	pkg/news/news_test.go	87	<p>The most notable changes are the offered feeds and the feed location. Archweb only offers an Atom feed which is	CODE