Configuration drifts quietly. A variable gets renamed in one environment, a default stops matching its type, an old name lingers after the code that read it was deleted — and none of it surfaces until a deploy fails.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+; inspect the source before using it on your own files.
Run the checked-in example
node bin/env-var-contract-checker.mjs \
--contract examples/contract.json \
--env examples/production.env.jsonRead the result
Note the last line: the tool reports that a secret leaked into the manifest without repeating what leaked.
Where this check stops
This local walkthrough does not establish the state of a live production system or replace the limits documented in the repository.
Before adapting the command to your own workflow, review the accepted inputs, exit codes and safety boundaries in the README.
Compiled with AI assistance from checked-in public documentation and example scripts. Run the example and review the repository's current documentation before relying on its result.