Package Health/pop-cms-schema/page-mutations

pop-cms-schema/page-mutations

This release appears healthy and suitable to depend on: it has a long release history with 145 releases, 33 releases in the last 12 months, a stable non-prerelease version, and a release published very recently. The repository is active, unarchived, correctly associated with the package, and backed by an organization, while the artifact includes a license, README, tests, and a substantial source tree. The main risks are concentrated maintenance, since one contributor made all 16 commits in the last three months, plus the absence of repository security scanning and a security policy; low popularity is only weak supporting evidence and not itself a material dependency concern.

Latest 19.2.4

Packagist

86%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

One contributor made all 16 commits in the last three months, creating a meaningful continuity and bus-factor concern. Organization ownership partially compensates because maintenance can potentially be handed off within the project.

Repo issue activity

There are no open issues or pull requests, and no issue or pull-request activity in the last month. This does not indicate a problem by itself, but it provides little evidence about community support or responsiveness.

Repo popularity

The repository has only 1 star and no forks, so external adoption evidence is limited. This is weak supporting evidence rather than a health verdict, especially given the package's demonstrated release activity.

Repo tooling

Composer build tooling is present, but no security-scanning tools are configured. The missing scanning is a transparency and defense-in-depth gap, though it is not evidence that the package is unsafe.

Security policy

The repository has no security policy, leaving vulnerability-reporting and security-response procedures undocumented.