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

getdoorman

v2.0.1

Published

10 security checks. Zero false positives. Ship with confidence.

Readme

Doorman

Ship your code with confidence.

10 security checks. Zero false positives. 3 seconds. Free.

Quick Start

Tell your AI:

run npx getdoorman

Or run it directly:

npx getdoorman

What It Checks

✅ Leaked API Keys (35+ providers)
✅ .env File Safe
❌ SQL Injection — src/api/search.ts:42
✅ No Crashes Waiting
✅ No Hardcoded Secrets
✅ No Code Execution Risk
✅ No Sensitive Data in Logs
✅ No Debug Code
✅ Database Secure
✅ Safe Dependencies

Doorman: 9/10 checks passed. 1 issue found.
→ SQL Injection: Query built with user input in src/api/search.ts:42

Tell your AI: "fix the issues Doorman found"

The 10 Checks

| Check | What it catches | |-------|----------------| | 🔑 Leaked API Keys | Stripe, OpenAI, AWS, Anthropic, GitHub, and 30+ more | | 📄 .env Exposed | .env not in .gitignore | | 💉 SQL Injection | Queries built with user input | | 💥 Production Crashes | API routes without error handling | | 🔒 Hardcoded Secrets | Passwords and tokens in source code | | ⚠️ Code Execution | eval() with dynamic input | | 📋 Sensitive Logs | Passwords or tokens in console.log | | 🐛 Debug Code | console.log left in production | | 🗄️ Database Security | MongoDB without auth, server on 0.0.0.0 | | 📦 Bad Packages | Known compromised npm packages |

How It Works

  1. Tell your AI to run it — or run npx getdoorman yourself
  2. Doorman scans your code in ~3 seconds
  3. Green check = safe. Red X = here's where to look
  4. Tell your AI: "fix the issues Doorman found"

After the first run, Doorman checks automatically every time your AI writes code.

Options

npx getdoorman              # check current directory
npx getdoorman ./src        # check specific path
npx getdoorman --json       # output as JSON
npx getdoorman --ci         # exit code 1 if issues found

Privacy

Your code never leaves your machine. Doorman runs 100% locally. No cloud. No accounts. No telemetry.

License

MIT

Links