About Environment Variable Manager

Parses .env file syntax into structured key-value pairs, validates variable naming against the pattern [A-Z_][A-Z0-9_]*, flags duplicates and malformed lines, and auto-detects secrets by scanning key names for tokens like “password”, “token”, “api_key”, and “jwt.” Parsed variables can be exported to five formats: raw .env, JSON object, YAML with comments preserved, Dockerfile ENV directives, and shell export statements. Secret values are masked by default and toggled with a visibility control.

• Validates variable names against [A-Z_][A-Z0-9_]* (case-insensitive) and reports line numbers for errors
• Detects 13 secret-related keywords including password, token, api_key, jwt, cert, and access_key
• Exports to .env, JSON, YAML, Docker ENV, and shell export formats with comment preservation
• Flags duplicate variable names and missing equals signs with per-line error reporting

Frequently Asked Questions

What variable naming rules does this tool enforce?

Names must start with a letter or underscore and contain only uppercase/lowercase letters, digits, and underscores. Lines missing an equals sign or with empty key names are flagged as errors with their line number.

How does it decide which variables are secrets?

It checks if the key name (lowercased) contains any of 13 keywords: password, secret, key, token, api_key, private, credential, auth, pass, pwd, jwt, cert, or access_key. Matching variables display as masked dots until you toggle visibility.