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

@masterpack/cli

v0.1.0

Published

Set up MasterPack in your app: register, claim, and wire credentials — one command

Readme

@masterpack/cli

Set up MasterPack in your app — one command. MasterPack is a marketplace where subscribers pay one monthly fee and makers get paid from real usage of their app.

npx -y @masterpack/cli init \
  --name "My App" \
  --url "https://myapp.example" \
  --tagline "One line that sells it." \
  --description "At least 40 characters describing what the app does." \
  --category Productivity

The CLI prints what it's about to do, registers your app, gives you a claim link to open in your browser, waits until you've claimed it, then writes credentials into .env.local and makes sure that file is gitignored.

Your API key is never printed. It goes straight into the env file, and the terminal shows only a masked prefix. Pass --print if you'd rather see the credentials and have no files written.

Commands

| Command | What it does | |---------|--------------| | init | register the app, wait for the browser claim, write credentials | | config --redirect-uri <url> | register your OAuth callback URL(s) | | submit | run the automated listing checks and go live | | status | show the app's current listing state |

Useful flags: --print, --env-file <path>, --no-gitignore, --yes, --base <url> (self-hosted or staging), --help, --version.

What gets written

# --- MasterPack ---
MASTERPACK_APP_ID=…
MASTERPACK_API_KEY=…          # secret — never commit
MASTERPACK_TEST_CLIENT_ID=…   # sandbox: no subscription, no payouts
MASTERPACK_LIVE_CLIENT_ID=…   # production
# --- end MasterPack ---

Next.js and Vite projects also get a browser-visible copy (NEXT_PUBLIC_… / VITE_…), starting on the sandbox id.

Then integrate @masterpack/sdk: full guide at https://masterpack.app/docs/integrate.md

License

MIT