Dependency vulnerability scanner
Check your software dependencies for known vulnerabilities. Upload SBOM files, package manifests, or use our API for automated supply chain security.
Everything you need to protect your infrastructure and users
Upload SPDX or CycloneDX files for vulnerability analysis.
Support for npm, pip, Maven, NuGet, and more.
Analyze nested dependencies throughout your tree.
Accurate vulnerability matching using CPE and package DBs.
Get specific version upgrade recommendations.
Fail builds when critical vulnerabilities are found.
How security teams use this tool
Check dependencies before deploying to production.
Audit third-party components in your applications.
Integrate security checks into CI/CD pipelines.
Meet software supply chain security requirements.
A Software Bill of Materials (SBOM) is a comprehensive inventory of all components, libraries, and dependencies that make up a software application. Like an ingredient list for food products, SBOMs provide transparency into what's actually running in your systems. Modern applications rely on hundreds or thousands of open-source packages, each potentially containing vulnerabilities. The SolarWinds and Log4j incidents demonstrated how supply chain vulnerabilities can have devastating consequences. SBOM analysis is now essential for software security.
Our SBOM checker analyzes your software dependencies to identify known vulnerabilities: 1. **Parse SBOM/Manifest**: We support SPDX, CycloneDX, and common package formats (package.json, requirements.txt, Gemfile.lock, pom.xml, etc.) 2. **Resolve Dependencies**: We build a complete dependency tree including transitive (nested) dependencies that your direct packages rely on. 3. **Match Against CVEs**: Each package version is matched against vulnerability databases including NVD, OSV.dev, and vendor advisories. 4. **Prioritize Findings**: Results are sorted by severity and exploitability to highlight the most critical issues. 5. **Recommend Fixes**: We identify the minimum version upgrade needed to resolve each vulnerability.
Direct dependencies are only part of the picture. A typical Node.js application might have 50 direct dependencies but over 1,000 transitive dependencies. The infamous Log4j vulnerability (CVE-2021-44228) affected countless applications that didn't directly use Log4j but included it through other packages. Our SBOM checker analyzes the entire dependency tree to find vulnerabilities at any depth. You might be surprised to discover vulnerable packages you didn't know your application included.
The best time to catch vulnerable dependencies is before deployment. Our API and CLI tools enable: - **Build-Time Checks**: Fail builds when critical vulnerabilities are detected - **Pull Request Comments**: Automatic vulnerability reports on dependency changes - **Baseline Management**: Track and acknowledge known vulnerabilities - **Policy Enforcement**: Define acceptable risk thresholds by severity - **Compliance Reporting**: Generate reports for auditors showing dependency analysis Shift-left security means catching vulnerabilities during development, not in production.
Regulatory and industry requirements increasingly mandate software supply chain security: - **Executive Order 14028**: Requires SBOMs for software sold to the U.S. federal government - **PCI DSS 4.0**: Requires inventory of bespoke and custom software - **FDA Cybersecurity Requirements**: Mandates SBOMs for medical device software - **EU Cyber Resilience Act**: Will require vulnerability handling for products in the EU market Our SBOM checker helps organizations meet these requirements by providing comprehensive dependency analysis and vulnerability documentation.
Learn more from our security research blog
Join thousands of security teams using isMalicious to protect their infrastructure.