env-audit

To check environment variable consistency, audit your Zod schemas, .env.example files, and CI workflow secrets to identify drift. This process detects missing or mismatched variables across backend and frontend configurations, preventing runtime errors and deployment failures.

Environment variable drift occurs when configuration definitions mismatch across Zod schemas, .env.example files, and CI workflows. This inconsistency causes runtime errors and deployment failures because backend and frontend applications expect variables that are missing or incorrectly defined.

Ensure new API keys are added to frontend and backend .env.example files by running an environment variable audit. This verifies the key is correctly defined in the backend Zod schema, added to both .env.example files, and included in necessary CI workflow secrets.

Yes, you can audit a single environment variable instead of scanning the whole project. The audit supports single variable checks to verify its specific consistency across Zod schemas, .env.example files, and CI workflow secrets without a full project scan.

Track where secrets are used in CI/CD pipelines by auditing environment variable consistency. This identifies mismatches across CI workflow secrets and .env.example files, helping you map exactly where specific secrets are required and remediate missing configurations.