> 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-package-operational-risk-findings/package-operational-risks-findings-reference/reference-a-findings-tab-columns.md).

# Reference A: Findings tab columns

The **Findings** tab on the **Package Operational Risk** page displays the following columns, read from the table definition for `FINDINGS_OPERATIONAL_RISK` in `package-integrity-findings.mock.ts`.

| Column                | Field name                     | Description                                                                                             |
| --------------------- | ------------------------------ | ------------------------------------------------------------------------------------------------------- |
| **Finding Name**      | `XDM_FINDING_NAME`             | The composed finding name, which identifies the detection type as either a deprecation or a scored risk |
| **Asset Name**        | `XDM_FINDING_ASSET_NAME`       | The package asset the finding was raised against                                                        |
| **Asset Id**          | `XDM_FINDING_ASSET_ID`         | The strong identifier of the package asset                                                              |
| **Package Manager**   | `CAS_FINDINGS_PACKAGE_MANAGER` | The ecosystem that declared the package                                                                 |
| **Dependency Type**   | `CAS_FINDINGS_PACKAGE_TYPE`    | Whether the package is a Direct or Transitive dependency                                                |
| **Repository**        | `CAS_FINDINGS_REPOSITORY`      | The repository containing the dependency manifest                                                       |
| **Branch**            | `CAS_FINDINGS_BRANCH`          | The branch the finding was detected on                                                                  |
| **Data Source**       | `CAS_FINDINGS_DATA_SOURCE`     | The VCS provider hosting the repository                                                                 |
| **Domain provider**   | `CAS_FINDINGS_DOMAIN_PROVIDER` | The provider domain associated with the repository                                                      |
| **Detection Method**  | `XDM_FINDING_DETECTION_METHOD` | The scanner that produced the finding. Always `CAS_OPERATIONAL_RISK_SCANNER` on this tab                |
| **Finding Category**  | `XDM_FINDING_CATEGORY`         | The category classification of the finding                                                              |
| **Finding ID**        | `XDM_FINDING_INSTANCE_ID`      | The unique instance identifier of the finding                                                           |
| **Created**           | `XDM_FINDING_FIRST_OBSERVED`   | Timestamp of first observation                                                                          |
| **First Hash**        | `CAS_FINDINGS_FIRST_HASH`      | The commit that first introduced the dependency                                                         |
| **First Commit Date** | `CAS_FINDINGS_FIRST_HASH_TIME` | Timestamp of that commit                                                                                |

**Note.** The **Findings** tab carries no severity column, unlike the **Issues** tab. Severity is embedded in the finding name for risk findings and is absent from deprecation findings entirely. Filter by the **Finding Name** pattern rather than expecting a sortable severity column.


---

# 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-package-operational-risk-findings/package-operational-risks-findings-reference/reference-a-findings-tab-columns.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.