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

@albertoarena/envaudit

v1.0.0

Published

Zero-dependency CLI to audit, compare and sync .env files

Readme

envaudit

Zero-dependency CLI to audit, compare and sync .env files.

Compares .env against .env.example, detects missing variables, undocumented variables, empty values, and possible secrets leaked into .env.example.

Documentation

Installation

# Install globally
npm install -g @albertoarena/envaudit

# Or run directly with npx
npx @albertoarena/envaudit check

Usage

Check (audit)

# Auto-detects .env and .env.example in current directory
envaudit check

# Custom paths
envaudit check --env .env.local --example .env.example

# CI mode — exits with code 1 if errors found
envaudit check --ci

Output categories:

  • Errors (✗): Missing variables, possible secrets in .env.example, unquoted values with spaces
  • Warnings (⚠): Undocumented variables, empty values

Diff

Compare any two env files:

envaudit diff .env.staging .env.production

Shows keys only in each file and keys with different values. Secret-looking values are masked.

Sync

Add missing keys between .env and .env.example:

# Preview changes
envaudit sync --dry-run

# Apply changes
envaudit sync

Doc

Generate markdown documentation of all env variables:

envaudit doc > ENV.md

Outputs a table grouped by prefix (DB_, APP_, AWS_, etc.) with columns: Variable, Required, Default, Group.

CI Integration

Add to your CI pipeline to catch env mismatches early:

# GitHub Actions
- name: Check env files
  run: npx @albertoarena/envaudit check --ci --no-color

# Skip empty value warnings (secrets injected at runtime)
- name: Check env files
  run: npx @albertoarena/envaudit check --ci --no-color --ignore-empty
# GitLab CI
check-env:
  script:
    - npx @albertoarena/envaudit check --ci --no-color

Options

| Flag | Description | |------|-------------| | --env <path> | Path to .env file (default: .env) | | --example <path> | Path to .env.example (default: .env.example) | | --ci | Exit with code 1 if errors found | | --ignore-empty | Skip empty value warnings (useful in CI) | | --dry-run | Show sync changes without writing | | --no-color | Disable colored output | | --help, -h | Show help | | --version, -v | Show version |

Requirements

  • Node.js >= 18
  • Zero npm dependencies

License

MIT