Community plugin marketplace for Claude Cowork and Claude Code. Read-only mirror — submit plugins at clau.de/plugin-directory-submission.
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.
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.
Can maintainers explain intent, assumptions, and trade-offs? 60 finding(s).
Are imports declared and package/API names verified? 1 finding(s).
Are wrappers, guards, and repeated structures necessary? 20 finding(s).
Which changes need focused human review? 77 finding(s).
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.
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.
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.
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.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | .github/actions/bump-plugin-shas/scripts/bump.sh | 313 | # ── Source-owner verification gate (github.com sources) ──────────────────── | COMMENT |
| MEDIUM | .github/actions/bump-plugin-shas/scripts/bump.sh | 362 | # ── Identity leg (owner-baseline, when committed) ───────────────────────── | COMMENT |
| MEDIUM | .github/actions/bump-plugin-shas/scripts/bump.sh | 532 | # ============================================================================ | COMMENT |
| MEDIUM | .github/actions/bump-plugin-shas/scripts/bump.sh | 534 | # ============================================================================ | COMMENT |
| MEDIUM | .github/actions/bump-plugin-shas/scripts/bump.sh | 589 | # ────────────────────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/actions/bump-plugin-shas/scripts/bump.sh | 593 | # ────────────────────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/actions/bump-plugin-shas/scripts/bump.sh | 664 | # ────────────────────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/actions/bump-plugin-shas/scripts/bump.sh | 667 | # ────────────────────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/actions/owner-liveness-sweep/test-sweep.sh | 14 | # ── gh shim ────────────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/actions/owner-liveness-sweep/test-sweep.sh | 40 | # ── fixtures ───────────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/actions/owner-liveness-sweep/scripts/sweep.sh | 60 | # ── 1. Extract external github.com sources → owners + repos ───────────────── | COMMENT |
| MEDIUM | .github/actions/owner-liveness-sweep/scripts/sweep.sh | 109 | # ── 2. Batched GraphQL resolution ─────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/actions/owner-liveness-sweep/scripts/sweep.sh | 164 | # ── 3. Classify ───────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/actions/owner-liveness-sweep/scripts/sweep.sh | 210 | # ── 4. Step summary ───────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/actions/owner-liveness-sweep/scripts/sweep.sh | 248 | # ── 5. Mode tails ─────────────────────────────────────────────────────────── | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | .github/freeze-shas.txt | 1 | # freeze-shas — marketplace entry names held at their CURRENT source.sha | COMMENT |
| LOW | .github/workflows/owner-liveness-sweep.yml | 1 | name: Owner Liveness Sweep | COMMENT |
| LOW | .github/workflows/bump-plugin-shas.yml | 1 | name: Bump Plugin SHAs | COMMENT |
| LOW | .github/workflows/bump-plugin-shas.yml | 81 | id: bump | COMMENT |
| LOW | .github/actions/bump-plugin-shas/test-bump.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | .github/actions/bump-plugin-shas/test-bump.sh | 341 | # cases above — they need `gh api`, `git ls-remote`, and (for the stale-entry | COMMENT |
| LOW | .github/actions/bump-plugin-shas/test-bump-manifest.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | .github/actions/bump-plugin-shas/test-bump-manifest.sh | 201 | # @base64d is jq 1.6+. CI (ubuntu) ships 1.6+; the guard only matters for a dev on an | COMMENT |
| LOW | .github/actions/bump-plugin-shas/scripts/bump.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | .github/actions/bump-plugin-shas/scripts/bump.sh | 41 | # latest published RELEASE's commit instead of upstream HEAD. Absent/empty | COMMENT |
| LOW | .github/actions/bump-plugin-shas/scripts/bump.sh | 121 | COMMENT | |
| LOW | .github/actions/bump-plugin-shas/scripts/bump.sh | 221 | done | COMMENT |
| LOW | .github/actions/bump-plugin-shas/scripts/bump.sh | 321 | # API and require the canonical full_name to still match: | COMMENT |
| LOW | .github/actions/bump-plugin-shas/scripts/bump.sh | 361 | fi | COMMENT |
| LOW | .github/actions/validate-plugins/action.yml | 141 | # intermittently stalls or is skipped (npm --omit=optional, some pnpm | COMMENT |
| LOW | …ons/validate-plugins/scripts/11-validate-invariants.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | …/actions/validate-plugins/scripts/00-detect-changes.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | .github/actions/validate-plugins/lib/common.sh | 121 | return 1 | COMMENT |
| LOW | .github/actions/validate-plugins/lib/common.sh | 141 | # relaxes; any other value, incl. unset/true, requires a real manifest). | COMMENT |
| LOW | .github/actions/scan-plugins/test-pin-check.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | …ithub/actions/scan-plugins/scripts/static-pin-check.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | .github/actions/scan-plugins/lib/pin-check.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | .github/actions/scan-plugins/lib/pin-check.sh | 21 | # pinned — npm `pkg@1.2.3` (digit-led exact; prerelease/build metadata ok); | COMMENT |
| LOW | .github/actions/scan-plugins/lib/pin-check.sh | 41 | # PROVENANCE / KEEP IN SYNC: this is a faithful extract of | COMMENT |
| LOW | .github/actions/scan-plugins/lib/pin-check.sh | 61 | # server. `bare` rows are raw — refine with pin_check_refine_bare. | COMMENT |
| LOW | .github/actions/scan-plugins/lib/targets.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | .github/actions/owner-liveness-sweep/test-sweep.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | .github/actions/owner-liveness-sweep/scripts/sweep.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | .github/actions/owner-liveness-sweep/scripts/sweep.sh | 21 | # resolves at all (deleted or made private). | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | tres-finance-plugin/skills/tres-onboarding/SKILL.md | 76 | ### Step 1: Upload Wallets | COMMENT |
| LOW | tres-finance-plugin/skills/tres-onboarding/SKILL.md | 87 | ### Step 2: Data Collection (Commit) | COMMENT |
| LOW | tres-finance-plugin/skills/tres-onboarding/SKILL.md | 99 | ### Step 3: Validate Balances | COMMENT |
| LOW | tres-finance-plugin/skills/tres-onboarding/SKILL.md | 110 | ### Step 4: Reconciliation | COMMENT |
| LOW | tres-finance-plugin/skills/tres-onboarding/SKILL.md | 121 | ### Step 5: Cost Basis | COMMENT |
| LOW | tres-finance-plugin/skills/tres-onboarding/SKILL.md | 134 | ### Step 6: Export Unidentified Addresses | COMMENT |
| LOW | tres-finance-plugin/skills/tres-onboarding/SKILL.md | 151 | ### Step 7: Import Contacts | COMMENT |
| LOW | tres-finance-plugin/skills/tres-onboarding/SKILL.md | 162 | ### Step 8: Rollup Rules | COMMENT |
| LOW | …-plugin/skills/tres-asc845-swap-reprice-skill/SKILL.md | 44 | ### Step 1: Gather Parameters | COMMENT |
| LOW | …-plugin/skills/tres-asc845-swap-reprice-skill/SKILL.md | 55 | ### Step 2: Query Subtransactions | COMMENT |
| LOW | …-plugin/skills/tres-asc845-swap-reprice-skill/SKILL.md | 82 | ### Step 3: Run the Orchestrator Script | COMMENT |
| LOW | …-plugin/skills/tres-asc845-swap-reprice-skill/SKILL.md | 103 | ### Step 4: Repricing Logic (ASC 845) | COMMENT |
| LOW | …-plugin/skills/tres-asc845-swap-reprice-skill/SKILL.md | 160 | ### Step 5: Preview the Reprice Plan | COMMENT |
| LOW | …-plugin/skills/tres-asc845-swap-reprice-skill/SKILL.md | 179 | ### Step 6: Execute (with user confirmation) | COMMENT |
| LOW | …-plugin/skills/tres-asc845-swap-reprice-skill/SKILL.md | 205 | ### Step 7: Verify | COMMENT |
| LOW | …es-finance-plugin/skills/tres-report-analyzer/SKILL.md | 16 | ## Step 1: Identify the report type | COMMENT |
| LOW | …es-finance-plugin/skills/tres-report-analyzer/SKILL.md | 43 | ## Step 2: Run the analysis | COMMENT |
| LOW | …es-finance-plugin/skills/tres-report-analyzer/SKILL.md | 89 | ## Step 3: Present findings | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …res-asc845-swap-reprice-skill/scripts/reprice_swaps.py | 141 | CODE | |
| LOW | …res-asc845-swap-reprice-skill/scripts/reprice_swaps.py | 157 | CODE | |
| LOW | …n/skills/tres-report-create/tests/run_report_matrix.py | 251 | CODE | |
| LOW | …/skills/tres-report-analyzer/scripts/analyze_report.py | 26 | CODE | |
| LOW | …/skills/tres-report-analyzer/scripts/analyze_report.py | 144 | CODE | |
| LOW | …/skills/tres-report-analyzer/scripts/analyze_report.py | 278 | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …c845-swap-reprice-skill/scripts/orchestrate_reprice.py | 36 | def generate_graphql_mutations(plan, batch_size=50): | CODE |
| LOW | …c845-swap-reprice-skill/scripts/orchestrate_reprice.py | 53 | def generate_execution_script(plan, output_path): | CODE |
| LOW | …/skills/tres-report-analyzer/scripts/analyze_report.py | 144 | def analyze_reconciliation_ledger(wb): | CODE |
| LOW | …/skills/tres-report-analyzer/scripts/analyze_report.py | 237 | def analyze_asset_roll_forward(wb): | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | tres-finance-plugin/README.md | 26 | │ ├── tres-onboarding/ # Full entity onboarding (orchestrates sub-skills) | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | …n/skills/tres-report-create/tests/run_report_matrix.py | 334 | except Exception as exc: # noqa: BLE001 - harness records every failure | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …/skills/tres-report-analyzer/scripts/analyze_report.py | 33 | # Check if first row looks like a pivot header (single value like "Values") | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …n/skills/tres-report-create/tests/run_report_matrix.py | 334 | except Exception as exc: # noqa: BLE001 - harness records every failure | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …n/skills/tres-report-create/tests/run_report_matrix.py | 24 | CODE |