AI Slop Code Risk Monitor

humanlayer/12-factor-agents

SlopCodeMonitor badge for humanlayer/12-factor-agents Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

What are the principles we can use to build LLM-powered software that is actually good enough to put in the hands of production customers?

0.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for humanlayer/12-factor-agents, a TypeScript project with 26,933 GitHub stars. SynthScan examined 76,972 lines of code across 302 source files, recording 37 pattern matches distributed across 9 syntactic categories. The legacy adjusted pattern signal is 0.7 (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.7
Adjusted Signal
0.7
Raw Pattern Score
100%
Time Factor
2025-09-21
Last Push
26.9K
Stars
TypeScript
Language
77.0K
Lines of Code
302
Files
37
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 2.7/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.6/100 · LOW

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

Agent Over-Engineering Ratio 0.4/100 · LOW

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

PR Review Velocity Impact 3.6/100 · LOW

Which changes need focused human review? 37 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 10LOW 27

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 37 distinct pattern matches across 9 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.

Self-Referential Comments6 hits · 18 pts
SeverityFileLineSnippetContext
MEDIUMworkshops/2025-07-16/test_notebook_colab_sim.sh40# Create a Python script to execute the notebookCOMMENT
MEDIUMworkshops/2025-07-16/walkthrough/05-main.py20 # Create a new thread with the user's messageCOMMENT
MEDIUMworkshops/2025-07-16/walkthrough/07-main.py6 # Create a new thread with the user's messageCOMMENT
MEDIUMworkshops/2025-07-16/walkthrough/03-main.py2 # Create a new thread with the user's messageCOMMENT
MEDIUMworkshops/2025-07-16/walkthrough/02-main.py2 # Create a new thread with the user's messageCOMMENT
MEDIUMworkshops/2025-07-16/walkthrough/01-main.py2 # Create a new thread with the user's message as the initial eventCOMMENT
Modern AI Meta-Vocabulary3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUMcontent/factor-09-compact-errors.md23 # if we get an error, we can add it to the context window and try againCOMMENT
MEDIUMcontent/factor-09-compact-errors.md57 # break the loop, reset parts of the context window, escalate to a human, or whatever else you want to doCOMMENT
MEDIUMcontent/factor-03-own-your-context-window.md3### 3. Own your context windowCOMMENT
Deep Nesting7 hits · 7 pts
SeverityFileLineSnippetContext
LOWworkshops/2025-07-16/walkthroughgen_py.py87CODE
LOWworkshops/2025-07-16/walkthrough/05-agent.py4CODE
LOWworkshops/2025-07-16/walkthrough/03b-agent.py13CODE
LOWworkshops/2025-07-16/walkthrough/07-agent.py38CODE
LOWworkshops/2025-07-16/walkthrough/07-agent.py13CODE
LOWworkshops/2025-07-16/hack/inspect_notebook.py9CODE
LOWworkshops/2025-07-16/hack/analyze_log_capture.py9CODE
Redundant / Tautological Comments5 hits · 6 pts
SeverityFileLineSnippetContext
LOWworkshops/2025-07-16/walkthroughgen_py.py148 # Check if args are providedSTRING
LOWworkshops/2025-07-16/walkthroughgen_py.py153 # Check if kwargs are providedSTRING
LOWworkshops/2025-07-16/test_notebook_colab_sim.sh103# Check if Python BAML client was generatedCOMMENT
LOWworkshops/2025-07-16/test_notebook_colab_sim.sh106 # Check if it's Python or TypeScriptCOMMENT
LOWworkshops/2025-07-16/hack/analyze_log_capture.py24 # Check if this is a log capture test cellCOMMENT
Excessive Try-Catch Wrapping4 hits · 5 pts
SeverityFileLineSnippetContext
LOWworkshops/2025-07-16/test_notebook_colab_sim.sh83except Exception as e:CODE
MEDIUMworkshops/2025-07-16/hack/testing.md140 " print(f'Error: {e}')"CODE
LOWcontent/factor-09-compact-errors.md22 except Exception as e:CODE
LOWcontent/factor-09-compact-errors.md48 except Exception as e:CODE
Fake / Example Data5 hits · 5 pts
SeverityFileLineSnippetContext
LOWdrafts/a2h-spec.md132 "name": "John Doe",CODE
LOWdrafts/a2h-spec.md304 "name": "Jane Doe",CODE
LOWdrafts/a2h-spec.md309 "name": "John Doe",CODE
LOWdrafts/a2h-spec.md325 "name": "Jane Doe",CODE
LOWdrafts/a2h-spec.md343 "name": "John Doe",CODE
Unused Imports4 hits · 4 pts
SeverityFileLineSnippetContext
LOWworkshops/2025-07-16/walkthroughgen_py.py7CODE
LOWworkshops/2025-07-16/walkthroughgen_py.py8CODE
LOWworkshops/2025-07-16/walkthrough/03b-agent.py2CODE
LOWhack/contributors_markdown/contributors_markdown.py20CODE
Hyper-Verbose Identifiers2 hits · 2 pts
SeverityFileLineSnippetContext
LOWworkshops/2025-07-16/walkthroughgen_py.py170def convert_walkthrough_to_notebook(yaml_path, output_path):STRING
LOWpackages/walkthroughgen/src/cli.ts209function generateRichSectionMarkdown(CODE
Over-Commented Block1 hit · 1 pts
SeverityFileLineSnippetContext
LOWpackages/create-12-factor-agent/template/src/cli.ts41 const args = process.argv.slice(2);COMMENT