PAGES
← all tools
◆ Software Supply Chain Security

dependency-track

5.1.1 open-source

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.

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

all 15 features, with the evidence for each →

Languages

Not documented

Features

15 capabilities · 1 backed by code, an API document or a real run

Built from dependency-track's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • dependency-track covers 1 of the 5 supply chain security capabilities we track.

What dependency-track offers you

  • REST API2
  • Command-line interface
All capabilities 15 capabilities
Vulnerability data sources shipped Enriches vulnerability data by looking up aliases from VulnDB, GHSA, and OSS-Fuzz. 9 releases · first seen May 2024

release 9 total

  • Adds an option to use Snyk's per-package endpoint when batching is not available 5.1.1 · Sep 2026 · source · release history
  • Adds Checkmarx SCA as a vulnerability analyser. 5.1.0 · Aug 2026 · source · release history
  • Adds Checkmarx SCA as a new vulnerability data source analyzer 5.1.0 · Aug 2026 · source · release history
  • Adds REST API endpoints to view and trigger KEV (CISA Known Exploited Vulnerabilities) mirroring runs. 5.1.0 · Aug 2026 · source · release history
  • Adds JVN (Japan Vulnerability Notes) as a vulnerability data source. 5.1.0 · Aug 2026 · source · release history
  • Adds JVN (Japan Vulnerability Notes) as a new vulnerability data source 5.1.0 · Aug 2026 · source · release history
SBOM ingestion support shipped Ingests CycloneDX BOMs for project analysis, supporting schema validation and version updates including v1.6. 8 releases · 1 other source · first seen Aug 2021

Shared capability: CycloneDX SBOM

release 8 total

  • Adds CycloneDX 1.7 format support for BOM generation and processing. 4.14.4 · Sep 2026 · source · release history
  • Adds isActive parameter to the BOM upload API to control whether projects are activated during upload 5.1.0 · Aug 2026 · source · release history
  • Adds isActive parameter to the BOM upload API endpoint, allowing projects to be marked active or inactive at upload time. 5.1.0 · Aug 2026 · source · release history
  • Support for CycloneDX Scope Data in BOM upload 4.14.0 · Mar 2026 · source · release history
  • Bump SPDX license list to 3.27.0 4.13.5 · Oct 2025 · source · release history
  • Support ingestion of CycloneDX v1.6 BOMs 4.12.0 · Oct 2024 · source · release history

docs

  • Component analysis platform that identifies and reduces software supply chain risk by leveraging Software Bill of Materials (SBOM).
Notification system shipped Sends notifications for events like BOM validation failures and allows testing the notification publisher. 8 releases · first seen Aug 2021

release 8 total

  • Improves Jira Perform Test notification logging and status handling. 4.14.4 · Sep 2026 · source · release history
  • Adds protobuf publishing option for webhook notifications to support Protobuf-formatted payloads instead of JSON 5.1.0 · Aug 2026 · source · release history
  • Adds protobuf as a publishing option for webhook notifications. 5.1.0 · Aug 2026 · source · release history
  • Add lastVulnerabilityAnalysis to project 4.13.0 · Apr 2025 · source · release history
  • Add support for scheduled summary notifications 4.13.0 · Apr 2025 · source · release history
  • Add Notification for BOM_VALIDATION_FAILED events 4.12.0 · Oct 2024 · source · release history
Project and policy tagging shipped Provides bulk tagging and untagging capabilities for projects and policies via REST endpoints. 7 releases · first seen Oct 2024

Also counts toward: REST API

release 7 total

  • Adds component scope evaluation policy to allow evaluating vulnerability policies against specific components within a project 5.1.0 · Aug 2026 · source · release history
  • Aligns VEX semantics with CISA guidance and tooling ecosystem. 5.1.0 · Aug 2026 · source · release history
  • Add endpoint to mass-create tags 4.13.0 · Apr 2025 · source · release history
  • Add REST endpoints for bulk tagging & un-tagging of projects (POST /api/v1/projects/tags, DELETE /api/v1/projects/tags) 4.12.0 · Oct 2024 · source · release history
  • Add REST endpoint for tag deletion (DELETE /api/v1/tag/{uuid}) 4.12.0 · Oct 2024 · source · release history
  • Add REST endpoint for tag retrieval (GET /api/v1/tag) 4.12.0 · Oct 2024 · source · release history
