AI Slop Code RIsk Monitor

ykdojo/claude-code-tips

45+ tips for getting the most out of Claude Code, from basics to advanced - includes a custom status line script and Claude Code running itself in a container. Also includes the dx plugin: skills for everyday dev workflows.

9.7 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for ykdojo/claude-code-tips, a HTML project with 10,210 GitHub stars. SynthScan examined 12,062 lines of code across 51 source files, recording 45 pattern matches distributed across 7 syntactic categories. The legacy adjusted pattern signal is 9.7 (Moderate 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.

9.7
Adjusted Signal
9.7
Raw Pattern Score
100%
Time Factor
2026-09-25
Last Push
10.2K
Stars
HTML
Language
12.1K
Lines of Code
51
Files
45
Pattern Hits
2026-10-12
Scan Date
0.00
HC Hit Rate

Risk Review · v3

Use each vector to guide manual verification of the underlying findings.

Cognitive Ownership Risk 19.0/100 · LOW

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

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

PR Review Velocity Impact 37.4/100 · MEDIUM

Which changes need focused human review? 45 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 34LOW 11

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

Decorative Section Separators22 hits · 66 pts
SeverityFileLineSnippetContext
MEDIUM⚡scripts/setup.sh282# ============================================COMMENT
MEDIUM⚡scripts/setup.sh284# ============================================COMMENT
MEDIUMscripts/setup.sh113# ============================================COMMENT
MEDIUMscripts/setup.sh115# ============================================COMMENT
MEDIUMscripts/setup.sh127# ============================================COMMENT
MEDIUMscripts/setup.sh129# ============================================COMMENT
MEDIUMscripts/setup.sh148# ============================================COMMENT
MEDIUMscripts/setup.sh150# ============================================COMMENT
MEDIUMscripts/setup.sh162# ============================================COMMENT
MEDIUMscripts/setup.sh164# ============================================COMMENT
MEDIUMscripts/setup.sh176# ============================================COMMENT
MEDIUMscripts/setup.sh178# ============================================COMMENT
MEDIUMscripts/setup.sh190# ============================================COMMENT
MEDIUMscripts/setup.sh192# ============================================COMMENT
MEDIUMscripts/setup.sh204# ============================================COMMENT
MEDIUMscripts/setup.sh206# ============================================COMMENT
MEDIUMscripts/setup.sh218# ============================================COMMENT
MEDIUMscripts/setup.sh220# ============================================COMMENT
MEDIUMscripts/setup.sh238# ============================================COMMENT
MEDIUMscripts/setup.sh240# ============================================COMMENT
MEDIUMscripts/setup.sh266# ============================================COMMENT
MEDIUMscripts/setup.sh268# ============================================COMMENT
Modern AI Meta-Vocabulary9 hits · 28 pts
SeverityFileLineSnippetContext
MEDIUMREADME.md538### Advanced: Multi-model orchestrationCOMMENT
MEDIUMREADME.md1029📺 **Related talk**: [Claude Code Masterclass](https://youtu.be/9UdZhTnMrTA) - lessons and project examples from 31 monthCODE
MEDIUMREADME.md1033📰 **Newsletter**: [Agentic Coding with Discipline and Skill](https://agenticcoding.substack.com/) - bring the practice oCODE
MEDIUM⚡content/spectrum-of-agentic-coding.md1# The spectrum of agentic coding: From vibe coding to high-quality software engineeringCOMMENT
MEDIUM⚡content/spectrum-of-agentic-coding.md3After spending over a billion tokens on AI-assisted coding over the past two and a half years - ever since I created my CODE
MEDIUM⚡content/spectrum-of-agentic-coding.md7## Four levels of agentic/vibe codingCOMMENT
MEDIUM⚡content/spectrum-of-agentic-coding.md9![50 shades of agentic coding](https://raw.githubusercontent.com/ykdojo/claude-code-tips/main/content/50-shades-of-agentCODE
MEDIUMcontent/spectrum-of-agentic-coding.md54## The agentic coding matrixCOMMENT
MEDIUMscripts/context-bar.sh100# Get context window size from JSON (accurate), but calculate tokens from transcriptCOMMENT
Self-Referential Comments3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUMscripts/test-half-clone.sh86# Create a test conversation with N messagesCOMMENT
MEDIUMscripts/test-half-clone.sh321 # Create a 6-message conversation where the THIRD user message (which will beCOMMENT
MEDIUMscripts/test-half-clone.sh379 # Create a conversation with thinking blocks in assistant messagesCOMMENT
Structural Annotation Overuse4 hits · 6 pts
SeverityFileLineSnippetContext
LOWskills/review-claudemd/SKILL.md10## Step 1: Find conversation historyCOMMENT
LOWskills/review-claudemd/SKILL.md21## Step 2: Extract recent conversationsCOMMENT
LOWskills/review-claudemd/SKILL.md46## Step 3: Spin up subagentsCOMMENT
LOWskills/review-claudemd/SKILL.md75## Step 4: Aggregate findingsCOMMENT
Redundant / Tautological Comments3 hits · 3 pts
SeverityFileLineSnippetContext
LOW⚡scripts/setup.sh291# Check if shell config was modifiedCOMMENT
LOWscripts/setup.sh14# Check if running from local repo or via curlCOMMENT
LOWscripts/half-clone-conversation.sh302 # Check if it's a clone commandCOMMENT
Over-Commented Block3 hits · 3 pts
SeverityFileLineSnippetContext
LOWscripts/check-context.sh1#!/bin/bashCOMMENT
LOWscripts/half-clone-conversation.sh1#!/usr/bin/env bashCOMMENT
LOW…ls/private-github-search/private-github-search-sync.sh1#!/bin/bashCOMMENT
Example Usage Blocks1 hit · 2 pts
SeverityFileLineSnippetContext
LOWscripts/half-clone-conversation.sh8# Usage:COMMENT