DeprecateWatch

Dependency-Track — support and end-of-life dates

Dependency-Track 5.2 is the current release, released 2026-10-08, with no end-of-life date published upstream.

Direct answer

Dependency-Track 5.2 has no published end-of-life date. Newest supported cycle: 4.14 (latest 4.14.6). Data as of 2026-11-18.

All tracked cycles

CycleReleasedActive support endsEnd of life (EOL)LatestStatus
5.22026-10-08—not announced5.2.1No EOL date
5.12026-08-27—2026-10-08
41 days ago
5.1.2End of life
5.02026-06-09—2026-08-27
83 days ago
5.0.5End of life
4.142026-03-09—2026-12-09
in 21 days
4.14.6Supported
4.132025-04-07—2026-03-09
254 days ago
4.13.6End of life
4.122024-10-01—2025-04-07
590 days ago
4.12.7End of life
4.112024-05-07—2024-10-01
778 days ago
4.11.7End of life
4.102023-12-08—2024-05-07
925 days ago
4.10.1End of life
4.92023-10-16—2023-12-08
1076 days ago
4.9.1End of life
4.82023-04-18—2023-10-16
1129 days ago
4.8.2End of life
4.72022-12-16—2023-04-18
1310 days ago
4.7.1End of life

Upgrade path stated in the data

This is not a recommendation from DeprecateWatch. It repeats what the upstream source states, plus the newest cycle that is still inside its published support window.

Questions this page answers

Is Dependency-Track 5.2 end of life?

No. Dependency-Track 5.2 has no published end-of-life date in the source data.

What is the newest supported version of Dependency-Track?

Dependency-Track 4.14 (latest release 4.14.6), released 2026-03-09, with end of life on 2026-12-09.

How many Dependency-Track versions are already end of life?

9 of the 11 cycles tracked here have passed their EOL date as of 2026-11-18.

Other Server applications with upcoming deadlines

Source for the cycle table: endoflife.date/dependency-track read through the endoflife.date API on 2026-11-18. Machine-readable copy: /api/eol.json (product key dependency-track).