security-audit

The audit script scans for exposed credentials by checking config files and code for sensitive data leaks, while also validating rate limiting, auth, and CORS settings to detect configuration gaps across your deployment environment.

The best way to check Docker security risks is using an automated audit that evaluates container configurations against best practices, identifies misconfigurations, and provides an auto-fix option to remediate common issues found during the scan.

Yes, you can detect secrets leaked in Git history by running the security audit, which includes checks for secrets exposure in recent commits, helping teams find sensitive data leaks in version control before they impact operations.

Yes, the security audit works in deployment pipelines by running the audit script during automated flows, supporting scheduled scans and post-incident investigations across environments to scan port exposure, file permissions, and configuration gaps.

You run a quick security check or full audit by executing the audit.cjs script in the scripts directory, where the quick audit targets common issues for fast validation and the full audit provides a comprehensive security assessment.

Yes, the audit can automatically fix open ports and file permission issues using its built-in auto-fix option, which remediates common security problems found during the scan, including port exposure and sensitive file protection gaps.