> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/application-security/code-security/code-security-scanners/software-composition-analysis-sca-scanners/package-operational-risk-scanner/understand-the-package-operational-risk-table.md).

# Understand the package operational risk table

The Package Operational Risk table provides a consolidated view of all operational risk issues. Each row represents an issue created when a scanner finding matches a unified policy, linking the operational risk assessment to a specific package, dependency manifest file, repository, and the policy that triggered the issue.

The columns in this table are documented in a shared reference. For descriptions of every available column, the attributes common to all code scan issue tables and the attributes specific to this issue type, see [Issue table attributes reference](/application-security/code-security/code-security-scanners/issue-table-attributes-reference.md). 

## Filter and sort the table

Use the filter bar at the top of the Package Operational Risk table to narrow results by any filterable column. Common filtering strategies include:

* **By Severity:** Filter to High and Critical severity to focus on packages with the most significant operational risk factors
* **By Package Manager:** Filter to a specific package ecosystem such as NPM, Maven) to scope review by technology stack
* **By Dependency Type:** Filter to Direct to focus on dependencies explicitly declared in the project, or to Transitive to identify operationally risky packages inherited through the dependency chain
* **By Repository / Branch:** Filter to a specific repository to scope review to a single codebase, or to the main/production branch to focus on operational risk issues that affect production-bound code
* **By Resolution Status:** Filter to New to identify untriaged operational risk issues, or to In Progress to monitor active remediation

## Manage issues

Right-click a row in the **Package operation risks** table to access the following actions.

| Action                                     | Description                                                                   |
| ------------------------------------------ | ----------------------------------------------------------------------------- |
| **Change Status**                          | Modify the resolution status of the issue. Values: New, In Progress, Resolved |
| **Change Severity**                        | Modify the severity level of the issue. Values: Critical, High, Medium, Low   |
| **Change Assignee**                        | Change the user or identity assigned to address the issue                     |
| **Copy text to clipboard**                 | Copy the selected cell text                                                   |
| **Copy entire row**                        | Copy the full row of data                                                     |
| **Copy issue URL**                         | Copy the URL of the issue, to share or reference the issue                    |
| **Show/hide rows with the severity level** | Show or hide all rows matching the severity level of the selected row         |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/application-security/code-security/code-security-scanners/software-composition-analysis-sca-scanners/package-operational-risk-scanner/understand-the-package-operational-risk-table.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.