Dependency health lifecycles

Published support dates

Product lifecycles

Know when support ends, before it becomes an emergency.

473 products · Daily refresh at 02:30 UTC
Last successful collection: 2026-09-11 15:31 UTC
Source snapshot: 2026-09-11 14:51 UTC

Erlang

Release lineStatusEnd of active supportEnd of lifeEnd of extended supportLatest in line
29Not end of lifeNot recorded2029-05-11Not recorded29.0.6
28Not end of life2026-05-112028-05-20Not recorded28.5.0.6
27Not end of life2025-05-202027-05-20Not recorded27.3.4.17
26End of life2024-05-172026-05-26Not recorded26.2.5.21
25End of life2023-05-152025-05-17Not recorded25.3.2.21
24End of life2022-05-172024-05-10Not recorded24.3.4.17
23End of life2021-05-102024-03-14Not recorded23.3.4.20
22End of life2020-05-112024-03-18Not recorded22.3.4.27
21End of life2019-05-102021-06-19Not recorded21.3.8.24
20End of life2018-06-192020-06-21Not recorded20.3.8.26
19End of life2017-06-212019-06-21Not recorded19.3.6.13
18End of life2016-06-212018-11-09Not recorded18.3.4.11
17End of life2015-06-232018-10-11Not recorded17.5.6.10

endoflife.date evidence ↗ · Maintainer policy ↗

Extended support may require a paid agreement. A recorded date does not establish your entitlement. Missing dates do not mean indefinite support; a maintained product can still have unsupported release lines.

Source: endoflife.date · MIT licence. Data is normalised for display. Published lifecycle evidence is separate from our inferred package-maintenance verdicts and vulnerability checks. Product coverage does not imply that every package or SBOM component has a verified product mapping.