sneaky/wordpress-api-client

Release historydanger

The latest release was over 5 years ago, and there were no releases in the last 12 months. This is strong evidence of abandonment for a package intended as an ongoing integration dependency.

Repo commit activitydanger

There were no commits and no active maintainers in the last 3 months, matching the long gap since the last release. This indicates that maintenance has effectively stopped.

Maintainerscaution

One registry maintainer is consistent with an individually owned project, but it leaves little visible maintenance redundancy when considered alongside the lack of recent activity.

Project backingcaution

The repository is owned by an individual account rather than an organization, so there is no visible organizational backing to offset the single-maintainer and inactivity concerns.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is not required for health, but these counts provide no supporting evidence of community review or adoption.