Chef InSpec End of Life (EOL) Dates and End of Support (EOS) Dates
Chef InSpec end of life (EOL) and end of support (EOS) dates: 5 Chef InSpec versions have reached EOL, including Chef InSpec 5 (EOL date: Oct 16, 2025) — no longer receiving security updates or patches. Chef InSpec 7.3.4 is the current supported release — 2 versions in active support. Also see Docker Engine EOSL dates for related end-of-life information.
Currently Supported Chef InSpec Releases - Active EOS/EOSL Support (2)
Chef InSpec End of Life (EOL) Releases - No Longer Supported (5)
| Release | Released | Security Support | Active Support | Latest |
|---|---|---|---|---|
| 5 | (4 years and 8 months ago) | (1 year and 1 month ago) | (3 years ago) | 5.24.24 (4 months ago) |
| 4 | (7 years and 6 months ago) | (3 years ago) | (4 years and 8 months ago) | 4.56.58 (3 years ago) |
| 3 | (8 years and 1 month ago) | (6 years and 6 months ago) | (7 years and 6 months ago) | 3.9.3 (7 years and 7 months ago) |
| 2 | (8 years and 8 months ago) | (6 years and 10 months ago) | (8 years and 1 month ago) | 2.3.28 (7 years and 9 months ago) |
| 1 | (10 years and 1 month ago) | (6 years and 10 months ago) | (8 years and 8 months ago) | 1.51.31 (7 years and 8 months ago) |
Planning around Chef InSpec end of life starts with one fact: InSpec 7.x is the only generally available version, 5.x and 6.x are deprecated, and every release at 4.x or below has already reached EOL. Below you will find each line's support status, the dates that matter and the next step for your infrastructure.
Chef InSpec EOL Dates by Version
Progress Chef publishes the official EOL date for each release on its supported versions page. For this compliance framework, the schedule looks like this:
| InSpec release line | Lifecycle stage | EOL date |
|---|---|---|
| 7.x | Generally available | None announced |
| 5.x and 6.x | Deprecated | August 31, 2027 |
| 4.x and under | End of life | July 31, 2026 |
Chef notes that every future date in these tables is subject to change, so recheck the documentation before you lock a plan.
Generally Available: InSpec 7.x
InSpec 7 arrived on 16 October 2025, and the latest release at the time of writing is 7.3.4, published on 9 October 2026. It receives active support, bug fixes and security fixes, and Chef lists no deprecation for it.
Deprecated Chef InSpec Versions 5.x and 6.x
A deprecated line is no longer in active development. Chef still honours its support SLAs and may ship a patch for a critical defect, but scheduled releases stop. The replacement is InSpec 7.x.
The community tracker endoflife.date shows a tighter picture than Chef's own table. Active support for 6.x ended on 16 October 2025, though it keeps security support, with 6.8.24 as its last build. The 5.x line lost both on that same day, and 5.24.24 is its final build. Treat the Chef dates as the contractual limit, and the tracker as an early warning.
Chef InSpec EOL Lifecycle Stage Definitions
Chef places each product in one of three lifecycle stages:
- Generally available (GA): in active development and maintenance, with releases for customer needs and vulnerabilities.
- Deprecated: no scheduled releases, but support continues under the SLAs until the end-of-life date.
- End of life: a date after which the version is neither supported nor recommended.
Long-Term Support and N-1 Support
Chef follows a long-term support model, and InSpec appears to follow an N-1 support pattern. The latest release gets bug and security fixes, while the previous one is marked deprecated and keeps only security support. Run one of the supported release numbers and you stay inside that window.
What Chef InSpec End of Life Means for Security and Compliance
InSpec is an open-source framework for compliance as code: it lets you audit and test the state of your infrastructure against policy. Once your release reaches EOL, it keeps running, but nothing keeps it current.
Security Fixes Stop at the Cutoff
An unmaintained version receives no CVE patches, so every new vulnerability stays open. Compliance risk follows, because auditors flag outdated components, and your scans depend on Ruby libraries nobody updates. Expect that risk to grow the longer you wait.
Migration Plan Before the InSpec EOL Date
A calm upgrade beats a rushed one. Work through these steps:
- Run
inspec versionon your hosts and CI runners to inventory every release in use. - Upgrade your profiles to 7.x and rerun your testing pipeline.
- Fix controls that break, then replace any remaining 4.x runners first, since they are already past EOL.
- Schedule 5.x and 6.x moves well ahead of August 31, 2027.
Chef 360 Platform as the Replacement Product
If you need more than a client upgrade, the Chef 360 Platform brings infrastructure, compliance, policy and orchestration together, with commercial support. Chef names the Chef 360 Platform as the replacement product for several retiring components, so you can migrate onto one platform and one automation workflow rather than several.
Chef Infra Server Deprecation and the Wider Chef Product Lifecycle
InSpec is not the only Chef product on a clock. Chef Infra Server is deprecated and reaches end-of-life on November 30, 2026, with no new code or security fixes contributed to the open-source server after October 2026. Chef Automate is deprecated from November 1, 2026 and reaches EOL on November 30, 2027, while Chef Supermarket 5.x and Chef Infra Client 18.x follow in 2027. Chef Habitat, Chef Workstation 26.x and Chef Infra Client 19.x remain GA.
Chef says InSpec stays actively maintained with the open source community, so your configuration management and automation estate can keep its compliance checks while the server layer changes. Fold both timelines into one DevSecOps plan, and weigh the Chef 360 Platform for the server layer, since it is the platform Chef points Infra Server and Supermarket users toward.