security_scan

Security vulnerability prioritization is achieved by running dependency audits, SAST scans, and HoundDog scans in parallel. Results are consolidated into a compact, structured output compatible with downstream dashboards, delivering a single prioritized summary of all findings across code and packages.

Yes, you can run a SAST scan and dependency audit simultaneously. The skill uses parallel orchestration to execute all scanning mechanisms concurrently, which speeds up the overall analysis and returns a consolidated vulnerability report faster than running each scanner sequentially.

If one scanner fails during the security scan, your vulnerability report is still preserved. The parallel orchestration mechanism is designed to tolerate individual scanner failures, ensuring that partial results from the dependency audit, SAST, or HoundDog scans are still delivered in the final structured output.

Yes, this security scanning approach supports both code repositories and packages. The scope explicitly covers static code findings through the SAST scan and package vulnerabilities through the dependency audit, providing comprehensive risk identification across your entire software project.

You can integrate SAST and dependency audit results by leveraging the compact, structured output generated by the scan. This format is specifically designed to be compatible with downstream dashboards and vulnerability reporting workflows, allowing seamless export of prioritized security findings for incident response.

You need to run a HoundDog scan alongside a SAST scan when you want to identify both static code vulnerabilities and privacy or security dataflow findings. Combining these scanning methods provides a more comprehensive security assessment than using a single static analysis tool alone.