chef-stoveRubyGems · Ruby

Verdict

Looks abandoned

chef-stove is abandoned by its maintainers' own account — the README says it is no longer maintained, no commits for over 6 years. Plan a migration rather than waiting for a fix.

health 39/100

Why this verdict?

abandoned — No commits for over 365 days with unanswered issues piling up — or the registry marks it deprecated, or the repository is archived.

README says the project is no longer maintained

Judged 16 days ago from signal heuristics. How each verdict is decided

latest 7.1.6
last known licence Apache-2.0
stars 167
assessment attempted 16 days ago
GitHub evidence observed 16 days ago
registry checked 21 days ago
registry ↗
repository ↗

Vulnerabilities, end of life and next steps

Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.

Review remediation options →

Maintenance trends

Loading historical repository activity…

Signals · last 2 checks

Commits 90d

Open issues

Unanswered

Contributors

What the project says about itself

Open milestones — August 17 - August 28 (due 2020-08-28); August 31 - September 11 (due 2020-09-11). Source: the repository's milestones.

Third-party facts checked 16 days ago; registry facts on every crawl.

State history 1

When	Change
2026-10-27	first verdict: abandoned

Badge

Drop this in your README. It re-renders itself as the verdict changes.

[![maintenance](https://isitdeadyet.dev/badge/rubygems/chef-stove.svg)](https://isitdeadyet.dev/rubygems/chef-stove)

Watch it

Get told when chef-stove changes state, changes licence, or is deprecated — instead of finding out during an incident.

Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.