Dependency health Workspace Solo coming soon

jwt-simplenpm

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, jwt-simple published 0.6.1 on 2026-10-30.

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
  • Build provenance — the latest release carries no provenance attestation. Source: the registry.
  • Supported runtime — node >= 6.6.0. Source: the registry.
  • Publishers on the registry — 1. Source: the registry.
  • OpenSSF Scorecard — 2.8 / 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 4 days ago; registry facts on every crawl.

State history 2
WhenChange
2026-11-17 finished → abandoned
2026-10-16 first verdict: finished
Where to go instead 1
  1. jose

    Named by the maintainers in the deprecation notice

    jwt-simple is no longer maintained. Please migrate to jose or jsonwebtoken.

    From the maintainers’ own deprecation notice.

Badge

maintenance: abandoned

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

[![maintenance](https://isitdeadyet.dev/badge/npm/jwt-simple.svg)](https://isitdeadyet.dev/npm/jwt-simple)

Watch it

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