Complete end-of-life dates, support windows, and security status for all Pangp versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 3.0 | 3.0 | Feb 16, 2016 | Feb 15, 2018 | 3005 days past EOL | EOL |
| 3.1 | 3.1 | Jun 23, 2016 | Jun 23, 2018 | 2877 days past EOL | EOL |
| 4.0 | 4.0 | Jan 30, 2017 | Jan 30, 2019 | 2656 days past EOL | EOL |
| 4.1 | 4.1.13 | Mar 1, 2018 | Mar 1, 2020 | 2260 days past EOL | EOL |
| 5.0 | 5.0.10 | Feb 12, 2019 | Feb 12, 2021 | 1912 days past EOL | EOL |
| 5.1 | 5.1.12 | Dec 12, 2019 | Dec 31, 2024 | 494 days past EOL | EOL |
| 5.2 | 5.2.13-c418 | Jul 30, 2020 | Feb 28, 2024 | 801 days past EOL | EOL |
| 5.3 | 5.3.4 | Jun 1, 2021 | Jun 1, 2023 | 1073 days past EOL | EOL |
| 6.0 | 6.0.12 | Feb 22, 2022 | Dec 31, 2025 | 129 days past EOL | EOL |
| 6.1 | 6.1.5 | Sep 1, 2022 | Dec 31, 2025 | 129 days past EOL | EOL |
| 6.2 | 6.2.8-c910 | May 23, 2023 | Jun 30, 2027 | 417 days remaining | Active |
| 6.3 | 6.3.3-c915 | Jun 13, 2024 | Jun 30, 2028 | 783 days remaining | Active |
When a Pangp version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Pangp should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →