bonza/jwt

Release historydanger

The latest release was over six years ago, and there have been no releases in the last 12 months. This strongly increases abandonment risk for a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no current maintenance activity.

Maintainerscaution

Only one registry maintainer is recorded, leaving little visible publishing redundancy. This is a supporting concern rather than proof of abandonment because registry access does not measure actual development activity.

Repo popularitycaution

The repository has zero stars, forks, and watchers, providing no community adoption or review signal to offset the stale maintenance record.

Repo toolingcaution

Composer is used for builds, which is appropriate, but no security-scanning tools are configured. This leaves a meaningful transparency and maintenance gap for a JWT library.