Package & SBOM Vulnerability API with Monitoring
Check a package and version against known advisories and malicious-package reports. Send one package or a whole SBOM. A result names the fixed version when the advisories give one. The tools are free without an API key and work over REST and as MCP tools, for developers and AI agents.
What you can ask
package_check. Check one package and version against OSV.dev advisories and malicious-package reports. The answer also gives the support dates of the package from endoflife.date when it maps to a product there. API docs
package_check_bulk. Check many packages with exact versions, such as the contents of an SBOM. API docs
driver_lookup. Look up a Windows driver file hash in the LOLDrivers catalog. Its detection rules are context, not for blocking. API docs
Example
curl "https://api.contrastcyber.com/package_check?ecosystem=npm&name=lodash&version=4.17.20&limit=2"Example response, trimmed; the values are an example:
{
"data_source": {"source": "osv", "available": true},
"has_advisory_data": true,
"total": 5,
"limit": 2,
"offset": 0,
"next_offset": 2,
"fixed_version": "4.18.0",
"malicious": null,
"results": [
{
"id": "GHSA-r5fr-rjxr-66jc",
"source": "ghsa",
"aliases": ["CVE-2026-4800"],
"summary": "lodash vulnerable to Code Injection via `_.template` imports key names",
"fixed_version": "4.18.0",
"affects_version": true
},
{"...": "..."}
]
}From an agent
Your agent calls these MCP tools: package_check, package_check_bulk, driver_lookup and driver_lookup_bulk. Connect once with the MCP setup, then ask in plain words.
- “Is lodash 4.17.20 vulnerable, and which version fixes it?”
- “Check every dependency in this package-lock.json for known advisories.”
- “Is this driver hash in the LOLDrivers catalog?”
Limits
Without a key you get 30 credits per hour. A Pro key gets 500 credits per hour. package_check_bulk takes up to 500 packages per request. driver_lookup_bulk takes up to 20 hashes.
Monitor it
A Pro key can watch a package. Add an item with watchlist_edit. Then read its change events with watchlist_events. You pull the events when you want them.
A package item names an ecosystem and a package name, and may name one version. It runs no scan of its own. The server writes the events when it loads the advisories. An item with a version hears an advisory event only when the advisory affects that version, or when the server cannot tell. An item without a version hears the events of every version. An event also says which advisory it comes from and, for a fix, which version fixes it. A package that maps to an endoflife.date product also hears when a release cycle nears its end, reaches it or changes its end date.
To watch a whole SBOM, call watchlist_edit with an add of a list of up to 500 packages. A remove with a list removes those packages. A package already watched is left as it is. One package that is not valid refuses the whole call, and the answer lists every such package. The call costs 1 credit.
The endpoint of the item sets the events it can emit. The two CVE events kev_added and ransomware_linked reach the item when an advisory of its package lists the CVE as an alias:
| Watched endpoint | Events |
|---|---|
package_check | advisory_added fix_available malware_added kev_added ransomware_linked eol_approaching eol_reached eol_date_changed |
See pricing for the Pro key. The security monitoring page lists every watched endpoint and its events.
Data sources
- GitHub Advisory Database, through OSV.dev: CC BY 4.0. Local copy.
- Go vulnerability database, through OSV.dev: CC BY 4.0. Local copy.
- PyPA advisory database, through OSV.dev: CC BY 4.0. Local copy.
- RustSec advisory database, through OSV.dev: CC0 1.0. An advisory may name CC BY 4.0 instead. Local copy.
- OpenSSF Malicious Packages, through OSV.dev: Apache-2.0. Local copy.
- endoflife.date: MIT. The support dates of a package, in
eol. Local copy. - LOLDrivers: Apache-2.0. Local copy.
/healthshows the sync state of each feed. Each package answer names the source and licence of its advisories and of its support dates.
FAQ
- Which package ecosystems does it check?
- npm, PyPI, Maven, Go, NuGet, RubyGems, crates.io, Packagist and SwiftURL.
- Does it find malicious packages?
- Yes. The answer includes the OpenSSF malicious-package report when one names the package.
- Can I check a whole SBOM or lockfile?
- Yes. package_check_bulk takes a list of packages, each with an ecosystem, a name and an exact version. A version range is skipped.
- How do I get the severity of an advisory?
- Take the CVE IDs from aliases and pass them to cve_triage_bulk on the CVE API page.