Enforce .env Naming Conventions
Check that environment variable names follow UPPER_SNAKE_CASE.
💡 Catches duplicate keys, spaces around =, unquoted values, and naming-convention issues — then gives you a cleaned, sorted file and a ready-to-commit .env.example. Your secrets are parsed entirely in your browser and never uploaded.
conventions tips
Lowercase or mixed-case keys are flagged so your config follows the UPPER_SNAKE_CASE convention.
Invalid key names (bad characters, leading digits) are reported as errors.
Consistent naming avoids subtle bugs when different tools read the same file.
Validated locally — your secrets stay put.
So funktioniert es
Warum unseres?
Also check out…
Generate a .env.example
Create a .env.example from your real .env so teamm
Debug a Broken .env File
Find why your environment variables aren't loading
Clean Up a Messy .env
Sort, de-duplicate, and normalise an .env file.
Validate .env Before Deploying
Catch config mistakes before they reach production