Usable with caveats: the release is licensed, documented, tested, and backed by a matching repository, but it has had no registry release in nearly eight years and no commits in the last three months. Its beta status and broad runtime dependency set add maintenance risk for a WordPress project.
55%
Total Score
25
50
71
75
There have been 9 releases since March 2016, but none in the last 12 months and the latest registry release was August 2018. This long release gap materially raises abandonment and compatibility risk.
The repository recorded zero commits and zero active maintainers in the last three months. Together with the absent registry releases, this indicates currently inactive maintenance.
The package declares 11 runtime dependencies and no development dependencies, creating a relatively broad compatibility surface for a WordPress plugin and making long-term maintenance more dependent on older upstream components.
There are 12 open issues, with no new or closed issues and no pull-request activity in the last month, suggesting unresolved maintenance work and limited project responsiveness.
Composer is used for builds, but the repository reports no security scanning tools. That is a transparency and supply-chain hygiene gap, though it is partly offset by the visible source tree and dependency metadata.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
xrstf/composer-php52 Version 1.* | — | — |
webdevstudios/cpt-core Version dev-master | — | — |
techcrunch/wp-async-task Version dev-master | — | — |
tgmpa/tgm-plugin-activation Version ^2.5.2 | — | — |
webdevstudios/taxonomy_core Version ^0.2.4 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.