pop-cms-schema/users

This is a healthy, actively maintained Composer package with a substantial release history, a stable current version, a non-deprecated registry status, recent repository activity, clear licensing, tests, and a source repository that matches and documents the package. The main risks are that all recent commits come from one contributor, repository popularity is very low, and no repository security policy or security-scanning tooling was observed; the organization-owned repository provides some maintenance backing but does not eliminate single-contributor concentration. Overall, it appears reasonable to depend on, with normal continuity and security-process caveats.

Latest 19.2.4

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access, which is a continuity concern; however, this administrative list does not determine actual maintenance capacity, and the linked repository is owned by an organization with recent activity.

Repo bus factor

One contributor made all 15 commits in the last 3 months, creating a real continuity risk. Organization ownership offers some potential handoff capacity, but no second active contributor is shown to compensate for the concentration.

Repo popularity

The repository has only 1 star, 0 forks, and 1 watcher, indicating limited external adoption or visibility; popularity is supporting evidence rather than a health verdict, so this is a modest concern.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected; the build setup is appropriate while the security-process coverage is limited.

Security policy

The repository has no SECURITY.md or equivalent security policy, leaving vulnerability reporting and response expectations less explicit despite the README providing an email-based security contact.