babicaja/jwt-4laravel

Release historydanger

The package has made no releases in nearly seven years, with zero releases in the last 12 months. This is strong evidence of stalled maintenance, although the stable major version and existing tests provide some continuity.

Repo commit activitydanger

The repository had zero commits and zero active maintainers in the last three months. Combined with the old release history, this indicates that fixes and compatibility updates may not arrive.

Project backingcaution

The package and repository are owned by the same individual account, so there is no organizational backing signal to compensate for the thin maintenance base.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest repository-hygiene gap rather than evidence that the package is unsafe to depend on.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This reduces transparency for a package implementing authentication tokens.