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

claudepluginhub

v0.10.0

Published

Install Claude Code components from ClaudePluginHub

Downloads

13,574

Readme

claudepluginhub

Install Claude Code plugins from ClaudePluginHub and GitHub with a single command.

Usage

# GitHub plugin or marketplace
npx claudepluginhub owner/repo

# ClaudePluginHub collection
npx claudepluginhub u/<userId>/<slug>

# ClaudePluginHub plugin by slug
npx claudepluginhub p/<slug>

# Full URL
npx claudepluginhub https://claudepluginhub.com/api/user-plugins/<userId>/<slug>/marketplace.json

# Recommend plugins for the current project
npx claudepluginhub recommend

Identifier types

owner/repo (GitHub)

Installs a plugin or marketplace directly from a GitHub repository using Claude Code's native plugin system.

  • Marketplace repos (.claude-plugin/marketplace.json): Adds the marketplace and installs selected plugins via claude plugin marketplace add and claude plugin install.
  • Plugin repos (with or without .claude-plugin/plugin.json): Creates a local wrapper marketplace, then installs via Claude Code.

u/<userId>/<slug> (ClaudePluginHub)

Installs from a ClaudePluginHub user-curated collection. Components are downloaded directly and tracked in a lock file.

p/<slug> (ClaudePluginHub)

Installs a single ClaudePluginHub plugin by its site slug via a wrapper marketplace (requires Claude Code).

Full URL

Same as u/ form but with the full marketplace JSON URL.

Commands

npx claudepluginhub <identifier>        Install from a source
npx claudepluginhub add <identifier>    Same as above
npx claudepluginhub update [identifier] Update (u/ collections only)
npx claudepluginhub list                List (u/ collections only)
npx claudepluginhub remove <identifier> Remove
npx claudepluginhub recommend           Recommend plugins for the current project

Recommend

Run npx claudepluginhub recommend from a project root to get plugin recommendations grouped by each detected stack ("For Next.js:", "For PostgreSQL:", …) — no account, no setup.

npx claudepluginhub recommend             # top picks per detected stack
npx claudepluginhub recommend --limit 6   # picks per stack (1-50, default 4)
npx claudepluginhub recommend --json      # raw JSON, pipeable

Detection reads dependency names from package.json, requirements.txt, pyproject.toml, Cargo.toml, and go.mod, plus which known config files exist (e.g. next.config.*, tailwind.config.*). Privacy: only dependency names and allowlisted config-filename prefixes are sent — never file contents, never arbitrary filenames.

Examples

# Install a specific plugin from a marketplace repo
npx claudepluginhub vercel/next.js --plugin cache-components

Options

| Option | Description | |--------|-------------| | --plugin <name> | Install a specific plugin from a marketplace repo | | --yes, -y | Skip prompts (install all, project scope) | | --scope <scope> | Set scope: user, project (default), local | | --limit <n> | recommend only: picks per detected stack (1-50, default 4) | | --json | recommend only: raw JSON output | | -h, --help | Show help |

Lifecycle differences

| Feature | owner/repo | u/ collections | |---------|-------------|------------------| | Install | claude plugin commands | Direct download | | List | claude plugin list | npx claudepluginhub list | | Update | claude plugin update | npx claudepluginhub update | | Remove | npx claudepluginhub remove owner/repo --scope <scope> (standalone) or claude plugin commands (marketplace) | npx claudepluginhub remove |

Standalone wrapper

When installing a standalone plugin via owner/repo, a local wrapper marketplace is created:

| Scope | Wrapper path | |-------|-------------| | user | ~/.claude/.cpd-wrappers/<owner>-<repo>-user/ | | project | .claude/.cpd-wrappers/<owner>-<repo>-project/ | | local | ~/.claude/.cpd-wrappers/<owner>-<repo>-local-<cwd-hash>/ |

Note: local scope wrappers are stored under ~/.claude/ and are tied to the working directory where they were installed. Running npx claudepluginhub remove owner/repo --scope local for a local install must be done from the same project directory.

Requirements

  • Node.js 18+
  • Claude Code installed and available in PATH (required for owner/repo installs)