Get Operational Risk Report Content

Xray REST APIs

Products
JFrog Xray
Content Type
REST API
ft:sourceType
Paligo

Description: Get specific content in an Operational Risk report.

Since: 3.49.0

Security: Requires a user with the Manage Reports role.

Notes: For Xray version 3.21.2 and above with Projects, a Project Admin with Manage Security Assets privilege can get specific content in an Operational Risk report. using this REST API in the scope of a project, by using the additional query parameterprojectKey.

Usage: POST /api/v1/reports/operationalRisks/{id}

Mandatory Pagination Parameters: You can order by

  • risk

  • artifact

  • component

  • released

  • is_eol

  • cadence

  • commits

  • committers

Sample Request

POST .../api/v1/reports/operationalRisks?direction=asc&page_num=2&num_of_rows=10&order_by=risk

Sample Response

{
  "total_rows": 100,
   "rows" :[
    {
        "component": "deb://debian:master:abc:2.28-10",
        "artifact": "docker://redis:latest-07142020122937",
        "path": "repo/dir/file",
        "artifact_scan_time": "2021-01-01T01:00:00+02:00",
        "risk": "High",
        "risk_reason": "",
        "released": "2005-01-01T03:00:00+02:00",
        "version": "2.28-10",
        "latest_version": "1.2.3"
        "newer_versions": "10,
        "is_eol": "true,
        "eol_message": "unsupported",
        "cadence": "5",
        "committers": "10",
        "commits": "7",
        "project_keys": ["proj1","proj2"],
  ]
}