tool · ops / safety

envguard.

validate .env files against a schema before deploy.

describe required keys + types in a small yaml. envguard runs at build / start time, refuses to boot if anything is missing or wrong-typed.

npm i -g @v0idd0/envguard

github → npm mit · free forever

envguard check→→ validate .env vs schema

envguard --schema env.yaml→→ custom schema

envguard run -- node app.js→→ guard before exec

envguard init→→ scaffold schema from existing .env

envguard --strict→→ unknown keys = error

envguard diff prod.env staging.env→→ key drift report

envguard --required PORT,DB_URL→→ inline schema

envguard --json→→ ci-friendly output

envguard check→→ validate .env vs schema

envguard --schema env.yaml→→ custom schema

envguard run -- node app.js→→ guard before exec

envguard init→→ scaffold schema from existing .env

envguard --strict→→ unknown keys = error

envguard diff prod.env staging.env→→ key drift report

envguard --required PORT,DB_URL→→ inline schema

envguard --json→→ ci-friendly output

what it does

never see DATABASE_URL undefined in production again.

four jobs. all in your terminal. no api call, no internet round-trip — just a plain tool that does what it says.

guard a deploy

$ envguard check

✓ DATABASE_URL url
✓ PORT int
✗ SENTRY_DSN missing

wrap your start

$ envguard run -- node app.js

envguard: all keys ok
app: listening on :3000

diff two envs

$ envguard diff prod staging

+ FEATURE_X (in prod only)
- DEBUG (in staging only)

scaffold schema

$ envguard init

wrote env.yaml
(11 keys inferred)

install

three ways. all painless.

npm

$ npm i -g @v0idd0/envguard

node 14+ on linux / macos / windows. updates with npm update -g.

github releases

$ curl -L github.com/voidd0/envguard/releases/latest

single static binary. zero runtime needed. all releases →

git clone

$ git clone github.com/voidd0/envguard

read the source, send a pr, fork it. mit licence, no cla. repo →

why we built it

“why is staging crashing?” → 20 minutes later: oh, we forgot to set REDIS_URL. envguard catches that before the boot sequence even starts.

no telemetry. no signup. just a tiny yaml schema + a fail-fast check. mit forever — the source is public and the npm package is yours to fork.

star on github → envguard vs dotenv-linter → all tools

power user?

use this daily? tools.voiddo Pro · $9 one-time

supports 66 free tools · Pro license via Paddle · one flat price, no subscription