Offline parser proof
Same .env.
Different runtime.
Catch missing keys, quote drift, bad coercion, unsafe placeholders, and environment drift before your service starts.
- No network
- No telemetry
- No secret output
Live semantic plate
See what the runtime sees.
This browser demo uses the same core rules for the most common quoting fault. Text stays in this tab and is discarded when you leave.
You’re offline. Good news: the demo and docs still work; nothing needed a server.
CI-sized workflow
Contract. Parse. Prove.
- 01
Write the contract once
Required, typed, bounded, secret-aware. TOML stays reviewable beside your code.
- 02
Name the real parser
Node, Python, and Docker do not always agree about quotes, comments, or expansion.
- 03
Fail before startup
Human output locally; stable JSON and deliberate exit codes in CI. Values stay redacted.
Version 0.1.0 · MIT
Put it before docker run.
Build the single binary from source today. Release binaries can drop into the same CI command later.
cargo install --git https://github.com/B-Divyesh/sf-env-contract-check
$ env-contract-check check \
--contract env.contract.toml \
--env .env.production \
--profile docker \
--deny-warnings
ERROR [invalid_type] APP_PORT — expected a base-10 integer
Result: FAIL · 1 error(s), 1 warning(s)
A deliberately boring data policy
Your secrets never become our data.
The CLI is offline. The demo has no backend. There are no analytics, cookies, accounts, uploads, or local storage.