get_process_memRubyGems · Ruby

Verdict

Finished, not abandoned

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

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

Judged today from signal heuristics. How each verdict is decided

latest 1.0.0
licence MIT
stars 497
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 →

Maintenance trends

Loading historical repository activity…

Signals · last 5 checks

Commits 90d

Open issues

Unanswered

Contributors

What the project says about itself

OpenSSF Scorecard — 3 / 10 on 2026-08-24. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.

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/get_process_mem.svg)](https://isitdeadyet.dev/rubygems/get_process_mem)

Watch it

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