ENV Key Type Validator
Check boolean, finite decimal, absolute HTTP URL, JSON and enum values against key-name clues or a JSON schema block. Review issues by line or key with a limited boolean case fix.
Fix a Boolean Case Mismatch in .env
ENV Key Type Validator: how to use it
- Paste or open dotenv text, or supply a JSON object with env or declared. Add a schema object to define rules explicitly.
- Select Validate key types and review the failures, checked entries and keys without applicable rules.
- Apply a proposed boolean case fix if accepted by your application. Review any remaining findings and export the report when needed.
Limits and notes
Use up to 262,144 UTF-16 code units per input and up to 10,000 lines of dotenv text. Processing takes place in your browser. JSON values can be strings, booleans or finite safe numbers. The check does not read endpoints or expand variables. The optional boolean fix changes case in a local .env draft.
How your privacy works →ENV Key Type Validator: common questions
Does a quoted true become a boolean in .env?
Node.js reads environment values as strings. The boolean rule checks whether the parsed string spells true or false.
How does a schema change the checks?
When you supply a schema object, keys under it use those rule definitions and other keys are unchecked. A rule with required set to false may be absent.
Do the exported type findings include secrets?
The report contains names, locations and rule findings. Source text and assigned values stay in the source editor.