evnx
CLI tool that validates, scans, and converts .env files for deployment targets.
Tested on Linux
Use it
Linux x86_64
pipx install evnx
pipx install evnx && evnx --version
Check that it works
evnx --versionThe output should contain “evnx 0.11.0”.
First thing to try
mkdir -p /tmp/evnxdemo && printf 'DEBUG=false\nPORT=3000\nDATABASE_URL=postgres://user:pass123@localhost:5432/mydb\nSECRET_KEY=supersecretkey1234567890abcdef\n' > /tmp/evnxdemo/.env && printf 'DEBUG=false\nPORT=3000\nDATABASE_URL=postgres://user:pass123@localhost:5432/mydb\nSECRET_KEY=supersecretkey1234567890abcdef\n' > /tmp/evnxdemo/.env.example && printf 'AKIAIOSFODNN7EXAMPLE\n' > /tmp/evnxdemo/leaked.txt && ls -la /tmp/evnxdemo && cat /tmp/evnxdemo/.envcd /tmp/evnxdemo && evnx validateIn a folder that has a .env file, run evnx validate to check it for problems.
What it does
- Check .env files for misconfigurationsTested
How to use it
- Go to the folder that contains your .env file.
- Run
evnx validateto list problems such as weak secret keys.
- Scan files for leaked credentialsTested
How to use it
- Run
evnx scan <file>to find credentials such as API keys and private keys. - Read the findings count and severity in the output.
- Run
- Convert .env files to deployment formatsTested
How to use it
- Go to the folder that contains your .env file.
- Run
evnx convert --to jsonto print the variables as JSON.
How far pickfit got
Linux x86_64
- Installs
- Starts
- 3 of 3 features work
- Works offline
Good for
- validate .env file for misconfigurations before deployment
- scan files for accidentally committed credentials
- convert .env file to deployment target format
- compare two env files for missing or different keys
- keep .env and .env.example aligned by variable name
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
Linux x86_64
Its main function works
- Replayed from scratch
- Works offline
- Checked on 30 Oct 2026
- Version 0.11.0