pop-schema/categories-wp

This is a healthy, actively maintained package with a substantial release history, frequent recent releases, a stable current version, clear licensing, source-backed tests, and a repository that was updated at the assessment time. The main adoption risks are concentrated maintenance by one contributor, low repository popularity, no security policy or security-scanning tooling, and the absence of a changelog; these are meaningful transparency and continuity concerns but do not outweigh the package's strong release and activity evidence. The organization-owned repository provides some backing for the concentrated maintainer base.

Latest 19.2.4

Packagist

82%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access, which is a modest continuity concern. The repository is organization-owned and shows active recent commits, partly compensating for the thin registry maintainer list.

Repo bus factor

One contributor made all 15 commits in the last 3 months, creating a real continuity risk. The organization ownership provides some capacity to hand off maintenance, so this is caution rather than a severe abandonment signal.

Repo popularity

The repository has 1 star, 0 forks, and 1 watcher. This low adoption footprint is a supporting caution, but popularity alone does not outweigh the strong release and commit activity.

Repo tooling

Composer build tooling is present, but no security-scanning tools are reported. This is a hygiene gap that lowers confidence in ongoing security oversight without indicating abandonment by itself.

Security policy

The repository has no security policy, leaving reporting and response expectations undocumented. The README does provide a security contact, which partly compensates for the missing repository policy.