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

@gkorner/envguard

v1.0.0

Published

Validate .env files against schema. No more undefined in production.

Readme

envguard

Validate .env files against schema. No more undefined in production.

npm license

Documentation · Report Bug · All Tools

Install

npm install -g envguard

Usage

# validate .env against .env.schema
envguard
# ✓ valid. 12 variables checked.

# generate schema from existing .env
envguard init
# ✓ schema generated: .env.schema

# compare two env files
envguard diff .env .env.prod
# only in .env.prod:
#   + PROD_API_KEY
# different values:
#   ~ DEBUG

# list all variables
envguard list

Schema Format

Create .env.schema:

# Required variables (no default)
DATABASE_URL
API_KEY

# With type validation
PORT=port
DEBUG=boolean
API_URL=url
ADMIN_EMAIL=email
MAX_CONNECTIONS=number

# Optional variables (with ?)
OPTIONAL_VAR?
ANALYTICS_ID?

# With default value
NODE_ENV=string:development
TIMEOUT=number:30

Types

| Type | Description | Example | |------|-------------|---------| | string | Any string (default) | hello | | number | Numeric value | 42, 3.14 | | boolean | true/false/1/0/yes/no | true | | url | Valid URL | https://example.com | | email | Valid email | [email protected] | | port | Port number (1-65535) | 3000 |

Commands

| Command | Alias | Description | |---------|-------|-------------| | check | c | Validate .env against schema (default) | | diff | d | Compare two .env files | | init | i | Generate schema from .env | | list | l | List all variables |

Options

| Flag | Description | Default | |------|-------------|---------| | -e, --env | Path to .env file | .env | | -s, --schema | Path to schema file | .env.schema | | -o, --output | Output file for init | .env.schema | | --strict | Fail on extra variables | false | | --quiet | Only output errors | false |

CI/CD Integration

# GitHub Actions
- name: Validate environment
  run: envguard check --strict

# Pre-commit hook
envguard check || exit 1

More tools from rtfm.codes

View all tools →

License

MIT © rtfm.codes


rtfm.codes — it works. the docs explain why.