For the complete documentation index, see llms.txt. This page is also available as Markdown.

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.

Last updated

Was this helpful?