cnam/jwt-api-extension

Release historydanger

This is the package's only release, published over 11 years ago, with no releases in the last 12 months. That strongly indicates abandonment risk despite the repository still being available.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the repository's last push being over 10 years ago. This is strong evidence that maintenance has stopped.

Dependency profilecaution

Five runtime dependencies, including Behat, Guzzle, and PHPUnit, create a meaningful maintenance surface for a small, old extension. The count is not extreme, but it adds compatibility burden.

Maintainerscaution

Only one registry account has publishing access. For a user-owned repository this provides little redundancy if that maintainer is unavailable.

Project backingcaution

The registry namespace and repository owner match, and the repository is owned by a user rather than an organization. The matching ownership supports attribution but offers no organizational maintenance backing.