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

leakgate

v0.2.0

Published

A last-second safety check that catches leaked secrets and private files before you publish your code.

Downloads

504

Readme

LeakGate 🛟

Catch leaked secrets and private files before you publish — in one command.

You build fast (especially with AI). LeakGate takes a last-second look at exactly the files you're about to publish and stops you if an API key, password, or private file is about to leak in public.

npx leakgate

Why

AI coding tools make it easy to ship fast — and easy to leak. A hardcoded key, a .env file, or a source map slips into your published package, and it's public forever. It has happened to solo devs and to big companies alike. LeakGate is the babysitter that checks the box before the door closes, so you can keep shipping fast without the fear.

The key difference from other scanners: it checks the real publish set — the exact files npm publish or python -m build would ship — not just your whole folder. Works on npm projects and Python (PyPI) projects.

Use it

npx leakgate            # scan the current project
npx leakgate ./my-app   # scan a specific folder

Exit code is 1 if anything serious is found, 0 if clean — so you can use it as a pre-publish guard or in CI.

Python (PyPI)

Point LeakGate at a Python project (one with pyproject.toml or setup.py) and it scans the real PyPI publish set — both the sdist (.tar.gz) and the wheel (.whl) — by building your package the same way twine upload would.

pip install build                # one-time — LeakGate uses it to see the real publish set
npx leakgate ./my-py-project

This matters because build backends like setuptools-scm silently include every git-tracked file in the sdist. A .env you forgot to untrack, or a .pypirc sitting next to your pyproject.toml, can end up on PyPI without you ever noticing. LeakGate builds the package, extracts both archives, and inspects every file inside — including auto-generated ones like PKG-INFO.

Run it automatically before every publish

"scripts": { "prepublishOnly": "npx leakgate" }

What it checks

Leaked secrets: AWS, Stripe, OpenAI, Anthropic, Google, GitHub, Slack keys; database URLs with passwords; private key blocks; hardcoded password = "..." values.

Dangerous files: .env, source maps, .git, private keys/certs, database dumps, .npmrc, .pypirc, credential files.

It ignores obvious placeholders (like your-api-key-here) and template files (.env.example, .env.sample, .env.template) so it doesn't cry wolf.

Roadmap

More languages · automatic continuous watching · one-click AI-ready fixes · team dashboard + auto-block.

License

MIT