gabmaxs/jwt-auth

Release historydanger

Only one release exists, published about five years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a library dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long inactivity period. This materially increases abandonment risk.

Dependency profilecaution

The package declares eight runtime dependencies, including two JWT libraries and several Laravel components. This is a meaningful dependency surface, though not by itself evidence of poor maintenance.

Maintainerscaution

A single registry publishing account is listed, but this is administrative metadata and does not establish project activity or capacity. The repository is user-owned, so no organization backing compensates for the thin registry base.

Project backingcaution

The registry namespace and repository owner are the same individual account, with no organization backing shown. This is consistent ownership but provides limited evidence of sustained project capacity.