← ← Back to all products
Dependency-Track
Active
Tools & Monitoring Latest Version: 4.13.6 Latest Release: Nov 17, 2025
Dependency-Track is an intelligent software composition analysis platform for identifying component risks.
Versions
7
Latest Version
4.13.6
Active Support
1
EOL
6
Lifecycle Timeline
Today ↓
4.13
4.13
4.12
4.12
4.11
4.11
4.10
4.10
4.9
4.9
4.8
4.8
4.7
4.7
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 4.13 | Apr 7, 2025 | - | No | 4.13.6 | No | Active |
| 4.12 | Oct 1, 2024 | - | Apr 7, 2025 | 4.12.7 | No | EOL |
| 4.11 | May 7, 2024 | - | Oct 1, 2024 | 4.11.7 | No | EOL |
| 4.10 | Dec 8, 2023 | - | May 7, 2024 | 4.10.1 | No | EOL |
| 4.9 | Oct 16, 2023 | - | Dec 8, 2023 | 4.9.1 | No | EOL |
| 4.8 | Apr 18, 2023 | - | Oct 16, 2023 | 4.8.2 | No | EOL |
| 4.7 | Dec 16, 2022 | - | Apr 18, 2023 | 4.7.1 | No | EOL |
Frequently Asked Questions
Which versions of Dependency-Track have reached end of life?
The following Dependency-Track versions have reached end of life and no longer receive security updates: 4.12, 4.11, 4.10, 4.9, 4.8, 4.7. It is recommended to upgrade to a supported version.
Is it safe to continue using Dependency-Track 4.12?
Dependency-Track 4.12 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Dependency-Track?
The latest version of Dependency-Track is 4.13.6, released in the 4.13 release cycle.
How many versions of Dependency-Track are currently supported?
Dependency-Track currently has 1 actively supported version(s): 4.13.
When does Dependency-Track 4.13 reach end of life?
Dependency-Track 4.13 does not have a specific end-of-life date announced yet.
What should I do when Dependency-Track reaches end of life?
When a Dependency-Track version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.