orkan/wp-base

The package has a clear MIT license, README, tests, changelog, and a small runtime dependency set. Its single-user project has no security policy or scanning, which increases maintenance risk.

Latest 3.0.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with the last repository push being about two years and four months ago. This materially raises abandonment risk.

Project backing

The registry namespace and repository are owned by the same individual account, which is consistent with a small personal project but provides limited organizational continuity.

Release history

All five releases arrived within about 15 days, but there have been no releases in the last 12 months and the latest release is about two years and four months old. This is a meaningful maintenance concern for a package intended as a WordPress foundation.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is not required for health, but this provides little supporting evidence of active community use or review.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. For a small PHP package this is a hygiene gap rather than evidence of an unsafe release.