dependency track end of life dates — full support timeline
7 of 9 tracked dependency track releases have already reached end of life. The dates below are published support dates, not estimates.
Version support timeline
| Release | Released | End of life | Latest | Status |
|---|---|---|---|---|
| 5.0 | 2026-06-09 | not announced | 5.0.4 | supported |
| 4.14 | 2026-03-09 | 2026-12-09 | 4.14.3 | ends soon |
| 4.13 | 2025-04-07 | 2026-03-09 | 4.13.6 | ended |
| 4.12 | 2024-10-01 | 2025-04-07 | 4.12.7 | ended |
| 4.11 | 2024-05-07 | 2024-10-01 | 4.11.7 | ended |
| 4.10 | 2023-12-08 | 2024-05-07 | 4.10.1 | ended |
| 4.9 | 2023-10-16 | 2023-12-08 | 4.9.1 | ended |
| 4.8 | 2023-04-18 | 2023-10-16 | 4.8.2 | ended |
| 4.7 | 2022-12-16 | 2023-04-18 | 4.7.1 | ended |
Who is affected
Anyone running an unsupported dependency track release. After end of life a version stops receiving security patches, which typically becomes an audit or compliance finding before it becomes an outage. Upgrading to a supported release is the migration path; the table above shows which releases still qualify.
Source
These dates are maintained by endoflife.date/dependency-track, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next dependency track deadline
You are reading this because a dependency track release is losing support. The next one will arrive the same way — quietly, months before an auditor finds it. A free weekly email lists every dependency track and related deadline as it is announced, with exact dates and primary sources.
Watch dependency track deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.