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

stackprobe

v0.1.2

Published

Audit your JS/TS project before it becomes a problem

Downloads

218

Readme

stackprobe — A CLI that audits your project and tells you what's wrong, outdated, or missing before it becomes a problem.

The real problem it solves: Developers constantly discover issues the hard way — a .env variable missing in production, a package 3 major versions behind with breaking changes, no license file, mismatched Node engine versions, circular dependencies nobody noticed. stackprobe catches all of this before you ship.

You run one command in any Node/JS project:

npx stackprobe audit

And you get a clean, readable report like:

Dependencies
   lodash is 4 major versions behind (installed: 1.x, latest: 4.x)
   axios has a known CVE — upgrade to 1.6.8+

Environment
   DATABASE_URL is used in code but missing from .env.example
   JWT_SECRET has no fallback and is not validated at startup

License
   MIT license found

Engine
   Your code uses Array.at() — not supported in Node < 16.6
   package.json specifies "node >= 14"  ← conflict