baltixRubyGems · Ruby
- latest 0.2
- last known licence MIT
- assessment attempted today
- registry checked 3 days ago
- registry ↗
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 →Came back
After 3 years without a release, baltix published 0.2 on 2026-11-19.
Usually this is a maintainer returning. It is also what a hijacked package looks like, so it is worth a glance at what changed before you upgrade.
Maintenance trends
Loading historical repository activity…
Signals · last 3 checks
State history 2
| When | Change |
|---|---|
| 2026-11-22 | unknown → active |
| 2026-10-23 | first verdict: unknown |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/rubygems/baltix)
Watch it
Get told when baltix 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.