Dependency health Workspace Solo coming soon

github.com/subuk/vmangoGo

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/subuk/vmango published v0.19.0 on 2026-11-08.

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
  • Open milestones — v0.14.0 1/3 done; 0.13.0 1/6 done. Source: the repository's milestones.

Third-party facts checked 25 days ago; registry facts on every crawl.

State history 1
WhenChange
2026-11-21 first verdict: active

Badge

maintenance: active

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

[![maintenance](https://isitdeadyet.dev/badge/go/github.com/subuk/vmango.svg)](https://isitdeadyet.dev/go/github.com/subuk/vmango)

Watch it

Get told when github.com/subuk/vmango 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.