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 🙏

© 2025 – Pkg Stats / Ryan Hefner

npm-ci-guard

v1.0.0

Published

Guard your npm CI by catching lockfile and npm-version issues before they hit main.

Downloads

137

Readme

npm CI Guard

Catch npm ci / lockfile problems before they break your CI.

npm-ci-guard is a small CLI + GitHub Action that checks:

  • Is package-lock.json consistent with package.json?
  • Are we using an npm version compatible with this lockfile?
  • Did someone run npm install locally but forget to commit the lockfile?

Status

MVP / experimental - focused on a single command: npm-ci-guard check.

Why?

Typical pain:

  • npm ci suddenly breaks in CI after a Node / npm upgrade.
  • npm ci fails while npm install worked locally.
  • You pinned npm versions but lockfile behaviour is still flaky.

Job to be done:

Before I merge or upgrade anything, I want to know if our package-lock.json will install deterministically in CI (and across machines), and if not, what to fix.

Install / Usage

You can run it via npx (no global install needed):

npx npm-ci-guard check