env-inspector

Analyze, validate, and secure your .env files.

Why?

• Accidentally committing .env files
• Missing environment variables causing runtime errors
• Weak secrets and default passwords in production
• No easy way to diff .env vs .env.example

Install

npx env-inspector <command>

Or install globally:

npm install -g env-inspector

Commands

diff - Compare .env files

Shows missing and extra variables between .env and .env.example.

env-inspector diff
env-inspector diff --env .env.local --example .env.example

validate - Check variable formats

Auto-detects and validates URLs, ports, emails, booleans, and numbers.

env-inspector validate
env-inspector validate --env .env.production

security - Detect weak secrets

Finds common default passwords, short secrets, and sequential patterns.

env-inspector security
env-inspector security --env .env.production

generate - Create .env from template

Generates an empty .env file from .env.example with all keys and empty values.

env-inspector generate
env-inspector generate --example .env.template --env .env.local

CI/CD Integration

Add to your pipeline to catch issues early:

# GitHub Actions
- name: Check env files
  run: |
    npx env-inspector diff
    npx env-inspector validate
    npx env-inspector security

License

MIT