ck:security-scan

To scan for hardcoded secrets and security vulnerabilities, run a full security scan on your codebase. The scan uses configured grep-based patterns and language-specific audits to identify risks and produce a findings report.

Yes, you can run a dependency audit across Node, Python, Go, and other ecosystems. The scan automatically invokes language-specific package managers like npm audit and pip audit when available to detect dependency issues.

The best way to identify OWASP vulnerability patterns in a multi-language project is to run an on-demand scan aligned with OWASP top risks. This process analyzes your codebase using configured references to detect and report vulnerability patterns.

The security scan works across development, CI, and pre-release workflows. You can run on-demand scans at any stage to detect secrets, dependency issues, and vulnerability patterns before addressing risks early in your pipeline.

You can configure custom vulnerability patterns by updating the references used for grep-based scans. The scan runs these configured patterns against your codebase to detect specific security gaps and produce findings reports.

When scanning ecosystems without native audit tools like npm audit or pip audit, the security scan relies solely on configured grep-based pattern references. This limits dependency issue detection to predefined vulnerability patterns rather than live package registry checks.