getpop/comments-wp

This release shows strong signs of an active, mature implementation: it has 162 releases over roughly 5 years, 33 releases in the last 12 months, a stable non-prerelease version, a linked and correctly matching repository, recent commits, tests, licensing, and no install-time lifecycle scripts. However, the registry explicitly marks the package as abandoned and identifies `pop-schema/comments-wp` as its replacement, which is a decisive dependency-safety concern: new projects should depend on the replacement rather than this package. Maintenance is also concentrated in one contributor, and the repository lacks security scanning and a formal security policy, though these are secondary to the deprecation status.

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/comments-wp` as its replacement. This is a severe adoption risk even though the package has recent releases and repository activity.

Repo bus factor

All 14 recent commits came from one contributor, giving a 100% top-contributor share. The organization-owned repository provides some maintenance backing, but no second recent contributor is shown, so succession risk remains.

Repo issue activity

There were no new issues or pull requests in the last month and no merged pull requests; with recent commits still present, this suggests limited collaboration rather than clear abandonment.

Repo popularity

The repository has only 1 star and 0 forks, indicating limited external adoption. Popularity is supporting evidence rather than a verdict, so this is a minor caution rather than a severe risk.

Repo tooling

Composer build tooling is present, but no security scanning tools are reported. The build setup is adequate, while the missing security automation modestly reduces transparency.