Get SCA Issues for Scan
Retrieve SCA issues for a specific scan
Authorizations
API key for authentication API tokens belonging to inactive users are rejected.
Path Parameters
The ID of the scan
Query Parameters
The page number for pagination
The number of results per page
x <= 50Filter by severity levels (comma-separated). Valid values: CRITICAL, HIGH, MEDIUM, LOW
Filter by package name (partial match)
Filter by package ecosystem (case-insensitive)
Filter by CVE identifier (partial match)
Filter by file path (partial match)
Filter by whether a fix is available (true/false)
Filter SCA issues by dependency reachability status
not_direct_dependency, pending, vulnerable_usage_reachable, vulnerable_usage_unreachable, dead_dependency Include dependency reachability status and description for each SCA issue.
Sort results by field (prefix with '-' for descending order)
created_at, -created_at, severity, -severity, package, -package, ecosystem, -ecosystem Filter by triage status (comma-separated). Valid values: open, fixed, false_positive, accepted_risk, duplicate
Filter by an exact package name. Unlike package, this does not match packages that merely contain the value (lodash will not match lodash.merge), which makes it safe for drilling into a package group.
Free-text search across package name, CVE identifier, summary, details, path and classification
