Repository Analysis

anthropics/claude-plugins-community

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

4.5 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of anthropics/claude-plugins-community, a Python project with 2,676 GitHub stars. SynthScan v2.0 examined 26,115 lines of code across 114 source files, recording 77 pattern matches distributed across 10 syntactic categories. The overall adjusted score of 4.5 places this repository in the Likely human-written band.

The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).

4.5
Adjusted Score
4.5
Raw Score
100%
Time Factor
2026-08-25
Last Push
2.7K
Stars
Python
Language
26.1K
Lines of Code
114
Files
77
Pattern Hits
2026-08-29
Scan Date
0.00
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

Longitudinal tracking requires multiple scan runs. Once this repository is re-scanned after new commits land, this chart will visualise how the synthetic code signal evolves over time — enabling you to detect whether AI authorship is growing, stabilising, or being actively corrected by human engineers.

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

Severity Breakdown

Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.

CRITICAL 0HIGH 0MEDIUM 17LOW 60

Directory Score Breakdown

This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.

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 statistically significant AI authorship indicator. 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 diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.

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