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

safe-audit

v0.0.1

Published

Reserved placeholder. Defensively published to hold the bare npm name `safe-audit` so it cannot be squatted. Not a functional package — do not depend on it.

Readme

safe-audit (reserved placeholder)

This package is not functional. It exists only to hold the bare npm name safe-audit so that name cannot be registered by a third party.

Why

An earlier version of the safe package-install gate built an audit command as npx --yes safe-audit package-audit … inside a sandbox. That name was never published by the gate's authors, so the fetch always failed harmlessly — but had anyone registered safe-audit on npm, the gate would have fetched and run their code. The gate no longer references this name; this placeholder holds it so the vector cannot be reopened.

Do not depend on this

It emits nothing to stdout, returns no verdict, and exits 0. If you were looking for a security auditing tool, this is not it.