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

dotdoctor

v0.1.0

Published

The doctor for your .env files — like flutter doctor, but for environment variables.

Downloads

155

Readme

dotdoctor

The doctor for your .env files — like flutter doctor, but for environment variables.

dotdoctor reads your source code to find the environment variables it actually uses, parses your .env stack, and tells you which ones are missing, unused or invalid before the app starts. It scans JavaScript, TypeScript, Python, Go and Ruby.

$ npx dotdoctor check
dotdoctor v0.1.0 — scanned 5 files in 2ms

✗ DATABASE_URL   required by the code but not defined in any env file   src/db.ts:4
! LOG_LEVEL      not defined (optional — the code provides a fallback)   src/log.ts:3
✓ 8 other variables OK

1 error, 1 warning
→ add the missing variables to your env files, then re-run `dotdoctor check`

Exit codes: 0 clean, 1 problems found, 2 dotdoctor could not run.

Install

npm install --save-dev dotdoctor

This package is a launcher. The actual binary arrives through one of the platform packages below, picked automatically by npm via os/cpu and listed here as optionalDependencies:

@dotdoctor/darwin-arm64 · @dotdoctor/darwin-x64 · @dotdoctor/linux-arm64 · @dotdoctor/linux-x64 · @dotdoctor/win32-x64

If you install with --no-optional, no binary is installed and dotdoctor will tell you which package to add.

Programmatic use

const { execFileSync } = require("child_process");
const { binaryPath } = require("dotdoctor");

const report = JSON.parse(execFileSync(binaryPath(), ["check", "--json"]));

Documentation

Full docs, the env.schema.toml reference and the GitHub Actions recipe live in the repository README.

License

MIT