scan-deep

To enrich an initial security scan, you can process an existing initial-scan JSON file to validate findings, perform stack-aware discovery, remove false positives, and output a deep-scan JSON report conforming to the Pydantic ScanReport schema.

Removing false positives from a web application security scan is achieved by re-processing initial findings against a standardized schema and performing stack-aware probing to corroborate existing vulnerabilities before outputting a validated report.

Yes, you can validate JSON scan reports against the Pydantic ScanReport schema by loading the initial scan data, reconciling the findings, and producing a Pydantic-conformant JSON output for remediation workflows.

Performing stack-aware discovery to expand a web application assessment involves probing detected stack configurations to reveal additional vulnerabilities, corroborating initial findings, and enriching the final validated output.

Yes, you need an existing initial-scan.json because the deep scan process requires an initial scan to load, validate against the ScanReport schema, and enrich with stack-aware discovery and false positive removal.

Security scan JSON reports fail schema validation during enrichment when initial findings do not conform to the standardized ScanReport schema, requiring reconciliation and validation before producing a production-ready output.