getpop/post-tags-wp

This release shows strong evidence of active development and a real, organization-backed source repository: it has 162 releases over roughly 5 years, 33 releases in the last 12 months, recent commits, tests, a matching repository, and an explicit GPL license. However, the package is marked abandoned on Packagist with a named replacement, which is a decisive dependency-health concern: new projects should migrate to the replacement rather than adopt this package. The single-contributor activity and absent security policy add caution, but the registry deprecation is the primary reason this release falls in the critical range.

Latest 19.2.4

Packagist

22%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Registry deprecation

Packagist marks the package as abandoned and specifies pop-schema/post-tags-wp/ as the replacement. Even though the package remains actively released, adopting a deprecated package creates avoidable maintenance and migration risk.

Maintainers

Only one registry account has publish access. This is a modest publishing concentration risk, though it is partly compensated by the organization-owned repository and demonstrated recent release activity.

Repo bus factor

All 14 recent commits came from one contributor, giving the repository a bus-factor concern. The organization-owned repository provides some handoff capacity, so this is caution rather than a severe risk.

Repo issue activity

There were no new issues or pull requests in the last month and no merged pull requests. This provides little evidence of community maintenance, though the recent commit activity shows the project is not inactive.

Repo popularity

The repository has only 1 star, 0 forks, and 1 watcher, indicating limited external adoption. Popularity is supporting evidence rather than a verdict, so this lowers confidence in broad community support but is not decisive given the active release history.