http-acceptRubyGems · Ruby

Verdict

Finished, not abandoned

http-accept looks complete rather than neglected — last commit this week. 1 of 4 open issues have had no reply. A library that has stopped changing is not the same as one that has been dropped.

health 85/100

Why this verdict?

finished — No commits for over 365 days, and almost nobody filing new issues — or the README says the project is done.

last commit 545 days ago
almost no new issues — nobody is waiting on a fix

Judged today from signal heuristics. How each verdict is decided

latest 2.2.2
licence MIT
stars 87
checked today
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 →

Came back

After 2 years without a release, http-accept published 2.2.2 on 2026-09-06.

Usually this is a maintainer returning. It is also what a hijacked package looks like, so it is worth a glance at what changed before you upgrade.

Maintenance trends

Loading historical repository activity…

Signals · last 2 checks

Commits 90d

Open issues

Unanswered

Contributors

What the project says about itself

Open milestones — 2.0 0/2 done; v2.2.0 1/1 done. Source: the repository's milestones.

Third-party facts checked yesterday; registry facts on every crawl.

State history 1

When	Change
2026-09-06	first verdict: finished

Badge

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

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

Watch it

Get told when http-accept 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.