Track New Vulnerabilities and License Changes Release to Release
Every new release changes the code and components inside your software. A library gets upgraded, another gets dropped, and a new one arrives with its own vulnerabilities and license terms. Many of those changes are small. A few need action before the release ships, whether that means fixing a license issue, bumping a package to a newer version, or patching a vulnerability.
Today, Manifest Cyber is launching SBOM Comparison in The Manifest Platform. Pick any two versions of a software bill of materials (SBOM) for the same asset, and Manifest shows you what changed. You see the components that were added or removed, the vulnerabilities those changes brought in or removed, and the licenses that changed as part of the release.
Why We Built This
Security, compliance, and vendor risk teams all ask the same question when a new SBOM arrives. What's different from last time? They need that answer to know which license issues to fix, which package versions to bump, and which vulnerabilities to patch before the next release goes out.
Until now, answering it meant scripts and spreadsheets. Someone exported two component lists, lined them up, and tried to identify the differences manually. That works for a small project once. It does not work for hundreds of components across every release, and it does not give a compliance team a repeatable record to show an auditor.
Now you can pick two versions of an SBOM in Manifest and see exactly what changed, so your team knows what to update before a release ships.
Why Not a Line-by-Line Comparison?
An SBOM is a long, structured file. Run two of them through a standard text diff and you get hundreds of lines of noise, such as reordered entries, new timestamps, and formatting changes. The changes that matter get buried.
Manifest's SBOM Comparison shows changes only. It instantly shows you what was added and what was removed.
How It Works
SBOM Comparison works from data Manifest maintains for every version of your software that we continuously monitor. It finds the packages that differ between the two versions and ignores the components that stayed the same.
The data is also available through the Manifest API, so teams can build comparisons into their own release checks.
What a Comparison Looks Like
Start by choosing two versions of the same asset. One is the Baseline and the other is the Comparison. Both are clearly labeled, so you always know which version is your starting point and which one is newer.
Manifest then returns a summary. At the top, you see the key details for each version, including its risk score, component count, vulnerabilities, and license issues. Below that, you see only the changes that matter, including the components, vulnerabilities, and licenses that were added or removed.
When you're done, export the full comparison as a spreadsheet to share with your team or keep for an audit.
What Comes Next
SBOM Comparison is available now in The Manifest Platform. Every release raises the same question about what's different this time. Now the answer takes a few clicks instead of a spreadsheet, so your team knows what to fix before the next release ships.





