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

quickenv-check

v1.0.1

Published

Lightning-fast .env file validator. Compare .env vs .env.example, find missing vars, detect leaked secrets, and enforce env hygiene in CI/CD.

Readme

quickenv-check

Lightning-fast .env file validator. Zero dependencies.

Compare .env vs .env.example, find missing variables, detect leaked secrets, and enforce env hygiene in CI/CD pipelines.

Why?

Every project has .env files. Most have bugs in them:

  • Missing variables that crash at runtime
  • Empty values nobody noticed
  • Real API keys committed by accident
  • Placeholder values left in production

quickenv catches all of these in milliseconds, with zero dependencies.

Install

npm install -g quickenv-check

Or use in your project:

npm install --save-dev quickenv-check

Usage

# Validate .env against .env.example
quickenv

# CI mode (strict, fails on warnings)
quickenv --ci

# JSON output for automation
quickenv --json

# Check a specific env file
quickenv -e .env.staging -x .env.example

# Skip secret detection
quickenv --no-secrets

What It Checks

| Check | Description | |-------|-------------| | Missing variables | In .env.example but not in .env | | Empty values | Defined but blank | | Placeholder values | your_api_key, changeme, xxx, etc. | | Leaked secrets | OpenAI, GitHub, AWS, Stripe, Slack tokens, private keys | | Extra variables | In .env but not in .env.example |

Secret Detection

Detects 18+ secret patterns including:

  • OpenAI API keys (sk-...)
  • GitHub tokens (ghp_, gho_, ghs_)
  • AWS access keys (AKIA...)
  • Stripe keys (sk_live_, pk_live_)
  • Slack tokens (xoxb-, xoxp-)
  • Telegram bot tokens
  • npm/PyPI tokens
  • Private keys (PEM format)
  • And more...

CI/CD Integration

GitHub Actions

- name: Validate env
  run: npx quickenv-check --ci

Pre-commit Hook

{
  "scripts": {
    "precommit": "quickenv --strict"
  }
}

Options

| Flag | Description | |------|-------------| | -e, --env <path> | Path to .env file (default: .env) | | -x, --example <path> | Path to example file (auto-detected) | | --strict | Treat warnings as errors | | --ci | CI mode (strict + non-zero exit) | | --no-secrets | Skip secret detection | | --json | Machine-readable JSON output | | -q, --quiet | No output, just exit code |

Programmatic API

const { parseEnvFile, validate } = require('quickenv-check');

const env = parseEnvFile(envContent);
const example = parseEnvFile(exampleContent);
const result = validate(env, example, { checkSecrets: true });

console.log(result.ok);      // true/false
console.log(result.errors);  // missing vars
console.log(result.secrets);  // detected secrets

Exit Codes

| Code | Meaning | |------|---------| | 0 | All checks passed | | 1 | Errors found (or warnings in strict mode) | | 2 | Runtime error |

License

MIT


Built with speed by AI Hustle Lab as part of the 100 Days of AI Hustle challenge.