Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

OWASP Dependency-Track

dependencytrack.org

  • Free plan
  • Web
  • API
  • Self-hosted

What OWASP Dependency-Track is

OWASP Dependency-Track is a free, open-source, self-hosted platform for managing software supply-chain risk. It creates component inventories from software bills of materials, identifies vulnerabilities, and evaluates policies across projects. The system consumes, analyzes, and produces CycloneDX SBOM, HBOM, VEX, and VDR documents. It matches components against NVD, GitHub Advisories, OSV, OSS Index, Snyk, Trivy, and VulnDB, while EPSS support helps prioritize mitigation. Integrity checks flag components when published hashes differ from upstream registry hashes. A Common Expression Language policy engine can break builds when policies fail. Alerts can reach Slack, Teams, Mattermost, email, or webhooks, with event-field filters. Least-privilege portfolio access and single sign-on through OpenID Connect, Active Directory, and LDAP are supported. Version 5.1 uses separate API and frontend container images and supports Kubernetes. Version 5 requires PostgreSQL and an offline migration from 4.x.

Who it suits

It suits software teams and enterprises managing portfolios from one team to hundreds of thousands of projects. Organizations wanting self-hosted SBOM analysis, vulnerability intelligence, and policy enforcement may use it.

Good to know, and what to watch

  • Free and open source
  • Supports multiple SBOM document types
  • Matches several vulnerability intelligence sources
  • Can fail builds on policy violations
  • Supports Kubernetes and API access
  • Version 5 requires PostgreSQL
  • Version 5 cannot upgrade in place from 4.x
  • Deployment is self-hosted
  • Migration requires planned maintenance

Dependency-Track

Free

Free plan

The verdict

Dependency-Track provides broad SBOM, vulnerability, policy, and notification capabilities without a license charge. PostgreSQL and the non-in-place 4.x migration requirement are important deployment considerations.

What the maker publishes

Access and identity
The platform supports least-privilege portfolio access control and single sign-on via OpenID Connect, with Active Directory and LDAP. source
Community
The project directs users to community support through Slack, GitHub Discussions, a mailing list, and YouTube. source
Database requirement
Version 5 standardizes on PostgreSQL; H2, MySQL, and SQL Server are no longer supported. source
Deployment
Version 5.1 is distributed as separate API server and frontend container images, and Kubernetes is supported. source
Founded
2013 source
Integrations
Alerts can be routed to Slack, Teams, Mattermost, email, and webhooks, with filters based on event fields. source
Integrity checks
It flags components whose published hashes diverge from those served by the upstream registry. source
Intended users
The platform is described as serving organizations from a single team to enterprise portfolios of hundreds of thousands of projects. source
Migration limit
Version 5 does not upgrade in place from 4.x; migration uses an offline, one-time migrator and requires a planned maintenance window. source
Policies
A Common Expression Language policy engine evaluates component policies and can break the build when a policy fails. source
Purpose
Dependency-Track inventories software components from SBOMs, identifies vulnerabilities, and helps enforce policy across the software supply chain. source
Risk prioritization
Integrated EPSS support helps prioritize vulnerability mitigation. source
SBOM formats
It consumes, analyzes, and produces CycloneDX SBOM, HBOM, VEX, and VDR documents. source
Vulnerability intelligence
It matches components against the NVD, GitHub Advisories, OSV, OSS Index, Snyk, Trivy, and VulnDB. source

Checked against the maker's pages on 5 Oct 2026.