env-secrets-manager

You can scan a local repository for hardcoded credentials by running the env auditor script on your working directory. It uses regex-based pattern matching to detect exposed API keys, tokens, and private keys in source code and configuration files before you push to a shared remote repository.

Sensitive environment variables detected in source code include hardcoded credentials like API keys, access tokens, and private keys. The audit targets configuration files and source code across both development and production environments to prevent accidental security leaks.

Regex-based pattern matching finds accidentally committed secrets by systematically scanning local repository files against predefined credential patterns. This mechanism identifies potential secret exposure in source code and generates structured reports for remediation and security rotation workflows.

Yes, you can audit environment files across development and production environments. The skill facilitates the identification of secret exposure in configuration files throughout your entire infrastructure, ensuring consistent environment variable hygiene and security compliance.

After detecting exposed API keys and tokens, you should follow the provided lifecycle management guidance for rotating secrets. The structured reporting output supports remediation workflows, allowing you to securely rotate compromised credentials before pushing code to a shared repository.