Package Health/wpscholar/wp-post-expiration

wpscholar/wp-post-expiration

The README, package license, and matching source repository make integration and ownership clear. Maintenance is the main concern: the last registry release was nearly nine years ago, repository commits have stopped, and 23 pull requests remain open.

Latest 1.1.1

Packagist

55%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published nearly nine years ago, with no releases in the last 12 months. This is strong evidence of a stale release line, although the repository remained available and was pushed more recently.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old registry release, this materially raises abandonment risk.

Repo issue activity

There are no open issues, but 23 pull requests remain open and none were merged in the last month. That backlog suggests limited follow-through despite some repository activity.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are configured. The missing scanning is a modest transparency and maintenance gap.

Security policy

The repository has no security policy. For a small WordPress module this is a limited gap, but it provides no documented process for reporting or handling vulnerabilities.