palmtree/wp-cleaner

Release historydanger

The latest release was about 8 years and 10 months ago, with no releases in the last 12 months and only two releases overall. This is strong evidence of an unmaintained dependency, despite the package not being deprecated.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the old last push, this indicates a substantial abandonment risk.

Package scaffoldingcaution

The package includes a README and its absence of tests or a changelog is normal for a published artifact, but the README leaves usage as “TBA,” limiting consumer guidance for this integration component.

Repo popularitycaution

The repository has zero stars and forks and only one watcher, providing little supporting evidence of adoption or community oversight. Popularity is not decisive by itself, but it offers no compensation for stale maintenance.

Repo toolingcaution

Composer is used as the build tool, but no security-scanning tooling is present. For a small PHP package this is a modest transparency and assurance gap, not proof of unsafe code.