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

pop-wp-schema/schema-commons

This is a generally healthy and actively maintained release: it has a stable version, 146 releases since 2021, 33 releases in the last 12 months, recent repository activity, an unarchived source repository, clear licensing, and package/repository alignment. The main concerns are a single active contributor accounting for all 15 recent commits, no repository security policy or security-scanning tooling, and very limited repository adoption signals; these increase continuity and transparency risk but do not outweigh the strong release cadence and current maintenance evidence.

Latest 19.2.4

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access, which is a continuity concern, although the source repository is backed by an organization and recent releases demonstrate active publishing.

Repo bus factor

One contributor made all 15 commits in the last 3 months, creating a meaningful continuity risk. Organization ownership provides some handoff capacity, but no second active contributor is shown.

Repo popularity

The repository has only 1 star, 0 forks, and 1 watcher. Popularity is supporting evidence rather than a verdict, but these low figures provide little external adoption or review evidence.

Repo tooling

Composer is used as a build tool, but no security-scanning tools are configured; the missing scanning coverage is a modest supply-chain hygiene gap.

Security policy

The linked repository has no SECURITY.md or other detected security policy, leaving vulnerability-reporting and response practices undocumented.