pop-cms-schema/posts-wp

This is a mature, actively released package with 162 releases over roughly 5.6 years, 33 releases in the last 12 months, a stable current version, no registry deprecation, a non-archived repository, licensing, tests, and no install-time lifecycle scripts. The package is transparently linked to a matching organization-owned repository and has recent commit activity, but maintenance is concentrated entirely in one contributor, repository popularity is minimal, issue and pull-request activity is absent, and no security policy or security-scanning tooling was detected. These are meaningful resilience and security-hygiene limitations, but the strong release cadence and active backing make the package generally reasonable to depend on with normal dependency monitoring.

Latest 19.2.4

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

One contributor made all 14 commits in the last 3 months, creating a concentrated maintenance risk. The organization-owned repository provides some handoff potential, but no second active contributor is shown.

Repo issue activity

There were no new or merged pull requests and no issue activity in the last month. This does not outweigh the active release and commit history, but it limits evidence of community maintenance and review.

Repo popularity

The repository has only 1 star, 0 forks, and 1 watcher. Popularity is supporting evidence rather than a verdict, but these very low counters provide little external validation.

Repo tooling

Composer is used as a build tool, but no security-scanning tools were detected. The build tooling is appropriate, while the missing scanning capability is a security-hygiene gap.

Security policy

The linked repository has no security policy. This weakens vulnerability-reporting transparency, although the package otherwise provides a security contact in its README and has active release maintenance.