Package Health/pop-cms-schema/categories-wp

pop-cms-schema/categories-wp

This is a healthy, actively maintained release with a strong five-year history, 162 releases, 33 releases in the last 12 months, stable versioning, a current unarchived repository, tests, clear licensing, and no install-time lifecycle scripts. The main concerns are that all 15 recent commits came from one contributor, the repository has very little visible popularity, no security scanning or repository security policy was found, and no changelog is present; however, the organization-owned repository, active release cadence, package-specific source linkage, and test coverage materially reduce abandonment and transparency risk. It appears reasonable to depend on, with normal caution around maintainer concentration and security-process maturity.

Latest 19.2.4

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

One contributor made all 15 commits in the last 3 months, creating a genuine continuity and bus-factor concern. Organization ownership provides some handoff potential but does not eliminate concentration risk.

Repo issue activity

There were no new or closed issues or pull requests in the last month and no open pull requests; open issue count is unknown. This provides little evidence of community activity, but does not outweigh the strong release and commit cadence.

Repo popularity

The repository has only 1 star, 0 forks, and 1 watcher, indicating limited public adoption or visibility. Popularity is supporting evidence rather than a decisive health criterion, so this warrants only caution.

Repo tooling

Composer build tooling is present, but no security scanning tools are detected. The missing scanning is a process gap, though it is not evidence of abandonment by itself.

Security policy

The repository has no SECURITY.md or other detected security policy, reducing transparency for vulnerability reporting and coordinated response.