How do you get more exposure for your open-source project?
2 days ago
- #security
- #development-tools
- #environment-variables
- Scan codebase to detect environment variables used in SvelteKit, Next.js, Node.js, Nuxt, Vue, and other modern JavaScript/TypeScript projects.
- Ensure required environment variables are defined before deploying to catch missing or misconfigured variables early.
- Improve team collaboration by keeping everyone aligned on necessary environment variables.
- Enhance security by preventing sensitive variables from being accidentally committed to version control.
- Scale confidently in turbo monorepos and multi-environment setups.
- Compare environment variables against an example file (e.g., .env.example) to detect discrepancies.
- Include files from monorepo packages in the scan using the --include-files flag.
- Automatically fix missing keys in .env files using the --fix flag.
- Treat all warnings as errors in CI environments with the --strict flag.
- Detect and warn about incorrect environment variable usage in SvelteKit and Next.js projects.
- Scan .env.example files for potential secrets and known provider key patterns.
- Detect and warn about environment variables being logged to the console.
- Ignore specific lines from secret detection using the dotenv-diff-ignore comment.
- Calculate a health score based on missing variables, exposed secrets, naming conventions, and framework-specific warnings.
- Detect environment variables with expiration dates and warn about expired or soon-to-expire variables.
- Warn about inconsistent naming patterns for environment variables.
- List unused variables in .env files and disable this behavior with --no-show-unused.
- Disable scan statistics with --no-show-stats.
- Specify files to include or exclude from the scan using --include-files and --exclude-files.
- Compare values of variables in .env and .env.example files with --check-values and --compare.
- Exclude keys from comparison using --ignore or --ignore-regex.
- Detect non-uppercase environment variable keys and suggest uppercase versions.
- Generate a config file with default settings using --init.
- Output results in JSON format with --json.
- Disable colored output with --no-color.
- Compare all matching .env* files against .env.example with --compare.
- Restrict comparison to specific categories with --only.
- Run non-interactively in CI environments with --yes or -y.
- Prompt to create missing .env or .env.example files.
- Warn if .env file is not ignored by Git to prevent accidental commits of sensitive data.