pop-schema/pages

This release appears suitable for dependency use: it has a long release history, frequent recent releases, a stable non-prerelease version, an active and non-archived source repository, clear licensing, tests, and no install-time lifecycle scripts. The main concerns are that all recent repository commits come from one contributor, the project has very low popularity, and no repository security policy or automated security scanning was detected; however, organization ownership and strong ongoing release activity partly mitigate the maintainer-concentration concern. The missing changelog is a minor transparency gap because the package README directs users to a changelog that was not found.

Latest 19.2.4

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

One contributor made 100% of the 16 commits in the last 3 months, creating a meaningful continuity risk. Organization ownership provides some ability to hand off maintenance, but no second active contributor is shown.

Repo popularity

The repository has only 1 star, 0 forks, and 1 watcher. This limits external validation and community support, although popularity is supporting evidence rather than a verdict.

Repo tooling

Composer is used as a build tool, but no security-scanning tools were detected. The missing scanning is a security-hygiene gap, though it does not establish maliciousness or make the package unfit on its own.

Security policy

The repository has no SECURITY.md or equivalent security policy, reducing transparency for vulnerability reporting and response.