dependency-track
5.1.1 open-sourceThe section your link pointed to isn't on dependency-track's page any more, so we've brought you to the top.
Dependency-Track is a software composition analysissoftware composition analysisSoftware composition analysis, identifying third-party dependencies and checking them for known vulnerabilities and license issues. It covers software a team uses rather than writes itself. platform that identifies and monitors vulnerabilities in application dependencies and third-party components.
curl -X POST 'https://dtrack.example.com/api/v1/bom' \ -H 'X-Api-Key: <api-key>' \ -F 'autoCreate=true' \ -F 'isActive=true' \ -F 'projectName=my-app' \ -F 'projectVersion=1.0.0' \ -F 'bom=@bom.cdx.json.gz;type=application/gzip'
Summary
Dependency-Track is an open-source component analysis platform, free to use, that identifies and reduces risk in the software supply chainsoftware supply chainThe dependencies, tools and processes used to build and deliver software. Compromising one part can affect the products or organizations that rely on it. by ingesting Software Bills of Materials rather than scanning source code directly. It runs as a self-hosted service: an API server, frontend, and Postgres database brought up together, typically via Docker Compose, with a web UI for ongoing use. This suits application security and supply-chain teams who need continuous visibility into open-source component risk across many projects rather than a one-off scan. It sits in the SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. and software composition analysis space, tracking vulnerabilities, license issues, and component metadata over the life of a project rather than at a single build step. With 258 contributors, nearly 2,000 commits in the past year, and a release 22 days ago, it is under active, well-supported development.
Dependency-Track is a software composition analysis platform that identifies and monitors vulnerabilities in application dependencies and third-party components.
How dependency-track helps
Which of my open-source dependencies have a known vulnerability?
matches component identities from uploaded SBOMs against mirrored vulnerability sources and lists every affected project with the CVE or advisory behind it
Which of my components are being actively exploited in the wild rather than just theoretically vulnerable?
flags components whose vulnerabilities appear in the CISA Known Exploited Vulnerabilities catalog and surfaces that status in policies and notifications
Which projects in my portfolio violate the standards I've set for licenses, versions, or component scope?
evaluates every uploaded SBOM against configurable policy rules and lists the violating components by project and rule
Do I still need to worry about a vulnerability my vendor already told me isn't exploitable in my product?
ingests VEX statements and reconciles their analysis and severity against what was previously recorded for that component
Which of my projects have out-of-date or stale component data I should re-check?
tracks a resolution state for each component's package metadata so projects whose dependency data never completed lookup are distinguishable from those that are current
Where do I send word when a new vulnerability shows up in something I ship?
routes findings as notifications to channels like Slack, email, or a webhook, and can forward them into external trackers such as DefectDojo with the analysis detail attached
Languages
Command line
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for dependency-track, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail dependency-track puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
dependencytrack.org, every changeOWASP's home page and 2 more pages as they looked each month from August 2021 to October 2026: 15 renders, 0 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
24 entries
No entries match these filters.
- September 20262
- August 20262
- July 20262
- June 20262
- May 20261
- April 20261
- March 20261
- November 20251
- October 20252
- August 20251
- April 20251
- February 20251
- December 20241
- October 20241
- June 20242
- May 20241
- October 20221
- August 20211
Project health
Issue, contributor and maintainer activity in DependencyTrack/dependency-track, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 35 +23 vs prior 12 months
- Maintainers 1 +0 joined · −2 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 95% of issues opened, last 12 months
- Median time to close 49 days first maintainer reply 5.9 hours
- Open backlog 991 of 2,749 issues ever filed
- Issues opened / month 24 · 0 communitymaintainers
- Open backlog 991
- Contributors / month 7
- Commits / month 44
- Stars 4,208
- bugs 60%
- features 31%
- other 9%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.