Inline diagnostics for environment variables -- find missing, unused, and undocumented env vars without leaving your editor.
- Missing vars -- env vars referenced in code but not in
.env.example(error) - Unused vars -- vars in
.env.examplebut never referenced in code (warning) - Undocumented vars -- vars in
.envbut not in.env.example(info) - Empty vars -- vars defined in
.envwith no value (warning) - Quick fixes -- add missing vars to
.env.examplewith one click - Multi-language -- scans
.ts,.js,.vue,.svelte,.py,.go, and more
EnvGuard scans your source files for env var patterns (process.env.X, import.meta.env.X, etc.) and compares them against your .env and .env.example files. Issues appear as inline diagnostics in your editor.
| Pattern | Runtime |
|---|---|
process.env.VAR |
Node.js |
process.env['VAR'] |
Node.js |
import.meta.env.VAR |
Vite, Nuxt, Astro |
Deno.env.get('VAR') |
Deno |
os.environ['VAR'] |
Python |
os.Getenv("VAR") |
Go |
| Setting | Default | Description |
|---|---|---|
envguard.enable |
true |
Enable/disable diagnostics |
envguard.includeBuiltins |
false |
Include NODE_ENV, PATH, etc. |
For CI pipelines, use the envguard CLI:
npm install -g @faizkhairi/envguard
envguard # exits with code 1 if missing vars foundMIT