Package Health/pop-wp-schema/taxonomymeta

pop-wp-schema/taxonomymeta

This release appears healthy and suitable to depend on: it has a long release history, frequent recent releases, a stable non-prerelease version, an active non-archived repository, matching package documentation, and an organization-backed project. The main risks are concentration of recent development in one contributor, lack of repository security scanning and a formal security policy, and the absence of a changelog despite the README referring to one. These are meaningful transparency and resilience gaps, but they are outweighed by strong ongoing release and commit activity and the absence of deprecation or install-time lifecycle scripts.

Latest 19.2.4

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact includes a README and tests, and the README documents installation, development, testing, issue reporting, and security contact details. A changelog is absent both from the package and repository, which leaves a modest transparency gap.

Repo bus factor

All 14 recent commits came from one contributor, creating a low bus factor and a resilience risk. Organization ownership provides some handoff potential but does not eliminate the observed concentration.

Repo popularity

The repository has no stars or forks and only one watcher, so there is little popularity-based external validation. This is supporting evidence only and does not outweigh the active release and commit history for a small component.

Repo tooling

Composer is used as a build tool, but no security-scanning tools are configured, leaving a security-hygiene gap.

Security policy

The repository has no formal security policy. The README does provide a security email address, which partially compensates for the missing SECURITY.md-style policy but leaves reporting guidance less formal.