batenburg/jwt-guard

Release historydanger

Only two releases exist, with none in the last 12 months; the latest release was about five years and nine months ago. This is strong evidence of abandonment risk.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the long release gap and indicating no current maintenance capacity.

Project backingcaution

The repository is owned by the matching individual account rather than an organization, so the single registry maintainer reflects a genuinely narrow backing structure.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but this small footprint provides little evidence of community support.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a hygiene gap that matters modestly for a package handling authentication.