Dependency-Track End of Life Dates
Release, end of support and end of life dates for every tracked Dependency-Track version, with current status.
All products · Vendor release notes · Source entry
Status as of 2026-09-23 (UTC): 10 versions tracked; 1 supported, 0 security fixes only, 1 ending within 90 days, 8 end of life.
| Version | Status | Released | Support ends | Latest |
|---|---|---|---|---|
| 5.1 | Supported | 2026-08-27 | Not announced | 5.1.1 |
| 5.0 | End of life | 2026-06-09 | 2026-08-27 | 5.0.5 |
| 4.14 | Ends within 90 days (77 days left) | 2026-03-09 | 2026-12-09 | 4.14.4 |
| 4.13 | End of life | 2025-04-07 | 2026-03-09 | 4.13.6 |
| 4.12 | End of life | 2024-10-01 | 2025-04-07 | 4.12.7 |
| 4.11 | End of life | 2024-05-07 | 2024-10-01 | 4.11.7 |
| 4.10 | End of life | 2023-12-08 | 2024-05-07 | 4.10.1 |
| 4.9 | End of life | 2023-10-16 | 2023-12-08 | 4.9.1 |
| 4.8 | End of life | 2023-04-18 | 2023-10-16 | 4.8.2 |
| 4.7 | End of life | 2022-12-16 | 2023-04-18 | 4.7.1 |
Note: "Not announced" means the vendor has not published a date. "Ended (no date published)" means the source marks it ended without a date. Dates are compared as calendar days in UTC, so a date can flip up to a day earlier or later than your local calendar.
Data: endoflife.date (MIT license), snapshot 2026-09-23. Dates come from each vendor's published lifecycle. Always confirm with the vendor link before a purchase or migration decision.