pop-wp-schema/pages

This is a healthy, actively maintained release with a strong release history: it has existed for about 5 years, has 150 releases, and received 32 releases in the last 12 months, with a stable non-prerelease version. The repository is active, unarchived, matches the package, and is backed by an organization, while the package includes a license, README, tests, and no install-time lifecycle scripts. The main concerns are that all 14 commits in the last 3 months came from one contributor, the repository has very limited popularity, lacks a security policy and security scanning, and has no changelog; these reduce transparency and resilience but do not outweigh the clear ongoing maintenance and organizational backing.

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 14 recent commits, creating a low bus factor; organization ownership partly compensates because maintenance can potentially be handed off internally.

Repo issue activity

There were no new or closed issues or pull requests in the last month and no open pull requests; this is a limited collaboration signal, but it does not show unresolved maintenance failure.

Repo popularity

The repository has only 2 stars, 0 forks, and 1 watcher, indicating limited community adoption and review; popularity is supporting evidence rather than a decisive health verdict.

Repo tooling

Composer is used as a build tool, but no security scanning tools are configured; the missing scanning reduces defensive supply-chain hygiene without indicating abandonment.

Security policy

The repository has no SECURITY.md or other detected security policy, leaving vulnerability-reporting guidance less transparent despite the README providing an email contact.