pop-schema/metaquery-wp

This is a generally healthy and actively maintained release: it has a five-year history, 161 releases, 32 releases in the last 12 months, a stable non-prerelease version, a non-deprecated registry entry, an active non-archived organization-owned repository, tests, a README, a license file, and no install-time lifecycle scripts. The main dependency risks are concentrated maintenance, with one contributor producing all 14 commits in the last three months, and the absence of a repository security policy; these are meaningful but do not outweigh the strong release and repository continuity evidence. The package is reasonable to depend on, with normal organizational and maintainer-continuity risk.

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 linked repository is owned by an organization and the package has strong observed release activity.

Repo bus factor

One contributor made all 14 commits in the last three months, creating a genuine single-person continuity risk. Organization ownership provides some handoff potential, but no second active contributor is shown to be available.

Repo popularity

The repository has zero stars and forks and one watcher, indicating limited public adoption or visibility; this is supporting caution only and does not outweigh the active release history.

Repo tooling

Composer is used as a build tool, but no security-scanning tools are detected; the build setup is present while automated security coverage is not evident.

Security policy

The repository has no SECURITY.md or other detected security policy. The README provides an email-based reporting instruction, which partially improves transparency but does not replace a repository policy.