Skip to main content

Config contract

Catches environment variable drift: code references process.env.* (or import.meta.env) that are missing from .env.example or unset in CI.

What it catches​

  • Env vars used in code but absent from .env.example
  • Vars declared in .env.example never referenced (optional noise)
  • Required secrets missing in the runner environment

CLI​

npx prodverdict check config --config prodverdict.yml

Use the full template with access + config: examples/nextjs-stripe/prodverdict.full.yml.

GitHub Action​

- uses: prodv-dev/prodverdict-action@v0.9.1
  with:
    config: ./prodverdict.yml
    contract: config

MCP​

Local and remote MCP expose check_config_contract and validate_config.