security_scan

You can run a consolidated security scan to assess dependency vulnerabilities, static code findings, and privacy dataflow issues in one pass. The scan orchestrates three independent scanners in parallel and outputs a prioritized summary with severity counts and remediation guidance.

Prioritizing vulnerabilities is best handled by running a security scan that surfaces critical and high findings first. This approach outputs a minimal response shape with per-scanner status, severity counts, and top findings with file locations to streamline remediation.

To scan your project codebase for privacy and dataflow findings, execute a security assessment that includes a dedicated privacy scanner. This runs alongside static analysis and dependency audits to detect dataflow issues without blocking results if an individual scanner fails.

Yes, the security scan tolerates per-scanner failures during a CI pipeline run. It orchestrates three independent scanners in parallel and ensures that if one scanner fails, it does not block the overall result or the generation of the consolidated severity breakdown.

Yes, you can use this security assessment to check package dependency vulnerabilities. The scan specifically includes a dependency audit function that runs in parallel with static and privacy scanners to identify vulnerable packages and provide remediation guidance.

The security scan output payload includes per-scanner status, severity counts, and top findings with file locations and messages. This minimal response shape is designed to surface critical and high findings first, streamlining the remediation process.