Workflow activity execution control shipped Enforces timeouts on workflow activities and supports automatic heartbeating to keep long-running activities alive. 7 releases · first seen Mar 2026

release 7 total

  • Exposes workflow run status on the BOM token polling endpoint. 5.1.0 · Aug 2026 · source · release history
  • Enforces execution timeouts for workflow activities with a defined default, preventing runaway background tasks. 5.0.4 · Jul 2026 · source · release history
  • Enables automatic heartbeating for long-running activities to prevent premature timeout detection. 5.0.4 · Jul 2026 · source · release history
  • Adds dex.activity.execution.timeout config key to define default activity execution timeout 5.0.4 · Jul 2026 · source · release history
  • Backport: Add age and version distance to operational policy criteria 4.14.1 · Apr 2026 · source · release history
  • Backport: Support Sonatype Guide tokens for OSS Index analyzer 4.14.1 · Apr 2026 · source · release history
Maintenance and cleanup operations shipped Runs background maintenance cycles that execute multiple deletion batches and support configurable query timeouts to tune cleanup throughput. 7 releases · first seen Oct 2024

release 7 total

  • Executes multiple deletion batches per maintenance cycle, increasing throughput for cleanup operations. 5.0.4 · Jul 2026 · source · release history
  • Makes DEX query timeout configurable for tuning background task responsiveness. 5.0.4 · Jul 2026 · source · release history
  • Adds dex.timeout.query config key to make dex query timeout configurable 5.0.4 · Jul 2026 · source · release history
  • Backport: Allow out-of-order execution of Flyway migrations to accommodate custom or delayed database schema changes. 5.0.1 · Jun 2026 · source · release history
  • Backport: v4-migrator now supports TCP keepalive and optional socket timeout for better connection stability during migration. 5.0.1 · Jun 2026 · source · release history
  • Add /v1/project/batchDelete API method that deletes with SQL 4.13.0 · Apr 2025 · source · release history
CWE dictionary lookup verified Looks up entries in a CWE dictionary by package name and dictionary version. 5 releases · 2 other sources · first seen May 2024

release

  • Backport: Support Sonatype Guide tokens for OSS Index analyzer 4.14.1 · Apr 2026 · source · release history
  • Configurable base URL for OSS Index API via environment variable or config 4.14.0 · Mar 2026 · source · release history
  • Validate uploaded BOMs against the CycloneDX schema during import 4.11.0 · May 2024 · source · release history
  • Store computed severities in the database for persistence across restarts 4.11.0 · May 2024 · source · release history
  • Look up vulnerabilities using VulnDB aliases (e.g., GHSA, OSS-Fuzz IDs) in addition to standard CPEs/PURLs 4.11.0 · May 2024 · source · release history

command line

Portfolio and project configuration shipped Supports configurable welcome messages, system-wide default locale, team-based portfolio ACLs, and latest-version policy targeting. 6 releases · first seen Oct 2024

release

  • Add project filters to component identity search allows scoping the search results by specific projects. 4.14.2 · May 2026 · source · release history
  • Introduce collection projects for better usage of hierarchical view 4.13.0 · Apr 2025 · source · release history
  • Support configuration of teams for portfolio ACL when creating a project 4.12.0 · Oct 2024 · source · release history
  • Support customizable welcome message on the login page 4.12.0 · Oct 2024 · source · release history
  • Add isLatest project flag and allow policies to be limited to latest version only 4.12.0 · Oct 2024 · source · release history
  • Add support for configurable system-wide default locale 4.12.0 · Oct 2024 · source · release history
DefectDojo integration configuration shipped Configures the DefectDojo integration, including control of verified flags and custom test titles. 5 releases · first seen Apr 2025

