Find missing environment variables

Supply environment samples and the variable names each deployment needs. Results contain names and differences, never values.

In your browser nothing you paste is uploaded

What to provide

The example compares development and production for missing required keys and inconsistent configuration.

required: An array of variable names every environment should provide.
environments: An array of objects, each with a name and content containing its .env text.
environments[].content: Encode line breaks as JSON newline escapes. Values stay in this browser and are omitted from results.

Input template

{
  "required": ["DATABASE_URL"],
  "environments": [
    {"name": "development", "content": "DATABASE_URL="},
    {"name": "production", "content": ""}
  ]
}

Compares the supplied .env files. It cannot read deployed settings, verify credentials, or reproduce your runtime’s environment parser.

This checks one thing. A scan reads your whole repository and tells you what an attacker would find first.

Free scan

More tools

CODEOWNERS coverage checker Match file paths against CODEOWNERS rules and find gaps in ownership. Security finding deduplicator Group duplicate findings by location or a supplied stable fingerprint. Security baseline comparator Compare finding sets for new, changed and no-longer-reported issues. JWT debugger Decode a token and catch alg:none, a missing expiry, and secrets in the payload. Secret scanner Paste a .env file or a diff and find the keys that should not be in it. CSP evaluator Grade a Content-Security-Policy and see which directive undoes it.

Find missing environment variables

Results

Findings

Scope of this result