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

plugin-hunter

v1.1.1

Published

ph — Scan Claude Code / Codex CLI / Gemini CLI plugins for malicious hooks, poisoned SKILL.md, and MCP tool-poisoning *before* you install. Uses your local LLM CLI as the judge — no API key required.

Readme

plugin-hunter

Pre-install security scanner for AI coding-agent plugins

Scan Claude Code · Codex CLI · Gemini CLI plugins for malicious hooks, poisoned SKILL.md, and MCP tool-poisoning — before you install them. Uses your local LLM CLI as the judge, so no API key is required.

Full docs (English) · 한국어 문서 · GitHub


Install

Global install puts the ph binary on your PATH.

# npm
npm install -g plugin-hunter

# bun (recommended, faster)
bun add -g plugin-hunter

# pnpm
pnpm add -g plugin-hunter
ph --version
ph --help
ph lang             # show / change UI language (English default, auto-detects Korean from locale)

Requires Node 18+ or Bun 1.1+, and git on PATH.

CLI output, reports, and judge reasoning are bilingual (English / Korean). English is the default; ph lang ko or PH_LANG=ko switches to Korean.

No Node/Bun? Download a single binary from Releases (Bun runtime embedded, zero dependencies).


Prerequisite — one local LLM CLI

ph ships no model of its own. It calls whichever LLM CLI is already authenticated on your machine as the judge. You need at least one of:

command -v claude     # Claude Code CLI
command -v codex      # OpenAI Codex CLI
command -v gemini     # Gemini CLI

Install and sign in to one of them first (see their respective docs). No additional API key for ph.


Usage

Scan a plugin before installing it

# owner/repo shorthand
ph scan claude MoonDongmin/git-helper-pro-claude

# full GitHub URL
ph scan codex https://github.com/owner/repo

# pick whichever LLM CLI you have
ph scan gemini owner/repo

<judge> is one of claude, codex, gemini — the LLM CLI that will judge the plugin.

Exit codes (so you can chain it into CI / shell):

| Exit | Meaning | |---|---| | 0 | clean — safe to install | | 1 | unsafe — risk detected | | 2 | error — scan itself failed |

# install only if clean
ph scan claude owner/repo && plugin-install owner/repo

List plugins already installed

ph ls
# shows everything under ~/.claude/plugins and ~/.codex/{skills,rules,memories}

Re-scan / detect rug-pulls

ph remembers per-file SHA-256 of the last scan, so it can spot a plugin that was clean but got compromised later.

ph watch claude all              # re-scan every installed plugin
ph watch claude <plugin-name>    # re-scan one
ph watch claude all --quiet      # summary only — fits a Stop hook / cron

Scan history

ph history
ph history --limit 50
ph history --id <plugin-id>

State lives in ~/.ph/registry.json (last scan result, basis for rug-pull diff), ~/.ph/history.json (last 500 scans), and ~/.ph/config.json (user preferences such as lang).

UI language

ph lang                    # show effective + saved language
ph lang en | ph lang ko    # pin permanently
ph lang --reset            # back to auto-detect
ph --lang en <command>     # one-off override
PH_LANG=ko ph <command>    # shell-session override

Resolution priority: --lang flag → PH_LANG env → ~/.ph/config.json → system LANGen default. The judge prompt switches with the UI language so finding descriptions stay in the chosen language.


What it catches

| Vector | How it's caught | |---|---| | Hook RCE (curl ... \| sh, credential exfil) | LLM judge reads hook shell commands | | Skill / Agent / Command poisoning (malicious natural-language instructions) | LLM judge reads SKILL.md, agent files | | MCP Tool Poisoning (prompt injection inside tool descriptions) | LLM judge reads MCP tool schemas | | Eager-spawn MCP RCE (.mcp.json command runs a shell) | LLM judge evaluates manifest | | Obfuscation (base64 -d \| bash, split strings) | LLM judge reconstructs semantics | | Rug-pull (post-install compromise) | ph watch diffs SHA-256, re-judges changed files |

See the full docs for the detection pipeline, threat model, and demo.


License

MIT © MoonDongmin