AI Slop Code Risk Monitor

anthropics/claude-plugins-community

SlopCodeMonitor badge for anthropics/claude-plugins-community Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Community plugin marketplace for Claude Cowork and Claude Code. Read-only mirror — submit plugins at clau.de/plugin-directory-submission.

4.1 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for anthropics/claude-plugins-community, a JavaScript project with 4,803 GitHub stars. SynthScan examined 29,011 lines of code across 125 source files, recording 77 pattern matches distributed across 10 syntactic categories. The legacy adjusted pattern signal is 4.1 (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.

4.1
Adjusted Signal
4.1
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
4.8K
Stars
JavaScript
Language
29.0K
Lines of Code
125
Files
77
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 11.6/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.2/100 · LOW

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

Agent Over-Engineering Ratio 8.3/100 · LOW

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

PR Review Velocity Impact 17.4/100 · LOW

Which changes need focused human review? 77 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 17LOW 60

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 77 distinct pattern matches across 10 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 Separators15 hits · 45 pts
SeverityFileLineSnippetContext
MEDIUM.github/actions/bump-plugin-shas/scripts/bump.sh313 # ── Source-owner verification gate (github.com sources) ────────────────────COMMENT
MEDIUM.github/actions/bump-plugin-shas/scripts/bump.sh362 # ── Identity leg (owner-baseline, when committed) ─────────────────────────COMMENT
MEDIUM.github/actions/bump-plugin-shas/scripts/bump.sh532# ============================================================================COMMENT
MEDIUM.github/actions/bump-plugin-shas/scripts/bump.sh534# ============================================================================COMMENT
MEDIUM.github/actions/bump-plugin-shas/scripts/bump.sh589 # ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUM.github/actions/bump-plugin-shas/scripts/bump.sh593 # ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUM.github/actions/bump-plugin-shas/scripts/bump.sh664 # ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUM.github/actions/bump-plugin-shas/scripts/bump.sh667 # ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUM.github/actions/owner-liveness-sweep/test-sweep.sh14# ── gh shim ──────────────────────────────────────────────────────────────────COMMENT
MEDIUM.github/actions/owner-liveness-sweep/test-sweep.sh40# ── fixtures ─────────────────────────────────────────────────────────────────COMMENT
MEDIUM.github/actions/owner-liveness-sweep/scripts/sweep.sh60# ── 1. Extract external github.com sources → owners + repos ─────────────────COMMENT
MEDIUM.github/actions/owner-liveness-sweep/scripts/sweep.sh109# ── 2. Batched GraphQL resolution ───────────────────────────────────────────COMMENT
MEDIUM.github/actions/owner-liveness-sweep/scripts/sweep.sh164# ── 3. Classify ─────────────────────────────────────────────────────────────COMMENT
MEDIUM.github/actions/owner-liveness-sweep/scripts/sweep.sh210# ── 4. Step summary ─────────────────────────────────────────────────────────COMMENT
MEDIUM.github/actions/owner-liveness-sweep/scripts/sweep.sh248# ── 5. Mode tails ───────────────────────────────────────────────────────────COMMENT
Over-Commented Block29 hits · 29 pts
SeverityFileLineSnippetContext
LOW.github/freeze-shas.txt1# freeze-shas — marketplace entry names held at their CURRENT source.shaCOMMENT
LOW.github/workflows/owner-liveness-sweep.yml1name: Owner Liveness SweepCOMMENT
LOW.github/workflows/bump-plugin-shas.yml1name: Bump Plugin SHAsCOMMENT
LOW.github/workflows/bump-plugin-shas.yml81 id: bumpCOMMENT
LOW.github/actions/bump-plugin-shas/test-bump.sh1#!/usr/bin/env bashCOMMENT
LOW.github/actions/bump-plugin-shas/test-bump.sh341# cases above — they need `gh api`, `git ls-remote`, and (for the stale-entryCOMMENT
LOW.github/actions/bump-plugin-shas/test-bump-manifest.sh1#!/usr/bin/env bashCOMMENT
LOW.github/actions/bump-plugin-shas/test-bump-manifest.sh201# @base64d is jq 1.6+. CI (ubuntu) ships 1.6+; the guard only matters for a dev on anCOMMENT
LOW.github/actions/bump-plugin-shas/scripts/bump.sh1#!/usr/bin/env bashCOMMENT
LOW.github/actions/bump-plugin-shas/scripts/bump.sh41# latest published RELEASE's commit instead of upstream HEAD. Absent/emptyCOMMENT
LOW.github/actions/bump-plugin-shas/scripts/bump.sh121COMMENT
LOW.github/actions/bump-plugin-shas/scripts/bump.sh221 doneCOMMENT
LOW.github/actions/bump-plugin-shas/scripts/bump.sh321 # API and require the canonical full_name to still match:COMMENT
LOW.github/actions/bump-plugin-shas/scripts/bump.sh361 fiCOMMENT
LOW.github/actions/validate-plugins/action.yml141 # intermittently stalls or is skipped (npm --omit=optional, some pnpmCOMMENT
LOW…ons/validate-plugins/scripts/11-validate-invariants.sh1#!/usr/bin/env bashCOMMENT
LOW…/actions/validate-plugins/scripts/00-detect-changes.sh1#!/usr/bin/env bashCOMMENT
LOW.github/actions/validate-plugins/lib/common.sh121 return 1COMMENT
LOW.github/actions/validate-plugins/lib/common.sh141# relaxes; any other value, incl. unset/true, requires a real manifest).COMMENT
LOW.github/actions/scan-plugins/test-pin-check.sh1#!/usr/bin/env bashCOMMENT
LOW…ithub/actions/scan-plugins/scripts/static-pin-check.sh1#!/usr/bin/env bashCOMMENT
LOW.github/actions/scan-plugins/lib/pin-check.sh1#!/usr/bin/env bashCOMMENT
LOW.github/actions/scan-plugins/lib/pin-check.sh21# pinned — npm `pkg@1.2.3` (digit-led exact; prerelease/build metadata ok);COMMENT
LOW.github/actions/scan-plugins/lib/pin-check.sh41# PROVENANCE / KEEP IN SYNC: this is a faithful extract ofCOMMENT
LOW.github/actions/scan-plugins/lib/pin-check.sh61# server. `bare` rows are raw — refine with pin_check_refine_bare.COMMENT
LOW.github/actions/scan-plugins/lib/targets.sh1#!/usr/bin/env bashCOMMENT
LOW.github/actions/owner-liveness-sweep/test-sweep.sh1#!/usr/bin/env bashCOMMENT
LOW.github/actions/owner-liveness-sweep/scripts/sweep.sh1#!/usr/bin/env bashCOMMENT
LOW.github/actions/owner-liveness-sweep/scripts/sweep.sh21# resolves at all (deleted or made private).COMMENT
Structural Annotation Overuse18 hits · 27 pts
SeverityFileLineSnippetContext
LOWtres-finance-plugin/skills/tres-onboarding/SKILL.md76### Step 1: Upload WalletsCOMMENT
LOWtres-finance-plugin/skills/tres-onboarding/SKILL.md87### Step 2: Data Collection (Commit)COMMENT
LOWtres-finance-plugin/skills/tres-onboarding/SKILL.md99### Step 3: Validate BalancesCOMMENT
LOWtres-finance-plugin/skills/tres-onboarding/SKILL.md110### Step 4: ReconciliationCOMMENT
LOWtres-finance-plugin/skills/tres-onboarding/SKILL.md121### Step 5: Cost BasisCOMMENT
LOWtres-finance-plugin/skills/tres-onboarding/SKILL.md134### Step 6: Export Unidentified AddressesCOMMENT
LOWtres-finance-plugin/skills/tres-onboarding/SKILL.md151### Step 7: Import ContactsCOMMENT
LOWtres-finance-plugin/skills/tres-onboarding/SKILL.md162### Step 8: Rollup RulesCOMMENT
LOW…-plugin/skills/tres-asc845-swap-reprice-skill/SKILL.md44### Step 1: Gather ParametersCOMMENT
LOW…-plugin/skills/tres-asc845-swap-reprice-skill/SKILL.md55### Step 2: Query SubtransactionsCOMMENT
LOW…-plugin/skills/tres-asc845-swap-reprice-skill/SKILL.md82### Step 3: Run the Orchestrator ScriptCOMMENT
LOW…-plugin/skills/tres-asc845-swap-reprice-skill/SKILL.md103### Step 4: Repricing Logic (ASC 845)COMMENT
LOW…-plugin/skills/tres-asc845-swap-reprice-skill/SKILL.md160### Step 5: Preview the Reprice PlanCOMMENT
LOW…-plugin/skills/tres-asc845-swap-reprice-skill/SKILL.md179### Step 6: Execute (with user confirmation)COMMENT
LOW…-plugin/skills/tres-asc845-swap-reprice-skill/SKILL.md205### Step 7: VerifyCOMMENT
LOW…es-finance-plugin/skills/tres-report-analyzer/SKILL.md16## Step 1: Identify the report typeCOMMENT
LOW…es-finance-plugin/skills/tres-report-analyzer/SKILL.md43## Step 2: Run the analysisCOMMENT
LOW…es-finance-plugin/skills/tres-report-analyzer/SKILL.md89## Step 3: Present findingsCOMMENT
Deep Nesting6 hits · 6 pts
SeverityFileLineSnippetContext
LOW…res-asc845-swap-reprice-skill/scripts/reprice_swaps.py141CODE
LOW…res-asc845-swap-reprice-skill/scripts/reprice_swaps.py157CODE
LOW…n/skills/tres-report-create/tests/run_report_matrix.py251CODE
LOW…/skills/tres-report-analyzer/scripts/analyze_report.py26CODE
LOW…/skills/tres-report-analyzer/scripts/analyze_report.py144CODE
LOW…/skills/tres-report-analyzer/scripts/analyze_report.py278CODE
Hyper-Verbose Identifiers4 hits · 4 pts
SeverityFileLineSnippetContext
LOW…c845-swap-reprice-skill/scripts/orchestrate_reprice.py36def generate_graphql_mutations(plan, batch_size=50):CODE
LOW…c845-swap-reprice-skill/scripts/orchestrate_reprice.py53def generate_execution_script(plan, output_path):CODE
LOW…/skills/tres-report-analyzer/scripts/analyze_report.py144def analyze_reconciliation_ledger(wb):CODE
LOW…/skills/tres-report-analyzer/scripts/analyze_report.py237def analyze_asset_roll_forward(wb):CODE
Modern AI Meta-Vocabulary1 hit · 2 pts
SeverityFileLineSnippetContext
MEDIUMtres-finance-plugin/README.md26│ ├── tres-onboarding/ # Full entity onboarding (orchestrates sub-skills)CODE
AI Slop Vocabulary1 hit · 2 pts
SeverityFileLineSnippetContext
MEDIUM…n/skills/tres-report-create/tests/run_report_matrix.py334 except Exception as exc: # noqa: BLE001 - harness records every failureCODE
Redundant / Tautological Comments1 hit · 2 pts
SeverityFileLineSnippetContext
LOW…/skills/tres-report-analyzer/scripts/analyze_report.py33 # Check if first row looks like a pivot header (single value like "Values")COMMENT
Excessive Try-Catch Wrapping1 hit · 1 pts
SeverityFileLineSnippetContext
LOW…n/skills/tres-report-create/tests/run_report_matrix.py334 except Exception as exc: # noqa: BLE001 - harness records every failureCODE
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOW…n/skills/tres-report-create/tests/run_report_matrix.py24CODE