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

@ccpluginizer/ccpluginizer

v0.7.0

Published

CLI for pluginizing non-plugin Claude Code repos

Downloads

278

Readme

@ccpluginizer/ccpluginizer

CLI for pluginizing non-plugin Claude Code repos.

Generate and validate ccpluginizer marketplace entries from any GitHub repo with Claude Code-compatible content (skills, agents, commands, hooks, MCP servers).

Install

ccpluginizer is Bun-first. Two co-equal ways to run it — pick whichever fits.

Bun (light)

bun add -g @ccpluginizer/ccpluginizer
# or one-shot, no install:
bunx @ccpluginizer/ccpluginizer scan <owner/repo>

Don't have Bun? curl -fsSL https://bun.sh/install | bash.

Native binary (self-contained)

Download the binary for your platform from GitHub Releases — no runtime required (the Bun runtime is embedded; ~60 MB):

| Platform | Asset | |---|---| | macOS (Apple Silicon) | ccpluginizer-darwin-arm64 | | Linux x64 | ccpluginizer-linux-x64 | | Linux arm64 | ccpluginizer-linux-arm64 | | Windows x64 | ccpluginizer-windows-x64.exe |

# macOS / Linux — mark executable, then run:
chmod +x ccpluginizer-<os>-<arch>
# macOS only: clear the Gatekeeper quarantine flag first (see the macOS note below)
./ccpluginizer-<os>-<arch> scan <owner/repo>

# Windows (PowerShell or cmd) — run the .exe directly:
.\ccpluginizer-windows-x64.exe scan <owner/repo>

macOS: the binaries are unsigned, so Gatekeeper quarantines them. Clear it before running: xattr -c ./ccpluginizer-darwin-arm64. Windows: the unsigned .exe triggers SmartScreen — choose More info → Run anyway.

Windows: ccpluginizer's bin/ccpluginizer launcher is a POSIX shell script that doesn't run natively on Windows, so prefer this native binary over the Bun path.

Node is not supported. The CLI uses Bun-native APIs; running it under npm/npx (Node) refuses to start with a pointer to the two paths above.

Usage

ccpluginizer scan <owner/repo>     # Generate a marketplace entry
ccpluginizer validate <entry.json> # Validate an entry against the schema

To add a repo to the catalog, run scan, commit the JSON to entries/<name>.json in the catalog repo, and open a PR. See the catalog's CONTRIBUTING.md.

<owner/repo> accepts either GitHub shorthand (elysiajs/skills) or a full URL (https://github.com/elysiajs/skills).

How it works

ccpluginizer detects skills, agents, commands, hooks, and MCP servers in the source repo, then synthesizes a marketplace entry that uses Claude Code's strict: false mode to point at the source. The catalog never holds a copy of the source itself.

Detection runs in three passes. The first looks at convention paths like .claude/skills/, .claude/agents/, and .claude/commands/. The second reads .claude-plugin/manifest.json or a .ccpluginizer.json marker file if the repo has one. The third is a heuristic fallback for repos that follow neither convention. It scans for SKILL.md files with YAML frontmatter, commands/*.md, and similar patterns.

Repository

Source, issues, and contribution guide: https://github.com/lifebugz/ccpluginizer

License

MIT