Package Health/ezitisitis/jetstream-no-personal-team

ezitisitis/jetstream-no-personal-team

Its focused eight-file implementation is easy to inspect, and the latest release includes Laravel 12 support. The MIT declaration and package/repository name match improve transparency. There are no tests, security policy, or recent issue or commit activity, so future compatibility work is uncertain.

Latest 1.5.0

Packagist

64%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry publishing account is listed. That is a limited publishing base for a user-owned project and increases continuity risk when combined with the absence of recent activity.

Project backing

The package and repository are owned by the same individual account rather than an organization. That is consistent with a small personal project but provides limited visible backing for sustained maintenance.

Release history

The package has six releases over about three years, but none in the last 12 months; the latest release was in May 2025. This indicates a meaningful maintenance slowdown for a framework integration.

Repo commit activity

The repository had zero commits and zero active maintainers in the last three months. Combined with no releases in the last year, this raises the risk that compatibility issues will remain unattended.

Security policy

The repository has no security policy. This is a transparency and response-process gap, though it is not by itself evidence that the package is unsafe.