geminaboxRubyGems · Ruby
- latest 4.0.0
- licence MIT
- stars 1,546
- 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 1 check
The first observation is recorded. Trend lines appear once at least two checks have data for the same signal.
Commits 90d
34
Open issues
0
Unanswered
0
Contributors
4
What the project says about itself
- Open milestones — v1.4.4 (unreleased) (due 2022-08-31) 2/2 done; v3.0.0 (due 2022-10-31); v2.2.0 (due 2023-05-31) 48/48 done; Backlog (due 2023-06-30) 1/1 done; v2.3.0 (due 2023-06-30) 1/1 done. Source: the repository's milestones.
- OpenSSF Scorecard — 5.5 / 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 today; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-09-27 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/rubygems/geminabox)Watch it
Get told when geminabox 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.