$ envlock health
[SCAN] EnvLock Health Check - my-project
- Phase 1: Loading environment files and scanning code...
✔ Loaded 5 variables from .env files, 3 from examples; found 6 variables referenced in code
- Phase 2: Analyzing dependencies and checking variables...
✔ Analyzed dependencies (2 required by 1 packages); found 2 missing, 1 unused variables; identified 1 security risks
- Phase 3: Detecting issues and reviewing history...
✔ Detected 0 logged variables, 1 syntax issues; found 0 Git history flags
- Phase 4: Validating metadata and consistency...
✔ Validated metadata (found 0 expired variables); checked naming (0 inconsistencies) and frameworks (0 warnings)
- Phase 5: Finalizing analysis...
✔ Analysis complete
- Missing Variables
API_KEY
DATABASE_URL (Required by: prisma@^5.0.0)
! Security Risks
AWS_SECRET_KEY - potential secret based on naming pattern
- Syntax Issues
.env:5 - Unquoted value with spaces
- Unused Variables
DEBUG
Actions needed: 4 fixes
✓ Health check completed!
Sample repo: Flags a missing API key + Git leak, suggests fixes. (Your results may vary—test on a fresh clone!)