Dependency health Workspace Solo coming soon

github.com/nccurry/go-kongGo

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 7 years without a release, github.com/nccurry/go-kong published v0.0.0-20261022213644-a9705e2b0005 on 2026-10-22.

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 finished → active
2026-10-26 first verdict: finished

Badge

maintenance: active

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

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

Watch it

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