Package Health/pop-schema/schema-commons-wp

pop-schema/schema-commons-wp

This is a healthy, actively maintained release with a strong release cadence, stable versioning, explicit GPL licensing, a matching and documented source repository, tests, and no deprecation or 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 low public popularity, no security policy or security-scanning tooling was detected, and no changelog was present in the package or repository. These are meaningful transparency and resilience gaps, but the organization-owned repository, recent activity, mature release history, and otherwise coherent package structure substantially reduce abandonment risk.

Latest 19.2.4

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact and repository include a substantial README and tests, although neither contains a changelog; the README points consumers to a CHANGELOG, but its presence was not observed, leaving a modest release-transparency gap.

Repo bus factor

One contributor made all 14 commits in the last 3 months, creating a genuine continuity risk; the organization-owned repository provides some compensating capacity but does not remove the concentration concern.

Repo popularity

The repository has only 2 stars, 0 forks, and 1 watcher, indicating limited adoption evidence. Popularity is supporting evidence rather than a verdict, so this is a minor caution for resilience and external review.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a security-hygiene gap, while the available build tooling supports basic project maintenance.

Security policy

The linked repository has no security policy, reducing transparency about vulnerability reporting and coordinated disclosure.