Dependency health Workspace Solo coming soon

github.com/rasky/go-lzoGo

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 6 years without a release, github.com/rasky/go-lzo published v0.0.0-20261012164727-ad21c35a1111 on 2026-10-12.

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.

What the project says about itself
  • OpenSSF Scorecard — 2 / 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 yesterday; registry facts on every crawl.

State history 2
WhenChange
2026-11-17 finished → abandoned
2026-09-20 first verdict: finished

Badge

maintenance: abandoned

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

[![maintenance](https://isitdeadyet.dev/badge/go/github.com/rasky/go-lzo.svg)](https://isitdeadyet.dev/go/github.com/rasky/go-lzo)

Watch it

Get told when github.com/rasky/go-lzo 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.