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

@kangmomin/cpm

v0.0.2

Published

Prototype CLI for managing Codex-compatible plugins.

Readme

cpm

cpm is a prototype CLI for managing Codex-compatible plugins with a Claude Code marketplace-compatible source model.

Install

npm install -g @kangmomin/cpm
cpm scope get

Scope Model

cpm supports three npm-like config scopes:

  • user: machine-wide defaults stored at ~/.cpm/config.toml
  • project: shared project config stored at <project>/.cpm/plugins.toml
  • local: checkout-local overrides stored at <project>/.cpm/local.toml

Effective scope resolution is:

local > project > user > builtin(project)

Commands

npm install
npm start -- scope get
npm start -- scope paths
npm start -- scope set user
npm start -- scope set project
npm start -- scope set local

Use --project DIR to target a specific project directory:

npm start -- scope set project --project /path/to/project
npm start -- scope get --project /path/to/project

Use --location when you want to write a default scope into a different config layer:

npm start -- scope set project --location user
npm start -- scope set local --location project

local config is intentionally ignored by git.

Install as a CLI

For local development:

npm link
cpm scope get

Or install from this checkout:

npm install -g .
cpm scope get

Publish to npm with:

npm publish

Run tests with:

npm test