moogatw/wp-metabox

The package is small, clearly documented, and has a focused dependency profile. Its only release was nearly five years ago, with no recent commits and no tests or security policy, leaving maintenance and abandonment concerns.

Latest v1.0

Packagist

44%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published nearly five years ago, and none in the last 12 months. This is strong evidence of an inactive project for a dependency that may need compatibility maintenance.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the long release gap and increasing abandonment risk.

Project backing

The package and repository are owned by the same individual account, so the source linkage is coherent, but there is no organizational backing shown to offset the thin maintenance record.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counts provide no community signal to compensate for the inactive maintenance record.

Repo tooling

Composer is used as the build tool, which is appropriate for the package, but no security scanning tooling was detected. This is a modest transparency and maintenance gap for a dependency.