CVE Monitor
Radar (CVE monitor) looks up published advisories for the packages you ship. Check a package version, keep a watch list of the packages that matter to you, and follow a threat feed that flags CISA Known Exploited Vulnerabilities.
What CVE Monitor tracks
Published advisories for a package and version across npm, PyPI, Maven, Go, Cargo and NuGet.
Add packages to a project watch list. Each one is checked against known advisories when you add it and re-checked once a day. Your organisation is notified when a watched package has new advisories.
A threat feed that flags CVEs on CISA's Known Exploited Vulnerabilities catalogue.
FIRST.org EPSS exploitation probability on findings that carry a CVE ID, refreshed daily.
The threat feed can be filtered to the entries that affect your organisation.
Each advisory that matches becomes a finding you can triage, assign and close.
From advisory to finding
- 1
Enter a package
Give the package name, ecosystem and, optionally, the version. Without a version, advisories for every version are returned.
- 2
Advisory lookup
Spoorder looks the package up in a public vulnerability database and records each matching advisory.
- 3
Prioritise with EPSS and KEV
Findings with a CVE ID are enriched with EPSS exploitation probability and KEV status, so you can start with what is being exploited.
- 4
Watch and review
Keep the packages you care about on a watch list, and choose an email notification when a scan finds something above your severity threshold.
{
"cve_id": "CVE-2021-23337",
"package": "lodash",
"ecosystem": "npm",
"installed_version": "4.17.20",
"fixed_version": "4.17.21",
"severity": "high"
}Spoorder CVE Monitor vs checking advisories by hand
| Criterion | Spoorder | checking advisories by hand |
|---|---|---|
| Prioritisation | EPSS and CISA KEV alongside severity | CVSS only |
| Watch list | Per-project package watch list | Manual searches |
| Tracking | Advisories become findings you can triage | A list of links |
| Compliance mapping | Counts as evidence for framework controls | Separate manual step |
Which ecosystems does CVE Monitor cover?
npm, PyPI, Maven, Go, Cargo and NuGet from the dashboard.
What is EPSS and how does it differ from CVSS?
CVSS rates how severe a vulnerability could be. EPSS (Exploit Prediction Scoring System), published by FIRST.org, estimates the probability that a CVE will be exploited in the wild within the next 30 days. Used together, they help you fix what is both serious and likely to be attacked.
What is the CISA KEV list and why does it matter?
The CISA Known Exploited Vulnerabilities catalogue lists CVEs that are confirmed to be exploited in real attacks. Spoorder flags findings on the KEV list and puts them at the top of the priority order.
How is this different from SCA?
SCA scans all the dependencies in a repository or manifest at one point in time. CVE Monitor checks the specific packages you name and keeps them on a watch list. Watched packages are checked when you add them and re-checked once a day, and your organisation is notified of new advisories.
What plan and credits does it need?
CVE Monitor is included from the Pro plan ($199/mo). A lookup costs 2 credits.
Start scanning
Start with a free health check. CVE Monitor is included from Pro ($199/mo).