Package Health/sakanjo/filament-auth-preferences

sakanjo/filament-auth-preferences

This is a usable and reasonably transparent package with a stable major release, 850 days of history, five releases in the last 12 months, an MIT license, tests, a matching source repository, and no deprecation or risky workflow findings. The main concerns are that recent repository activity is very light and entirely concentrated in one contributor, while the repository lacks a security policy and its workflows do not declare top-level token permissions. Low popularity is only supporting context rather than a decisive problem, but the thin maintenance base means dependents should monitor the project and be prepared for limited maintainer capacity.

Latest v3.0.2

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. This is a genuine continuity concern for a user-owned project, although repository activity shows the same owner is currently maintaining it.

Project backing

The repository is owned by an individual user rather than an organization, so the one-person maintenance and bus-factor concerns are not compensated by visible organizational backing.

Repo bus factor

All recent commits come from one contributor with a 100% share, leaving the project exposed to a single-maintainer interruption.

Repo commit activity

Only one commit was recorded in the last 3 months, by one active maintainer. The recent activity has not stopped, but its low volume suggests limited maintenance capacity.

Repo popularity

The repository has only 2 stars, 1 fork, and 1 watcher. This indicates limited adoption evidence, but popularity is supporting context and does not by itself make a small, maintained package unsafe to depend on.