Dependency health Workspace Solo coming soon

bml_connectRubyGems · Ruby

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 5 years without a release, bml_connect published 0.3.0 on 2026-10-26.

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.

State history 2
WhenChange
2026-11-19 active → abandoned
2026-09-16 first verdict: active

Badge

maintenance: abandoned

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

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

Watch it

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