> 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-b-finding-side-panel-fields.md).

# Reference B: Finding side panel fields

Select a row to open the finding side panel. The **Package Operational Risk** page uses a dedicated side panel evidence component, registered at `findings.extensions.config.ts:110`, which presents the following fields per `package-integrity-side-panel-sections.component.ts:87`.

| Field                 | Description                                                                                    |
| --------------------- | ---------------------------------------------------------------------------------------------- |
| **Data Source**       | The VCS provider, displayed with a provider icon and a link to the data source                 |
| **Repository**        | The repository containing the dependency manifest                                              |
| **Package Manager**   | The ecosystem, displayed with an ecosystem icon                                                |
| **Dependency Type**   | Direct or Transitive                                                                           |
| **Branch**            | The branch the finding was detected on                                                         |
| **Backlog Status**    | Whether the finding is New or pre-existing backlog                                             |
| **Collaborator**      | The Git author associated with the commit that introduced the dependency                       |
| **First Hash**        | The commit that first introduced the dependency                                                |
| **First Commit Date** | Timestamp of that commit                                                                       |
| **Actions**           | The policy actions that matched the finding, displayed as labels. Empty when no policy matched |

**Read the Actions field to diagnose a policy gap on a single finding.** An empty **Actions** field is the per-finding equivalent of the population-level policy gap described in the audit workflows: the finding was detected, no policy matched, and no issue was created.

**Note.** **Backlog Status** distinguishes a newly introduced dependency from pre-existing technical debt. A New operational risk finding means a developer has just added a dependency that was already unmaintained at the time of adoption, which is a prevention failure rather than a modernization backlog item. For enforcement at intake, refer to Unified Application Security Policies.


---

# 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-b-finding-side-panel-fields.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.