security-audit

To scan for security vulnerabilities and hardcoded secrets, you can run an automated security audit that targets authentication, data handling, and API workflows to enforce secure coding standards. It detects injection flaws, path traversal, and exposed credentials.

Checking project dependencies for known CVEs requires an automated vulnerability scanning process that inspects your dependency tree. This security audit scans dependencies to identify known vulnerabilities and provides auto-remediation paths to resolve them.

Yes, you can use automated vulnerability detection during the development of new API endpoints. The security audit targets API integration workflows to enforce secure coding patterns and identifies input validation issues and XSS vulnerabilities.

Security auditing detects SQL injection and path traversal vulnerabilities through comprehensive code analysis. The automated scanning process targets input validation issues to ensure production-grade security compliance before deployment.

Yes, you need the @claude-flow/cli dependency installed to execute the security audit skill. This prerequisite allows the advanced automated scanning scripts to run comprehensive vulnerability detection on your software projects.

You should run an automated vulnerability scan when developing new authentication modules or API endpoints to ensure secure coding patterns are enforced. This prevents hardcoded secrets and common coding flaws from reaching production.