pop-cms-schema/comments

This is a healthy, actively maintained release with a substantial release history, 33 releases in the last 12 months, a stable non-prerelease version, a recent repository push, and 15 commits in the last 3 months. The package is licensed, includes tests and a substantial source tree, has no install-time lifecycle scripts, is not deprecated or archived, and its repository matches and documents the package. The main concerns are that all recent repository commits came from one contributor, the repository has no security scanning or security policy, and its very low popularity provides little independent adoption evidence; these reduce resilience and transparency but do not outweigh the strong maintenance and release signals.

Latest 19.2.4

Packagist

80%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

One contributor made all 15 commits in the last 3 months, creating a concentrated bus factor. Organization ownership provides some potential handoff capacity, but no second active contributor is shown by this signal.

Repo commit activity

The repository recorded 15 commits in the last 3 months, demonstrating recent activity, but only one maintainer contributed those commits, limiting evidence of distributed maintenance capacity.

Repo issue activity

There were no new issues or pull requests in the last month and no merged pull requests; this provides little evidence of community interaction, although it does not show unresolved activity because the open issue count is unknown.

Repo popularity

The repository has only 1 star, 0 forks, and 1 watcher, so adoption evidence is weak. This is a supporting concern rather than a major health problem because the package shows strong release and commit activity.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. This is a transparency and preventive-hygiene gap, not evidence that the release is unsafe by itself.