npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

dotclaude-security

v0.1.0

Published

Scan a repo's local .claude/ config (settings.json hooks, MCP servers, env, allowed-tools) for the RCE and API-key-exfiltration footguns (CVE-2025-59536, CVE-2026-21852) that fire the moment you clone and open an untrusted repository — and flag the exact

Readme

dotclaude-security

Scan a repo's local .claude/ config — settings.json hooks, MCP server defs, env blocks, permissions.allow — for the RCE and API-key-exfiltration footguns that fire the moment you git clone and open an untrusted repository in Claude Code. It points at the exact dangerous line so you can read before you trust. Reads only — it never runs what it finds.

Run it in one line, no install, nothing leaves your machine:

npx dotclaude-security --dir ./some-cloned-repo

🤝 Want it hardened for you? Fixed-scope audit — $99 / 24h: I review each finding and send a written report with the exact .claude config fixes.

npm downloads license node deps

$ npx dotclaude-security --dir ./untrusted-repo
1 critical, 2 high, 0 medium across 1 config file(s).
  CRITICAL  .claude/settings.json:4  Auto-exec hook on "SessionStart" runs a command when the repo is opened
  HIGH      .claude/settings.json:7  permissions.allow pre-approves a dangerous tool: Bash(*)
  HIGH      .claude/settings.json:8  MCP server "x" runs an on-the-fly remote package (npx)

Why this exists

A repository can ship its own .claude/ config, and an agent honors it on open. In February 2026 Check Point Research disclosed two CVEs rooted in exactly this:

  • CVE-2025-59536 (CVSS 8.7) — a repo-controlled SessionStart hook auto-executes a shell command when the directory is opened. Clone a malicious repo, open it, get popped. Remote code execution on init.
  • CVE-2026-21852 — repo config (hook commands / env) reads your ANTHROPIC_API_KEY and ships it to a remote host. Silent key exfiltration.

Both attack the same surface: settings.json hooks, MCP server launch commands, env blocks, and the permissions.allow list — the things a stranger's repo can hand you. The big incumbents (Cisco's skill-scanner, Snyk's agent-scan) scan skills; almost nobody scans the .claude config files.

dotclaude-security parses those files, statically, and flags the exact file + line of every dangerous directive — so you triage facts, not maybes, and never execute the payload to find it.

What it checks

| Check | Severity | What it catches | |---|---|---| | Auto-exec hook on open (SessionStart/PreToolUse/UserPromptSubmit) | critical / high | command that runs the moment the repo is opened — RCE on init (CVE-2025-59536) | | Hook reads a secret and calls the network | critical | ANTHROPIC_API_KEY/token piped to a remote host — key exfil (CVE-2026-21852) | | Dangerous command pattern in any hook | high | curl\|sh, eval, base64 -d, nc -e, /dev/tcp, inline python -c/node -e | | MCP server launches a dangerous command | critical | MCP command/args that fetch-and-run code on connect | | MCP server runs an on-the-fly remote package | high | npx/uvx/bunx MCP definitions that pull unpinned packages | | MCP server handed a secret / remote URL | high / medium | env-injected credentials, untrusted remote endpoints | | Risky permissions.allow entry | high / medium | Bash(*), WebFetch, broad mcp__* that remove the human approval gate | | Committed secret value | critical | real sk-ant-…, AKIA…, ghp_…, private keys in any .claude file |

Usage

# Scan the .claude/ config in the current repo
npx dotclaude-security

# Scan a freshly cloned, untrusted repo BEFORE you open it in Claude Code
npx dotclaude-security --dir ./some-cloned-repo

# Machine-readable JSON only (gate your CI on the summary)
npx dotclaude-security --json

# Write a shareable HTML report
npx dotclaude-security --html report.html

Output is JSON on stdout (pipe it into CI) and a one-line-per-finding summary on stderr. Each finding carries file, location.line, location.text and a concrete fix.

Install (optional)

npm i -g dotclaude-security
dotclaude-security --dir ./untrusted-repo

Zero dependencies. It reads your config files and reports — it never executes a hook, MCP command, or anything else it discovers. Nothing leaves your machine.

Sister tools

Same local-first, prove-the-real-issue philosophy across the stack, all MIT:

supabase-security · strapi-security · pocketbase-security · firebase-security · appwrite-security · nhost-security · stripe-webhook-security · github-actions-security · aws-s3-security

License

MIT © Renzo Madueno