A lightweight, zero-config CLI that catches missing variables, empty values, and configuration drift. Stop environment issues from breaking production.
npm install -g envsane
They seem simple until they break production at 2am. Here's what typically goes wrong:
Someone adds NEW_API_KEY to production but forgets to update the example file. New developers onboard without it.
The key exists, but the value is blank. Your app starts fine, then mysteriously fails when it tries to connect to the database or external service.
DB_URL vs db_url
Same variable twice. Last wins.
Production has 47 variables, staging has 42, development has 38. Which ones are actually needed? Good luck figuring that out without proper tooling.
What does FEATURE_FLAG_XYZ do? What's a valid value? Open the code and hope someone left a comment.
envsane does exactly what you need and nothing more. No accounts, no dashboards, no complexity.
Compare your .env file against .env.example to catch
issues before they become problems. The command treats your example file as the
source of truth and reports any deviations.
See exactly what's different between any two environment files. Perfect for debugging why staging works but production doesn't, or ensuring parity across environments.
Get instant documentation for any environment variable. envsane reads
comments from your .env.example file and displays them in a
clean, readable format with type inference.
No configuration files. No setup wizards. Just install and run.
npm install -g envsane
Or use npx: npx envsane check
cd your-project
Make sure you have a .env.example file
envsane check
Exit code 0 = success, 1 = issues found
Add to your build process to catch missing variables before deployment reaches production.
envsane check --strict
New developers can instantly validate their local setup matches project requirements.
envsane check
Compare production vs staging vs dev to understand configuration differences.
envsane diff .env.prod .env.staging
Quickly understand what a variable does without digging through codebases.
envsane explain API_KEY
Install envsane and start validating your environment files today. It takes 30 seconds.
npm install -g envsane