pop-schema/users-wp

This release appears healthy and suitable to depend on: it has a long release history with 162 releases, 33 releases in the last 12 months, a stable non-prerelease version, no registry deprecation, an active non-archived repository, clear licensing, tests, and a matching repository with recent activity. The main concerns are that all 14 commits in the last three months came from one contributor, the repository has no security policy or security-scanning tooling, and no changelog was detected; these are meaningful transparency and resilience gaps, but the organization-backed repository, sustained release cadence, and current activity substantially mitigate abandonment risk.

Latest 19.2.4

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact and repository include a README and tests, and the README documents installation, development, testing, and security reporting. A changelog was not detected, which is a modest release-transparency gap despite the README referring to one.

Repo bus factor

One contributor made all 14 commits in the last three months, creating a significant continuity risk. The organization-owned repository provides some mitigation because maintenance can potentially be handed off, but no second active contributor is evidenced.

Repo popularity

The repository has only 1 star and 0 forks, so external adoption evidence is limited; however, low popularity is supporting evidence rather than a health verdict and does not outweigh the package's release and maintenance activity.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. The build setup supports reproducibility and maintenance, while the missing security tooling is a modest supply-chain hygiene gap.

Security policy

The repository has no SECURITY.md or other detected security policy, leaving vulnerability-reporting and response expectations less explicit than preferred.