getpop/access-control

This is a healthy, actively maintained release with a strong release history: the package is over five years old, has 162 releases, and had 33 releases in the last 12 months, with a stable non-prerelease version. It is not deprecated or archived, has a clear license, tests, a substantial README, a coherent 47-file implementation tree, and no install-time lifecycle scripts. The main concern is maintenance concentration: all 14 commits in the last three months came from one contributor, and the repository has no security scanning or security policy. Organization backing and the package's ongoing release cadence reduce—but do not eliminate—the single-maintainer risk. Overall, it appears suitable to depend on, with normal supply-chain and continuity precautions.

Latest 19.2.4

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

The registry lists one publishing maintainer, which is a limited publishing base; this is partly mitigated by the linked repository being owned by an organization and by observed release activity.

Repo bus factor

One contributor made all 14 commits in the last three months, creating a real continuity risk; organization ownership provides some handoff capacity, but no second active contributor is shown.

Repo popularity

The repository has only 2 stars, 0 forks, and 1 watcher, so external adoption evidence is weak; popularity is supporting evidence rather than a decisive health requirement for a small component.

Repo tooling

Composer build tooling is present, but no security scanning tools are detected, leaving a security-hygiene gap despite otherwise adequate build support.

Security policy

The repository has no security policy, reducing transparency about vulnerability reporting and response expectations.