---
title: "Find the unknown-dependency reason in CycloneDX or SPDX | Proofline Help"
description: "When a deployment review SBOM includes an unknown package entry, the document itself records why Proofline could not list the head commit’s dependencies."
url: https://proofline.sh/help/sbom-unknown-cyclonedx-spdx/
---

[Help center](/help/)

# Find the unknown-dependency reason in CycloneDX or SPDX

When a deployment review SBOM includes an unknown package entry, the document itself records why Proofline could not list the head commit’s dependencies.

## Locate the reason on the exported package

Download the format you need from the review’s **Software bill of materials** card. In CycloneDX inspect the **proofline:unknownReason** property. In SPDX read the package comment. Match the entry to the review’s head commit before comparing exports.

A pending reason means the source read is in progress. Disabled analyzers mean no collection is running. A failed read or a read that found no packages can also leave an unknown entry. The export describes source manifests and lockfiles rather than the container’s installed contents.

## Related guides

-   [Download an SBOM](/help/sbom/)
