DependencyTrack /dependency-track
Dependency-Track is an intelligent Component Analysis platform that allows organizations to identify and reduce risk in the software supply chain.
★ 4,474⑂ 861👁 77⑃ 4,174● 2,857▤ 97
4,474
stars
861
forks
77
watchers
4,174
prs
2,857
issues
97
releases
README
OWASP Dependency-Track Dependency-Track is an intelligent Component Analysis platform that allows organizations to identify and reduce risk in the software supply chain. Dependency-Track takes a unique and highly beneficial approach by leveraging the capabilities of Software Bill of Materials (SBOM). [!IMPORTANT] Looking for Dependency-Track v4? v4 is in maintenance mode on the 4.14.x branch. v4 documentation: . Migrating from v4 to v5? See V5_MIGRATION.md. v4 will reach end-of-life in December 2026, ~6 months after v5 GA. Quickstart Want to kick the tires? Follow the Quickstart tutorial to get a local instance running with Docker Compose in a few minutes. Documentation User-facing documentation is rendered at and maintained in the docs repository. Contributing 1. Code of conduct 2. Contribution guidelines 3. Developer guide Community Dependency-Track is an open source project maintained by a community of contributors. Join the monthly community meeting to hear project updates, ask questions, and meet other users and maintainers. See also frontend: Frontend repository docs: Documentation repository helm-charts: Helm charts community: Community resources
Top issues
#869Propagate vulnerabilities from child project to parent38 comments · 2020-12-10#170Add support for multiple licenses35 comments · 2018-07-01#2353Add support for advisories defined in CSAF30 comments · 2023-01-06#3953MS Teams is retiring webhooks - Power Automate workflows is the new black29 comments · 2024-07-09#3293Dependency-Track NVD API mirroring for Dependency-Check29 comments · 2023-12-12#3108Add End-of-life (EOL) / End-of-support (EOS) information for components29 comments · 2023-10-17#1546Vulnerabilities not detected27 comments · 2022-04-14#2578Portfolio MS Teams Notification are not being sent24 comments · 2023-03-08
Discussions
#8013Policy filter "Limit to project versions marked as latest" has no effect in Policy Violation Audit1 comments · 2026-11-17#7950Reason CVE is not found for component with CPE1 comments · 2026-11-12#7946Dependency-Track uses NVD severity instead of Trivy's vendor severity (Red Hat) for Trivy analyzer findings - but WHY?3 comments · 2026-11-11#7816Support login via SAML 2.0 for enterprise identity providers2 comments · 2026-10-29#7737Schedule vuln-analysis task to avoid consuming sonatype credits to fast2 comments · 2026-10-22#7732eMudhra Intermediate CA Compromise0 comments · 2026-10-21#7664Include KEV status in exported files1 comments · 2026-10-13#7604Using NVD provided affectedData as fallback when no CPE is available0 comments · 2026-10-06
Latest release
5.2.1 5.2.1 2026-10-25[!IMPORTANT] Please read the upgrade notes before upgrading your instance. What's Changed Bug Fixes 🐛 Backport: Accept pipe-separated UUIDs on dependency graph path by @nscuro in https://github.com/DependencyTrack/dependency-track/pull/7745 Backport: Resolve BOM upload tokens to root workflow runs only by @nscuro in https://github.com/DependencyTrack/dependency-track/pull/7746 Backport: Skip analyzer when checking if enabled fails by @nscuro in https://github.com/DependencyTrack/dependency-track/pull/7747 Backport: Fix collection tag missing in project lookup response by @nscuro in h