Repository navigation
First stable release of envguard: check and sync .env files, validate required keys, scan application configuration, audit Git history, and encrypt/decrypt env files.
Changes since v0.3.0
- Scan every YAML document and accept equals, colon, and whitespace property separators.
- Support nested environment fallbacks, including deeper chains and literal defaults. Strict validation evaluates fallback requirements conditionally.
- Include nested variables in quiet output and expose their structure in JSON.
- Detect secrets and committed env files introduced in merge commits.
- Restrict decrypted output to owner read/write permissions on Unix, including forced overwrites, while preserving overwrite protection.
- Add regression coverage for config scanning, CLI behavior, merge history, encryption authentication, and decrypted-file permissions.
Scope
- Config scanning checks key presence; empty values count as defined. Use check or validate to reject empty values.
- Git auditing scans history reachable from local refs using known secret patterns; it does not guarantee detection of every secret. CI checkouts must include the history and refs intended for auditing.
Validation
Go tests and go vet passed locally; GitHub CI passed for commit dc15c5a.