Package Health/getpop/api-endpoints-for-wp

getpop/api-endpoints-for-wp

This is a generally healthy and actively maintained release: it has a five-year history, 163 releases including 33 in the last 12 months, a stable non-prerelease version, a non-archived repository, clear licensing, tests, and recent repository activity. The main concerns are that all 14 recent commits came from one contributor, the repository has no security policy or security-scanning tooling, and no changelog was found in the artifact or repository. These are meaningful transparency and resilience gaps, but the organization-owned repository, active release cadence, package tests, and absence of risky lifecycle scripts keep the package within the healthy range.

Latest 19.2.4

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A substantial README and tests are present, but no changelog was found in either the package or repository. The README points to a changelog, yet the provided repository signal does not show one, leaving a modest transparency gap.

Repo bus factor

One contributor made 100% of the 14 commits in the last three months. Organization ownership provides some succession context, but no second active contributor is shown, so contributor concentration remains a resilience concern.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. This is a security-hygiene gap, though it is not evidence of maliciousness or an immediate release failure.

Security policy

The repository has no security policy, leaving disclosure guidance and the project's security process undocumented despite the README providing an email contact.