cryptorecordRubyGems · Ruby

Verdict

Looks abandoned

cryptorecord appears abandoned — its repository has been archived, no commits for 9 months. There are no open issues. Plan a migration rather than waiting for a fix.

health 10/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.

repository archived

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

latest 1.0.0
last known licence GPL
stars 2
assessment attempted 24 days ago
GitHub evidence observed 24 days ago
registry checked 21 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

State history 1

When	Change
2026-10-20	first verdict: abandoned

Badge

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

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

Watch it

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