SCA
Supply (Dependencies) checks the dependencies in a repository or a pasted manifest for known CVEs. Each finding shows the fixed version, EPSS exploitation probability and CISA KEV status, so you can fix the riskiest packages first.
What SCA covers
Each package version is looked up in public vulnerability databases.
Repository scans resolve the whole dependency tree, including indirect dependencies.
Flags copyleft licences such as GPL and AGPL, and packages with no declared licence.
Each CVE shows the fixed version when one exists.
FIRST.org EPSS exploitation probability and CISA Known Exploited Vulnerabilities status on each CVE.
A CycloneDX or SPDX SBOM built from your dependency scans.
GitHub pull requests that bump a vulnerable dependency to its fixed version.
Rules that accept risk automatically on findings that match your policy, for example low EPSS with no fix available.
In repository scans, checks whether a vulnerable package is actually imported in your source code.
From manifest to report
- 1
Manifest detection
Repository scans detect package-lock.json, yarn.lock, Pipfile.lock, go.sum, pom.xml, Cargo.lock, Gemfile.lock and more. You can also paste a single manifest.
- 2
Dependency resolution
Direct and transitive dependencies are resolved in repository mode. Dev dependencies are optional.
- 3
Vulnerability lookup
Each package version is checked for known CVEs, then enriched with EPSS and KEV data.
- 4
Report and SBOM
Findings list the affected package, severity and fixed version. Export the inventory as a CycloneDX or SPDX SBOM.
{
"dependencies": {
"lodash": "4.17.20",
"axios": "0.21.1"
}
}Spoorder SCA vs a basic dependency checker
| Criterion | Spoorder | a basic dependency checker |
|---|---|---|
| Transitive analysis | Resolved in repository scans | Direct dependencies only |
| Prioritisation | EPSS and CISA KEV on each CVE | CVSS only |
| Licence flags | Copyleft and unlicensed packages | Not included |
| SBOM formats | CycloneDX and SPDX | Not included |
| AutoTriage rules | Rules by EPSS, reachability, fix availability and age | Manual triage only |
| AutoFix PRs | Dependency bump PRs on GitHub | Manual upgrade |
Which package ecosystems does SCA support?
npm, PyPI, Maven, Go modules, RubyGems, Cargo and NuGet. Repository scans detect lock files such as package-lock.json, yarn.lock, Pipfile.lock, go.sum, pom.xml, Cargo.lock and Gemfile.lock.
What is EPSS and why does it matter?
The Exploit Prediction Scoring System (EPSS), published by FIRST.org, estimates the probability that a CVE will be exploited within the next 30 days. Spoorder shows EPSS on each CVE so your team can fix the highest real-world risk first, rather than the highest CVSS score.
Can I generate an SBOM for procurement or compliance?
Yes. Generate a CycloneDX 1.7 or SPDX 2.3 SBOM from a project's dependency scans and download it from Outputs in the dashboard.
Does SCA flag dev-only dependencies?
Dev dependencies are left out by default. Turn on "Include dev dependencies" in a repository scan to check them too.
How are licence issues detected?
In repository scans with licence checks turned on, Spoorder flags packages under copyleft licences such as GPL and AGPL, and packages with no declared licence. Licences are read from package-lock.json and the manifest files, and looked up on deps.dev where they do not state one.
Start scanning
Start with a free health check. SCA is included from Builder ($69/mo).