release

  • Adds component scope evaluation policy to allow evaluating vulnerability policies against specific components within a project 5.1.0 · Aug 2026 · source · release history
  • Adds group_by parameter forwarding to DefectDojo (v5) integration. 5.1.0 · Aug 2026 · source · release history
  • Includes analysis.detail in the DefectDojo finding payload for richer context 4.14.3 · Jul 2026 · source · release history
  • Add property to control verified flag in DefectDojo integration 4.13.0 · Apr 2025 · source · release history
  • Add feature to define the test title for DefectDojo integration 4.13.0 · Apr 2025 · source · release history
Dependency analysis sources shipped Analyzes dependencies from Hackage and Nixpkgs ecosystems. 4 releases · first seen May 2024

release

  • Extends distro-aware version matching with Red Hat support. 5.1.0 · Aug 2026 · source · release history
  • Backport: Add support for NuGet versioning scheme 4.14.1 · Apr 2026 · source · release history
  • Migrates the dependency analysis engine to use NVD 2.0 data feeds instead of the previous CVE data source format. 4.13.4 · Aug 2025 · source · release history
  • Analyze Hackage and Nixpkgs dependencies by leveraging the new hackage and nixpkgs meta analyzers 4.11.0 · May 2024 · source · release history
Project metadata enrichment shipped Supports the authors field in CycloneDX BOMs and exposes active status for project versions. 4 releases · first seen Aug 2021

Shared capability: CycloneDX SBOM

release

  • Mandates container-based distribution; WAR file deployment is no longer supported 5.0.0 · Jun 2026 · source · release history
  • Add support for authors field in CycloneDX BOMs 4.12.0 · Oct 2024 · source · release history
  • Add active field to Project Versions in API responses 4.12.0 · Oct 2024 · source · release history
  • Adds GET /api/v1/project/{uuid}/metadata endpoint to retrieve metadata for a project's components. 4.3.0 · Aug 2021 · source · release history
KEV (Known Exploited Vulnerabilities) support shipped Ingests and mirrors KEV data, exposes it in policy evaluation and metrics, and provides mirroring control endpoints. 2 releases · first seen Aug 2026

Also counts toward: REST API

release

  • Adds REST API endpoints to view and trigger KEV (CISA Known Exploited Vulnerabilities) mirroring runs. 5.1.0 · Aug 2026 · source · release history
  • Adds KEV dimension to time series metrics. 5.1.0 · Aug 2026 · source · release history
Telemetry collection shipped Collects basic usage and operational telemetry data from the cyber tooling. 2 releases · first seen Apr 2025

release

  • Backport: Support non-UTC timezones for metrics operations, allowing accurate time-based metric calculations in any region. 5.0.1 · Jun 2026 · source · release history
  • Implement basic telemetry collection 4.13.0 · Apr 2025 · source · release history
Workflow task scheduling shipped Schedules workflow tasks using concurrency keys to improve performance when large backlogs are present. 1 release · first seen Jul 2026

release

  • Improves workflow task scheduling performance for deep backlogs using concurrency keys. 5.0.4 · Jul 2026 · source · release history
Container image variants shipped Distributes optimized container images for deploying the cyber tool, including lightweight Alpine-based variants. 1 release · first seen Nov 2025

release

  • Adds Alpine-based container variants for Dependency Track 4.13.6 · Nov 2025 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. 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 →

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…

Explore the full chart →

Website history

dependencytrack.org, every change

OWASP'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 →

Releases

Show

24 entries

  1. September 20262
  2. August 20262
  3. July 20262
  4. June 20262
  5. May 20261
  6. April 20261
  7. March 20261
  8. November 20251
  9. October 20252
  10. August 20251
  11. April 20251
  12. February 20251
  13. December 20241
  14. October 20241
  15. June 20242
  16. May 20241
  17. October 20221
  18. August 20211
    Show

    24 entries

    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.

    1. Contributors 35 +23 vs prior 12 months
    2. Maintainers 1 +0 joined · −2 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 95% of issues opened, last 12 months
    5. Median time to close 49 days first maintainer reply 5.9 hours
    6. Open backlog 991 of 2,749 issues ever filed
    1. Issues opened / month 24 · 0 communitymaintainers
    2. Open backlog 991
    3. Contributors / month 7
    4. Commits / month 44
    5. Stars 4,208
    Issue themes, last 12 months
    • 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.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →