Naming Convention Checker

Key names are the API of a configuration system. DB_PASSWORD, dbPassword, db-password and DB.password may all work on one parser and fail on another, and a codebase mixing them is a codebase where nothing is greppable.

The Naming Convention Checker validates every key in your .env against the community-standard UPPER_SNAKE_CASE — or a rule you choose. It reports each offending key with its line number and exactly why it fails: lowercase letter, hyphen, dot, leading digit, or stray character.

It also flags invalid characters that will break the strictest parsers, and skips commented lines so your documentation stays free of false alarms.

• UPPER_SNAKE default: the standard .env rule.
• lower_snake option: for projects that enforce it.
• Mixed mode: only structural validity, no case rule.
• Character rules: dots and hyphens toggleable.
• Reason per key: exact why a name fails.
• Line numbers: locate offenders fast.
• Commented lines ignored: no false alarms.
• Private & free: all in-browser.

1. Paste your .env into the input, or load the sample which breaks every rule on purpose.
2. Pick the convention (upper, lower, or mixed).
3. Toggle character rules for dots and hyphens.
4. Click Check. Offenders are listed with reasons.

Example 1 — Cross-parser breakage. A team migrating to a strict parser finds db.host and service-url silently ignored. The checker names both keys before the switch.

Example 2 — Grep failure. A mix of api_key and API_KEY makes a simple grep for the secret miss half the references. Enforcing one case fixes the audit.

Example 3 — Leading digit. 2FA_ENABLED=true is invalid in most parsers; the checker explains the first character rule.

Example 4 — Terraform exposure. Names with dots look valid in .env but break environment exports to Terraform, which rejects them at apply time.

Example 5 — Community review. An open-source project uses the checker as a PR gate so every new key follows the documented naming standard.

• Standard-first: defaults to the community rule.
• Explainable: every violation carries a reason.
• Flexible: convention and characters adjustable.
• Parser-safe: stops silent key drops.
• Private: never leaves the page.
• Free: unlimited runs.