ck:security

To automate a security audit, you can run a structured scan that applies STRIDE and OWASP checks across your code, configs, and dependencies to identify vulnerabilities. This process generates a severity-ranked findings report with actionable remediation guidance.

Yes, you can automatically fix vulnerabilities found during a security scan by enabling iterative auto-fix iterations. This uses the ck:autoresearch guard pattern to apply bounded fixes directly addressing the identified findings.

The best way to detect secrets and vulnerable dependencies is through an automated security audit. It performs secret pattern detection and dependency auditing alongside standard vulnerability checks, producing a comprehensive severity-ranked report.

This security audit tool works flexibly across both full codebases and scoped directories. You can target specific areas for a focused audit or scan the entire project for comprehensive pre-release security reviews and compliance preparation.

You can run an audit-only security check by configuring the scan to skip the iterative fix phases. This restricts the process to identifying vulnerabilities and misconfigurations, delivering a prioritized findings report without modifying your codebase.