Package Health/pop-schema/user-state-mutations-wp

pop-schema/user-state-mutations-wp

This is a healthy, actively maintained Composer package with a five-year history, 162 releases, 33 releases in the last 12 months, a stable non-prerelease version, recent repository activity, matching source-repository identity, and clear licensing. The main risks are maintenance concentration in one contributor, no repository security scanning or security policy, no changelog, and limited repository popularity; these are meaningful transparency and continuity concerns but do not outweigh the strong release and activity history. It appears reasonable to depend on, with ordinary caution about single-maintainer continuity.

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. This is a continuity concern, although the organization-owned repository and strong recent activity provide some compensating project backing.

Repo bus factor

One contributor made all 15 commits in the last three months, creating a high bus-factor risk. Organization ownership partly mitigates handoff risk, but no second active contributor is evidenced.

Repo issue activity

There were no new or closed issues and no pull requests in the last month. This does not show abandonment because release and commit activity are strong, but it provides little evidence of broader maintenance participation.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide little external validation.

Repo tooling

Composer is used as a build tool, but no security-scanning tools are detected. The missing scanning capability is a security-hygiene gap, though it is not evidence that the package is malicious.