audit-env-variables

To find unused environment variables in a JavaScript or TypeScript project, audit your .env files and code references. This process maps declared variables to their actual usage, highlighting unused entries for potential safe cleanup.

Detecting service keys and inferring permissions for environment variables involves analyzing variable names and usage paths across your codebase. This identifies keys like Stripe or AWS and assesses their risk implications for a security audit.

You can remove unused .env declarations safely by generating backups and running regression checks. This validates that the cleanup of unused variables does not introduce production issues or break existing code paths.

The best way to generate a security audit report for environment variables is to map their usage and infer permissions automatically. This produces a structured Markdown report detailing declared, used, and undeclared variables for compliance review.

Yes, the environment variable audit works with both .env files and code declarations. It locates all .env* files and environment declarations across the repository, correlating them with code references to determine which variables are actively used.