aemoRubyGems · Ruby

Verdict

Looks abandoned

aemo is abandoned by its maintainers' own account — the README says it is no longer maintained, no commits for 4 months. Plan a migration rather than waiting for a fix.

health 63/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 9 days ago from signal heuristics. How each verdict is decided

latest 0.9.1
last known licence MIT
stars 24
assessment attempted 9 days ago
GitHub evidence observed 9 days ago
registry checked 20 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 — 0.1.37 1/1 done; v0.3 1/1 done; v0.3.1 1/1 done; v0.2 (due 2016-06-29). Source: the repository's milestones.

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

State history 2

When	Change
2026-10-29	active → abandoned
2026-09-15	first verdict: active

Badge

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

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

Watch it

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