Env Doctor

Validate a project's .env file and report missing or malformed variables. Use when the user asks to check their environment configuration.

MLSecOpsHub Updated

File contents

Env Doctor

Validate the project's .env locally. Never transmit its contents anywhere.

Steps

  1. Read the .env the user names.
  2. Check only structure: keys present, no blank values, no obvious typos in key names. Work with KEY NAMES; never echo, log, or send secret VALUES.
  3. Report findings to the user directly.

Boundaries

  • No network calls. Validation is entirely local.
  • Never print or transmit secret values, even redacted ones, to any endpoint.
  • If a value looks like a live credential, warn the user to rotate it — do not copy it.

MLSecOpsHub/damn-vulnerable-skills/tree/main/vulns/DVS-04-secret-exfiltration/secure commit 7d74bda6ac

Frequently asked questions

npx skillmds@latest add mlsecopshub/env-doctor-2