AI Slop Code Risk Monitor

dair-ai/AI-Papers-of-the-Week

SlopCodeMonitor badge for dair-ai/AI-Papers-of-the-Week Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).
15.4 Elevated pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for dair-ai/AI-Papers-of-the-Week. SynthScan examined 3,250 lines of code across 8 source files, recording 16 pattern matches distributed across 2 syntactic categories. The legacy adjusted pattern signal is 15.4 (Elevated 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.

15.4
Adjusted Signal
15.4
Raw Pattern Score
100%
Time Factor
—
Last Push
—
Stars
—
Language
3.2K
Lines of Code
8
Files
16
Pattern Hits
2026-10-31
Scan Date
0.50
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 53.7/100 · HIGH

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

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

PR Review Velocity Impact 60.3/100 · HIGH

Which changes need focused human review? 16 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

Run additional scans to build a history of the legacy pattern signal. Score changes are not a measure of AI adoption or code quality.

No multi-scan history yet — run the scanner again to build trend data.

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 4MEDIUM 12LOW 0

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 16 distinct pattern matches across 2 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-Vocabulary12 hits · 30 pts
SeverityFileLineSnippetContext
MEDIUMyears/2025.md394| 5) **Agentic Misalignment** - This study introduces the concept of agentic misalignment, where LLM-based agents autonoCODE
MEDIUM⚡years/2026.md29| 2) **LongHarness** - Agents that reason over document collections larger than their context window usually keep retrieCODE
MEDIUM⚡years/2026.md33| 6) **ReHarness** - Agent memory harnesses usually only write forward, so a lesson goes into the bank and is never checCODE
MEDIUM⚡years/2026.md34| 7) **The Agentic Scientist** - Fully autonomous research agents tend to have a narrow range of ideas and hill-climb myCODE
MEDIUM⚡years/2026.md45| 2) **CorpusMap** - Agents that search large document collections usually see the corpus as a flat set of files, so a rCODE
MEDIUM⚡years/2026.md46| 3) **VeriHarness** - A common practice with long-horizon agents is to sample several rollouts and trust the answers thCODE
MEDIUM⚡years/2026.md50| 7) **VERA** - Long-horizon agents need environments that can be resumed at any stage and scored from observable evidenCODE
MEDIUMyears/2026.md66| 7) **Jev-Mem** - Many agentic memory systems use an autoregressive LLM to decide how memories are organized, retrievedCODE
MEDIUMyears/2026.md79| 4) **WFM** - More agents now store long-term memory as an LLM Wiki, a folder of markdown pages linked to each other. ECODE
MEDIUMyears/2026.md98| 7) **Salesforce Koa** - Custom enterprise models usually need a training set someone has to build. Salesforce trained CODE
MEDIUMyears/2026.md101| 10) **Skill-Based Agentic Evaluation** - Storing a fixed reference answer for every eval case breaks when the underlyiCODE
MEDIUMyears/2026.md533| 2) **Codified Context** - Single-file AGENTS.md manifests don’t scale beyond modest codebases. A 1,000-line prototype CODE
Synthetic Comment Markers4 hits · 20 pts
SeverityFileLineSnippetContext
HIGHyears/2025.md689| 6) **Hallucinations Improve LLMs in Drug Discovery** - Claims that LLMs can achieve better performance in drug discoveCODE
HIGHyears/2024.md308| 3) **Improved RAG with Self-Reasoning** - presents an end-to-end self-reasoning framework to improve the reliability aCODE
HIGHyears/2024.md363| 2) **CriticGPT** - a new model based on GPT-4 to help write critiques for responses generated by ChatGPT; trained usinCODE
HIGHyears/2023.md555| 6) **TinyStories** - Explores how small LMs can be and still speak coherent English. <br>● Synthetic story dataset: CCODE