env-config-validator

Environment variable validation checks that required secrets, API keys, and database URLs are correctly configured across local, staging, and production .env files. Run the provided Python script to audit variables for presence, proper scoping (NEXT_PUBLIC_ vs private), and secure values, receiving structured reports with severity levels and fix suggestions.

NEXT_PUBLIC_ variables are exposed to the browser and safe for public data; private variables remain server-side only. The validator enforces this scoping, detecting when secrets or sensitive configuration are incorrectly marked as public, preventing accidental exposure in Next.js and Node.js projects.

Yes, the validator scans environment files to identify exposed secrets, weak or missing credentials, and misconfigured values. It flags issues by category and severity, cross-references against environment templates, and suggests fixes to prevent production incidents.

The validator performs cross-environment auditing by comparing .env, .env.local, and .env.production files against a template, verifying required variables exist in each environment and that naming conventions and scoping rules are applied consistently.

Yes, the validator is built for Next.js and Node.js projects, parsing .env variants including .env.local and .env.production, enforcing NEXT_PUBLIC_ scoping conventions, and validating the full configuration pipeline for both frameworks.

Ensure your .env files exist in the project root, define which variables are required for your application, and optionally create a .env.template or schema file to validate against. The validator then checks presence, format, and cross-environment consistency.