codesoup/acf-admin-categories

Release historycaution

The package is about five months old and has only one release, so there is little release history to demonstrate sustained maintenance. Its recent origin partly explains the limited record but does not remove the uncertainty.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months. Because the repository was last pushed at the initial release, ongoing maintenance capacity is not yet demonstrated.

Repo popularitycaution

The repository has one star, no forks, and no watchers, indicating very limited external adoption. Popularity is supporting evidence rather than decisive proof, but it provides little independent confidence.

Repo toolingcaution

Composer is used for the build, but no security-scanning tool is configured. This is a maintenance and transparency gap, though it is not severe enough to make the release unfit on its own.

Security policycaution

The repository has no security policy, leaving no stated process for reporting and handling vulnerabilities. That weakens project transparency for a plugin intended to run in WordPress sites.