Compare three saved, redacted local, CI and production configuration exports. A captured Node-version mismatch is actionable; an omitted list or unsupported secret assertion is not evidence of parity. This tool reads one local JSON bundle and reports differences and uncertainty. It never probes an environment, verifies a secret, edits configuration, or contacts a host.
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/environment-parity-checker.mjs --root examples/clean --input input.json
node bin/environment-parity-checker.mjs --root examples/failing --input input.json --json
node bin/environment-parity-checker.mjs --root examples/incomplete --input input.json
npm run checkRead the result
The clean example exits 0, the Node-mismatch example exits 1, and the incomplete-list example exits 2. --help prints usage. JSON goes to stdout; a fixed human summary goes to stderr unless --json is set. There is no report-file option.
Where this check stops
The input is a deliberately narrow saved-JSON dialect. This reporter does not read environment variables, CI APIs, a production host, package managers, or secret stores. A present secret or same assertion is an exporter's claim, not proof of the underlying bytes. An intentional-difference note is recorded evidence, not approval or a policy waiver. No remediation, deployment, network access, or output file writing occurs.
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.