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

@facetlayer/npm-status

v0.1.1

Published

CLI tool to check NPM publish status and detect unpublished changes

Readme

@facetlayer/npm-status

CLI tool to check NPM publish status and detect unpublished changes.

Installation

pnpm add -D @facetlayer/npm-status

Usage

Status Command

Check the publish status of a package:

cd my-package
npm-status status

Output:

Package: @facetlayer/my-package
Local version: 1.2.0
NPM version: 1.1.0
Last published: 2024-01-15T10:30:00.000Z

Issues:
  - Version differs: local=1.2.0, npm=1.1.0
  - Has 3 commits since last publish

Commits since last publish:
  abc1234 fix: resolve edge case in parser
  def5678 feat: add new validation option
  ghi9012 docs: update readme

JSON Output

For scripting, use the --json flag:

npm-status status --json

What It Checks

The status command compares your local package with NPM:

  • Version difference: Compares local package.json version with the published NPM version
  • Uncommitted changes: Uses git status to detect uncommitted changes in the current directory
  • Unpublished commits: Uses git log to find commits made after the last NPM publish time

This works correctly in monorepos by filtering git operations to only the current directory.

License

MIT