jsonwebtoken 7+Node.js 22

Why?

Why is jsonwebtoken 7 compatible with Node.js 22?

Requirement

Node.js >=0.12

Selected version

Node.js 22

Evaluation

22.23.2 satisfies >=0.12

Conclusion

COMPATIBLE

Evidence

CompatHub reports compatibility from upstream sources rather than making unsupported claims of its own.

• npm Registry

  Confidence: HIGH

  https://registry.npmjs.org/jsonwebtoken/7.4.3

  Retrieved 30 August 2026

  Requirement: >=0.12

Node.js versions

Compatibility is derived from the project's declared Node.js requirement (>=0.12); it does not mean every version combination has been independently tested.

• 4✓
• 5✓
• 6✓
• 7✓
• 8✓
• 9✓
• 10✓
• 11✓
• 12✓
• 13✓
• 14✓
• 15✓
• 16✓
• 17✓
• 18✓
• 19✓
• 20✓
• 21✓
• 22✓
• 23✓
• 24✓
• 25✓
• 26✓
• 27—

Other Node.js versions satisfying this requirement

jsonwebtoken 7 — compatible Node.js lines tracked in CompatHub

• ✓Node.js 4version lineEOL
• ✓Node.js 5version lineEOL
• ✓Node.js 6version lineEOL
• ✓Node.js 7version lineEOL
• ✓Node.js 8version lineEOL
• ✓Node.js 9version lineEOL
• ✓Node.js 10version lineEOL
• ✓Node.js 11version lineEOL
• ✓Node.js 12version lineEOL
• ✓Node.js 13version lineEOL
• ✓Node.js 14version lineEOL
• ✓Node.js 15version lineEOL
• ✓Node.js 16version lineEOL
• ✓Node.js 17version lineEOL
• ✓Node.js 18version lineEOL
• ✓Node.js 19version lineEOL
• ✓Node.js 20version lineEOL
• ✓Node.js 21version lineEOL
• ✓Node.js 22version linesupported
• ✓Node.js 23version lineEOL
• ✓Node.js 24version linesupported
• ✓Node.js 25version lineEOL
• ✓Node.js 26version linesupported

Other jsonwebtoken versions

Only lines with relevant compatibility evidence are listed.

• jsonwebtoken 9
• jsonwebtoken 8.4
• jsonwebtoken 8.0
• jsonwebtoken 7
• jsonwebtoken 6

Lifecycle context

Lifecycle status is separate from compatibility. An EOL component can still satisfy a documented version requirement.

Supported alternatives

Node.js lines that satisfy this requirement and are still supported.

• Node.js 22supported
• Node.js 24supported
• Node.js 26supported