pop-schema/users

This is a healthy, mature release with more than five years of history, 162 releases, 33 releases in the last 12 months, a stable non-prerelease version, and a very recent repository push. The package is licensed, has a README and tests in both the artifact and repository, uses Composer tooling, has no install-time lifecycle scripts, is not deprecated or archived, and its repository clearly matches the package. The main risks are concentrated maintenance: one registry maintainer and one contributor responsible for all 15 commits in the last three months, plus no repository security policy or security-scanning tooling. Those concerns warrant monitoring but are partly offset by organization ownership and strong ongoing release activity.

Latest 19.2.4

Packagist

84%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one account has registry publish access, which is a concentration risk, but this is partly compensated by the repository being owned by an organization and by the package's active release history.

Repo bus factor

One contributor made all 15 recent commits, creating a genuine single-contributor continuity risk; organization ownership provides some capacity for handoff but does not eliminate the observed concentration.

Repo popularity

The repository has only 1 star and no forks, so external adoption evidence is limited; popularity is supporting evidence rather than a decisive health criterion, and active releases compensate for this weakness.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. The missing scanning coverage is a hygiene concern rather than evidence of unsafe code by itself.

Security policy

The repository has no SECURITY.md or other detected security policy, reducing vulnerability-reporting transparency for dependents.