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

@billyjacoby/pack-man

v0.0.3

Published

A simple CLI to set your package.json packageManager field.

Readme

Pack-Man

@billyjacoby/pack-man

A lightweight utility that automatically updates your project's packageManager field in package.json to match the package manager you're currently using.

Why?

  • Ensures consistency between your actual package manager and what's declared in package.json
  • Helps prevent accidental usage of wrong package managers in your project
  • Useful for teams to maintain consistent package manager usage
  • Zero dependencies

Usage

Run via npx in your project directory:

npx @billyjacoby/pack-man

The tool will:

  1. Detect which package manager you're using (npm, yarn, or pnpm) based on the lock file (todo: detect what command you're running with - pnpm dlx, yarn dlx, npx, etc.)
  2. Update the packageManager field in your package.json accordingly
  3. Use the correct version of the detected package manager

License

MIT

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.