Complete end-of-life dates, support windows, and security status for all Protractor versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.8.0 | Jul 21, 2014 | Aug 31, 2023 | 982 days past EOL | EOL |
| 2.0 | 2.5.1 | Mar 18, 2015 | Aug 31, 2023 | 982 days past EOL | EOL |
| 3.0 | 3.3.0 | Nov 18, 2015 | Aug 31, 2023 | 982 days past EOL | EOL |
| 4.0 | 4.0.14 | Jul 12, 2016 | Aug 31, 2023 | 982 days past EOL | EOL |
| 5.0 | 5.4.4 | Jan 10, 2017 | Aug 31, 2023 | 982 days past EOL | EOL |
| 6.0 | 6.0.0 | Mar 23, 2019 | Aug 31, 2023 | 982 days past EOL | EOL |
| 7.0 | 7.0.0 | May 13, 2020 | Aug 31, 2023 | 982 days past EOL | EOL |
When a Protractor 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 Protractor 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 →