NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist
Packagist, #703 most downloaded on Packagist
JSON Web Token Authentication for Laravel and Lumen
Latest stable
2.3.1
Last release 29 days ago
24 Oct 2026
Release timing varies
gaps range from 2 weeks to 2.2 years
Most releases are documented
notes for 37 of 42 stable releases
Nothing withdrawn
no release was ever pulled
12 years old
55 releases · first in 2014
Drag across the ruler to compare, or tap a release to open it.
fix: Apply setAlgo, setSecret and setKeys changes in the Lcobucci provider by @tymondesigns in https://github.com/tymondesigns/jwt-auth/pull/2304
Full Changelog: https://github.com/tymondesigns/jwt-auth/compare/2.3.0...2.3.1
feat: Support Laravel 13 by @tymondesigns in https://github.com/tymondesigns/jwt-auth/pull/2299
Full Changelog: https://github.com/tymondesigns/jwt-auth/compare/2.2.1...2.3.0
Your coding agent can read these notes before it upgrades. Set up the MCP server →
fix: Carbon 3 diffInMinutes by @tymondesigns and @ThinhNdv in https://github.com/tymondesigns/jwt-auth/pull/2287
Full Changelog: https://github.com/tymondesigns/jwt-auth/compare/2.2.0...2.2.1
Add support for PHP 8.4 and Carbon 3 by @vbergerondev in https://github.com/tymondesigns/jwt-auth/pull/2280
Full Changelog: https://github.com/tymondesigns/jwt-auth/compare/2.1.1...2.2.0
Add support for Carbon 3.X by @RBFraphael in https://github.com/tymondesigns/jwt-auth/pull/2247
Full Changelog: https://github.com/tymondesigns/jwt-auth/compare/2.1.0...2.1.1
feat: Add Laravel 11 compatibility by @tymondesigns in https://github.com/tymondesigns/jwt-auth/pull/2243
Full Changelog: https://github.com/tymondesigns/jwt-auth/compare/2.0.0...2.1.0
Compatibility with Laravel 9 & 10 (Laravel 9 was previously done but not tagged)
Prevent installation of lcobucci/jwt 3.4 and above due to breaking deprecation notice in laravel #2059
✨ Improvements Compatible with Laravel 8
Drop support for Cartalyst Sentinel
Fix for php 7.3 when defining persistent claims that do not exist
Added "always-no" option to secret generate command
Do not add to blacklist if it already exists
Allow nbf claim to be in the future
nbf claim to be in the future (b860a4ca219d6d76374445cffd9836b1bd1db9a6)jwt:secret command to 64 characters (f72b8eb0deff2c002d40a8b0411a546c28ebec98)Reset claims collection when creating a payload
JWTProvider (#1505)JWTGuard is now macroable (#1604)JWTAuth also respects the lock_subject config (#1545)
👍 Huge thank you to everyone who contributed to this release!
ℹ️ The next release will be 1.0.0 and I will be stepping up activity on this repo very soon. Thanks for bearing with me 🙏
Add config option for lock_subject, allowing the removal of the prv claim, if you don't have multiple guards
lock_subject, allowing the removal of the prv claim, if you don't have multiple guards (7c1d58e294b255c4afa31c121b11b947e8699cbe)leeway to help with clock skew (#1453)namshi/jose has been abandoned (#1453)jwt:secret commandauth()->getToken() now returns null instead of false if the token is not present.👍 Huge thank you to everyone who contributed to this release!
More sensible order of claim overrides
jwt:secret command not returning when it should (5b4785e45671a45fdb23d3b3df5c9c31681d547c)Full docs will be ready for the final 1.0.0 release
👍 Huge thank you to everyone who contributed to this release!
@lucasmichot @cappuc @crynobone @miscbits @MitchellMcKenna @KennedyTedesco @DanielMcAssey @hughsaffar @nachodd
includes some important fixes along with some minor tweaks and improvements
fixes issue from previous release
Nothing published for this version
Tagging an alpha version of the next release.
Tagging an alpha version of the next release.
No documentation just yet (soon) so only use if you know what you're doing :smile:
Will populate here with a quick start soon too
Nothing published for this version
Nothing published for this version
Update namshi/jose dependency to fix issues with phpseclib
namshi/jose dependency to fix issues with phpseclibjti claim is now totally random as per the develop branch
jti claim is now totally random as per the develop branchNothing published for this version
Doh!... I added the incorrect config paths
Doh!... I added the incorrect config paths
removing closures from config as this breaks laravel's config caching
Very small patch release...
Some bug fixes brought over from develop branch.
Some bug fixes brought over from develop branch.
Some people expressed the need for this patch, so just a quick release whilst 0.6 is still cooking.
Some people expressed the need for this patch, so just a quick release whilst 0.6 is still cooking.
nbf, exp & iat claims to intadding typ back into the JWT header
typ back into the JWT headerNothing major here, just ensuring branches and releases are in-sync.
Nothing major here, just ensuring branches and releases are in-sync.
fixes token refreshing where token is wrongly deemed expired - see #102
- fixing token refreshing - adding JWTFactory facade
JWTFactory facadebumping version of namshi/jose to address this issue
namshi/jose to address this issueswitching to namshi/jose as it provides gretaer control over token verification
This release targets Laravel 5
- fixing token refreshing - adding JWTFactory facade
JWTFactory facadebumping version of namshi/jose to address this issue
namshi/jose to address this issuefallback to no tags on cach provider (when using file or db drivers)
switching to namshi/jose as it provides gretaer control over token verification
This release targets Laravel 4
fixing double quotes message on exception
Nothing published for this version
Nothing published for this version
fixing issue with firebase provider throwing exception when token has expired - see #14
fixing issue where getToken() returns actual token and thus cannot be chained - resolves #10
getToken() returns actual token and thus cannot be chained - resolves #10extracting token/payload validation to separate classes
~4.0 closes #8fixes an issue where custom responses weren't being returned correctly from events - see #6
fixing issue where fromUser() method was requiring an illuminate model
fromUser() method was requiring an illuminate modelremoving Mockery as dev dependency and updating tests
fixing issue where User had to be in global namespace - resolves #5
storing token on JWTAuth object to allow for method chaining.
JWTAuth object to allow for method chaining.e.g. JWTAuth::getToken()->toUser();
JWTAuthNothing published for this version
extracting Firebase provider into separate providers structure
lots of bugfixes and improvements
Nothing published for this version
One column per quarter.