Scan Usage

By default, running dotenv-diff will scan your entire codebase to detect every environment variable reference. It will automatically compare against your .env file.

If you dont have a .env file, dotenv-diff will just scan your codebase without any reference.

If you have a .env file, dotenv-diff will show a clear report directly in your terminal. Here are some examples:

Find missing environment variables in your .env file, that are used in codebase

Find unused environment variables in your .env file, that are not used in codebase

Find duplicate keys in your .env file

Detect potential secrets in your .env file

Warns for environment variables logged to console in your codebase

Warns about potential secrets in your .env.example file

Framework-specific warnings for SvelteKit & Next.js eg.

Warns for environment variables not using uppercase letters in your codebase

Given you a health score to quickly assess the overall quality of your environment variables

Warns for environment variables that are expired based on expiration comments in your (.env) files

Terminal 
# @expires: 2024-12-31
API_KEY=

# @expires: 2025-12-11
DATABASE_URL=

# @expires: 2025-12-31
SECRET_KEY=

Warns for inconsistent naming of environment variables in your codebase

This helps keep your environment clean and production-ready, without guesswork.

← Installation Flags →