chef-metal-fogRubyGems · Ruby

Verdict

Looks abandoned

chef-metal-fog appears abandoned — its repository has been archived, no commits for over 8 years. There are no open issues. Plan a migration rather than waiting for a fix.

health 10/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.

repository archived

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

latest 0.9
last known licence Apache-2.0
stars 53
assessment attempted 17 days ago
GitHub evidence observed 17 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 — 1.0 24/24 done; Later 12/12 done; 0.14.0 8/8 done; Accepted Minor; Accepted Major. Source: the repository's milestones.

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

State history 1

When	Change
2026-10-26	first verdict: abandoned

Badge

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

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

Watch it

Get told when chef-metal-fog 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.