Privacy & Compliance

SBOM Privacy Studio

All tools

Read a CycloneDX or SPDX SBOM locally and optionally check its packages against OSV.

How it works

Four simple steps

1

Paste CycloneDX or SPDX JSON

The SBOM file is parsed entirely in your browser.

2

Review components & licenses

Search purls, types, and license rollups locally.

3

Optional OSV scan

Only package URLs leave the device when you opt in.

4

Download a privacy receipt

Prove what was processed and which PURLs were queried.

SBOM Privacy Studio

About SBOM Privacy Studio

A customer's security questionnaire asks for your software bill of materials and its known vulnerabilities, and the SBOM file lists internal service names you would rather not upload to a random viewer. You still need a readable summary. SBOM Privacy Studio gives you one without sending the file anywhere.

Paste an SBOM in JSON and click Analyse. CycloneDX is detected from bomFormat or a components array, and SPDX from spdxVersion or a packages array. The report lists the format and spec version, the number of components, how many have a package URL (PURL), a count of each license, and every component's name, version, type, PURL and licenses. CycloneDX licenses are read from license ids, names or expressions; SPDX uses licenseConcluded and skips NOASSERTION.

Scan OSV is opt-in. Tick the consent box and the tool sends the PURLs, in batches of 50, to the public OSV.dev API and reports which packages have known advisories. Only package coordinates leave your browser, never the file. Components without a PURL cannot be checked, so a low PURL count is worth fixing in your SBOM generator. Only top-level components are read, so nested CycloneDX components are not included. A clean OSV result is not a security sign-off; review findings with your security team.

The Receipt button records what was processed and which PURLs were queried. The receipt format walkthrough explains the fields, the Privacy Receipt Builder makes simpler ones, and other local tools are on the privacy tools hub.

Keyboard shortcut

Ctrl Enter - Run tool
FAQ

Frequently asked questions

See all FAQs

Answers for this tool. For site-wide help, open the FAQ hub.

No. Only JSON is parsed. Most generators can output CycloneDX or SPDX as JSON with a flag, which is the easiest route if you currently produce XML or tag-value files.

Either the SBOM did not record them, or the SPDX license was NOASSERTION, which the tool skips. Rerun your generator with license detection enabled to fill the gaps.

OSV can only match components that have a PURL, and the ecosystem must be one OSV tracks. Private packages and components identified only by name and version will not return results.

View more FAQs

Related tools

View all

PII Detector

Scan text for emails, phones, and card-like patterns locally.

Open

On-Device NER Redactor

Redact PII with regex plus optional on-device NER - nothing uploaded.

Open

Image OCR

Extract text from images with Tesseract.js in your browser.

Open

Receipt Verifier

Validate a OneDevToolkit privacy receipt JSON file structure.

Open

Explore 321 free tools

Everything you need as a developer, marketer or creator - in one beautiful place.

Browse all tools