envfix
A zero-dependency environment config diagnostic tool for Node.js that compares env files and automatically fills in missing entries.
About envfix
envfix is an environment configuration diagnostic tool for Node.js projects. It has zero dependencies and is easy to wire into CI. It compares .env against .env.example item by item to quickly find missing or empty variables, detects duplicate and malformed declarations, and also checks whether .env is safely gitignored. When fixing, missing keys are appended to .env and existing lines and values are left untouched; it can also generate or sync .env.example without leaking secrets. The doctor command further assesses whether the environment configuration is healthy, consistent, and secure; in CI it exits with code 1 when variables are missing or empty, helping teams catch configuration drift before it reaches production.
Best for
Best use cases
Verify the local .env after cloning a project and automatically fill in missing variables
Catch missing or empty variables in CI pipelines to keep configuration drift out of production
Generate and sync .env.example for teams or open source projects without leaking real secrets
Run the doctor command for a full health, consistency, and security check of a project's environment configuration
Features
Config comparison check
Compares .env and .env.example item by item to find missing or empty variables, and detects duplicate and malformed declarations.
In-depth doctor checkup
Answers broader questions than the basic check: is the project's environment configuration healthy, consistent, and secure.
Append-only safe fixes
Missing keys are appended to .env; existing lines and values are never modified.
Secret and repository safety
Generates or syncs .env.example without leaking secrets, and checks whether .env is safely gitignored.
Pros
- Zero dependencies, lightweight to install and easy to use in CI
- Append-only fixes that leave existing lines and values untouched
- By default does not output environment variable values to the terminal, JSON, or CI annotations, reducing leak risks
- Exits with code 1 when variables are missing or empty, so pipelines can block immediately