.env linter
Lint environment files for the mistakes dotenv will not explain.
Most loaders accept a broken .env file quietly. EnvLint gives you a readable issue list before those mistakes turn into confusing runtime behavior.
Invalid lines
Find non-comment lines that are not valid KEY=VALUE pairs.
Duplicate variables
Catch repeated keys that make config depend on parser order.
Placeholder drift
Spot values like changeme or your-key-here before release.
Practical lint checklist
- Every required key has a non-empty value in local and deploy environments.
- Every duplicate key is intentional or removed.
- Every secret-looking value is excluded from committed examples.
- Every required variable is represented in
.env.example.
Env linter questions
- Why do duplicate env keys matter?
- Most parsers silently choose one value. That can hide the setting you thought was active.
- Can EnvLint replace CI secret scanning?
- No. Use it as a local safety pass alongside CI scanning and platform secret management.