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

Ansible

Release lineStatusEnd of active supportEnd of lifeEnd of extended supportLatest in line
14Not end of lifeNot recordedNot recordedNot recorded14.4.0
13End of lifeNot recorded2026-06-18Not recorded13.8.0
12End of lifeNot recorded2025-12-09Not recorded12.3.0
11End of lifeNot recorded2025-12-09Not recorded11.13.0
10End of lifeNot recorded2024-12-03Not recorded10.7.0
9End of lifeNot recorded2024-12-03Not recorded9.13.0
8End of lifeNot recorded2023-12-06Not recorded8.7.0
7End of lifeNot recorded2023-06-22Not recorded7.7.0
6End of lifeNot recorded2022-12-06Not recorded6.7.0
5End of lifeNot recorded2022-06-08Not recorded5.10.0
4End of lifeNot recorded2021-12-14Not recorded4.10.0
3End of lifeNot recorded2021-05-11Not recorded3.4.0
2.10End of lifeNot recorded2021-02-09Not recorded2.10.7
2.9End of lifeNot recorded2022-05-23Not recorded2.9.27

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.