legacy-rails-CVE-2020-5267-patchRubyGems · Ruby

Verdict

Finished, not abandoned

legacy-rails-CVE-2020-5267-patch looks complete rather than neglected — no commits for over 6 years. there are no open issues. A library that has stopped changing is not the same as one that has been dropped.

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

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

latest 1.0.0
last known licence MIT
stars 1
assessment attempted 24 days ago
registry checked 6 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

State history 1

When	Change
2026-10-12	first verdict: finished

Badge

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

[![maintenance](https://isitdeadyet.dev/badge/rubygems/legacy-rails-CVE-2020-5267-patch.svg)](https://isitdeadyet.dev/rubygems/legacy-rails-CVE-2020-5267-patch)

Watch it

Get told when legacy-rails-CVE-2020-5267-patch 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.