> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/artifact-registry/3.0/security-and-compliance/sbom-view-score-and-download.md).

# SBOM: view, score, and download

View the Software Bill of Materials for a scanned container image in Harness Artifacts, understand its SBOM score, and download the document for compliance.

Every time you push a container image to a Docker or Helm registry that has security scanning enabled, Harness generates a **Software Bill of Materials (SBOM)** alongside the vulnerability scan. The SBOM is a machine-readable inventory of every component inside the image: the packages, their versions, their suppliers, the licenses they carry, and the relationships between them.

This page explains how to find the SBOM on an artifact, how to read the SBOM score, and how to download the SBOM document for use in compliance submissions, audits, or blast-radius analysis.

## Before you begin

* Security scanning must be enabled on the registry. Go to [Configure security scanning](https://developer.harness.io/artifact-registry/3.0/registries/configure-security-scanning.md) to enable it.
* Viewing the **SBOM** tab requires a Harness Supply Chain Security (SCS) license.
* SBOMs are generated for Docker and Helm registries only.
* At least one image must have been pushed after scanning was enabled. Images pushed before scanning was configured do not have SBOMs unless you push a new version.

## View the SBOM

To open the SBOM for an artifact:

1. In the navigation menu, select **Artifacts**.
2. Click the artifact you want to inspect.
3. Select the **SBOM** tab on the artifact detail page.

The SBOM tab shows the complete dependency inventory for the image. Each row in the component table represents one software component found inside the image:

| Column              | What it shows                                                                                                    |
| ------------------- | ---------------------------------------------------------------------------------------------------------------- |
| **Component**       | The name of the package or library.                                                                              |
| **Version**         | The installed version of the component.                                                                          |
| **Supplier**        | The organization or maintainer that produces the component.                                                      |
| **Package manager** | The ecosystem the component belongs to (for example: `npm`, `pip`, `maven`, `alpine`).                           |
| **License**         | The license under which the component is distributed.                                                            |
| **PURL**            | A Package URL: a standardized identifier for the component, usable in other tooling and vulnerability databases. |

The total component count appears at the top of the tab.

{% hint style="info" %}
**Multi-arch images**

For multi-architecture images, the SBOM reflects the manifest selected in the tag/digest selector at the top of the artifact detail page. Select the specific architecture before reading the SBOM if you need findings for a particular build target.
{% endhint %}

## Understand the SBOM score

Harness computes an **SBOM score** for each scanned artifact. The score is a single number that reflects the overall health of the artifact's dependency inventory. Three factors contribute to it:

**Completeness** measures how fully the SBOM was resolved. Missing versions, unidentified suppliers, or packages without a license declaration reduce completeness. A lower completeness score means the SBOM cannot be relied on as a full audit record.

**License risk** reflects whether any component carries a high-risk or unknown license. Licenses such as GPL, Affero General Public License (AGPL), or Lesser General Public License (LGPL) may have downstream implications for commercial software distribution. Unknown licenses represent components that could not be classified.

**Vulnerability exposure** aggregates the CVE count and severity distribution across all components in the SBOM. This factor is influenced by the vulnerability scan results: a clean image with no CVEs contributes positively, and an image with multiple Critical CVEs contributes negatively.

The score gives you a quick signal before you drill into individual findings. A high score means the SBOM is complete, the license profile is clean, and no high-severity CVEs are present. A low score means at least one of these areas needs attention.

## Download the SBOM

To download the SBOM document:

1. Open the **SBOM** tab on the artifact detail page.
2. Select the download format:
   * **CycloneDX JSON**: the recommended format for security tooling. Designed specifically for vulnerability tracking, policy evaluation, and supply chain workflows. Widely supported by SBOM analysis tools.
   * **Software Package Data Exchange (SPDX)**: the format developed by the Linux Foundation with broad support in open-source tooling and license compliance workflows.
3. Click **Download**.

The SBOM document is downloaded as a JSON file. It includes the NTIA-defined minimum elements for SBOMs (component names, versions, unique identifiers, dependencies, and the author of the SBOM data), making it suitable for submission to customers, auditors, or regulators who require NTIA-compliant SBOMs.

### Common uses for a downloaded SBOM

**Compliance submissions**: US Executive Order 14028 requires SBOMs for software delivered to US federal agencies. The EU Cyber Resilience Act requires manufacturers to provide SBOMs for products with digital components. Download the SBOM and provide it with your software delivery.

**Blast-radius analysis**: if a new CVE is published against a component your teams commonly use, search the SBOM across all artifacts to identify every image that contains the affected package and version. Go to [Harness Supply Chain Security](https://developer.harness.io/software-supply-chain-assurance/) for cross-registry SBOM search and policy enforcement.

**License audits**: export SBOMs for all production images and use SBOM analysis tooling to identify GPL, AGPL, or other license types that require review before shipping.

## Troubleshooting

<details>

<summary>The SBOM tab is not visible on the artifact detail page</summary>

The **SBOM** tab requires a Harness Supply Chain Security (SCS) license. If the tab does not appear, your account may not have SCS enabled. Contact your Harness account administrator to confirm your license.

</details>

<details>

<summary>The SBOM tab is visible but shows no components</summary>

This happens in one of these situations:

* Security scanning was enabled on the registry after this image was pushed. The scan pipeline did not run for existing images. Push a new version of the image to trigger a scan and generate an SBOM.
* The scan pipeline ran but has not yet completed. The HARNESS ARTIFACT SCAN PIPELINE is visible in the Harness Pipelines view for the project associated with your registry. Check the pipeline execution status.
* The registry is not a Docker or Helm registry. SBOMs are not generated for other artifact formats.

</details>

<details>

<summary>The SBOM score is low but the Vulnerabilities tab shows no CVEs</summary>

The SBOM score reflects three factors: completeness, license risk, and vulnerability exposure. A low score despite no CVEs usually means either completeness is low (some components could not be fully resolved) or at least one component carries a high-risk or unknown license. Review the component table for rows with a blank **Supplier** or an **Unknown** or **GPL** license.

</details>

## Next steps

* To view the CVE findings generated alongside the SBOM, go to [Vulnerability scanning](https://developer.harness.io/artifact-registry/3.0/security-and-compliance/vulnerability-scanning.md).
* To understand how quarantine works when a scan finds a policy violation, go to [Quarantine](https://developer.harness.io/artifact-registry/3.0/security-and-compliance/quarantine.md).
* To learn what SBOMs are and how they support supply chain security, go to [SBOM and software supply chain](https://developer.harness.io/artifact-registry/3.0/concepts/sbom-and-supply-chain.md).
* For cross-registry SBOM policy enforcement, SLSA provenance, and attestation, go to [Harness Supply Chain Security](https://developer.harness.io/software-supply-chain-assurance/).

{% @harness-feedback/feedback %}
