aasm_historyRubyGems · Ruby

Verdict

Finished, not abandoned

aasm_history looks complete rather than neglected — no commits for over 8 years. 4 of 6 open issues have had no reply. A library that has stopped changing is not the same as one that has been dropped.

health 24/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 2937 days ago
almost no new issues — nobody is waiting on a fix

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

latest 0.1.3
licence MIT
stars 14
checked 4 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 1 check

The first observation is recorded. Trend lines appear once at least two checks have data for the same signal.

Commits 90d

Open issues

Unanswered

Contributors

What the project says about itself

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

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

State history 1

When	Change
2026-09-12	first verdict: finished

Badge

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

[![maintenance](https://isitdeadyet.dev/badge/rubygems/aasm_history.svg)](https://isitdeadyet.dev/rubygems/aasm_history)

Watch it

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