kampfcaspar/jwt

Release historydanger

The package has had no release in more than two years: its latest release was December 9, 2023, despite being over two years old. 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 release history's prolonged inactivity. No provided signal shows recent maintenance capacity.

Repo popularitycaution

The repository has zero stars and forks and only one watcher, indicating little visible adoption or community support. Popularity is supporting evidence rather than a verdict, but it reinforces the thin project backing.

Repo toolingcaution

The repository uses Composer build tooling, but it has no reported security scanning tools. The missing scanning is a hygiene concern, especially for a JWT-related library, though it is not severe on its own.

Security policycaution

The repository has no security policy. For a JWT abstraction library, the absence of a documented process for reporting and handling security issues reduces transparency.