pop-wp-schema/posts

This is a healthy, mature release with a strong maintenance record: it has existed for about 5 years, has 151 releases including 33 in the last 12 months, releases roughly every 4 days, and is currently stable and not deprecated. The source repository is active, unarchived, organization-backed, clearly associated with the package, and includes tests, a license, and Composer build tooling. The main concerns are that all 15 commits in the last 3 months came from one contributor, the repository has no security scanning or security policy, and repository popularity is very low; these increase maintainer and transparency risk but do not outweigh the sustained release activity and current repository activity.

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, which is a concentration risk, but the organization-backed repository and strong release activity provide compensating project context.

Repo bus factor

One contributor made all 15 commits in the last 3 months, creating a genuine continuity risk; organization backing partly mitigates the concern because maintenance can potentially be handed off.

Repo popularity

The repository has only 2 stars, 0 forks, and 1 watcher, indicating limited external adoption; popularity is supporting evidence only and is outweighed here by active releases and recent commits.

Repo tooling

Composer is used as a build tool, but no security scanning tools are configured; the missing scanning lowers supply-chain transparency without indicating an immediate health failure.

Security policy

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