Usable with caveats: it has a long release history, clear licensing, a substantial package, and a matching source repository. However, there have been no registry releases in the last 12 months and no repository commits or issue resolution in the last three months, so maintenance appears to have slowed.
68%
Total Score
67
100
88
88
The project has existed since August 2019 with 44 releases and a typical historical interval of about 25 days, but it has had no release in the last 12 months, indicating materially slower maintenance.
The repository recorded zero commits and zero active maintainers in the last three months. Together with the lack of releases in the last year, this is a meaningful maintenance and abandonment concern.
There were no new or closed issues and no merged pull requests in the last month, while 13 issues and 5 pull requests remain open; this suggests limited recent project response.
Composer is used for builds, but no security scanning tools were detected. This is a hygiene gap, though it is not by itself evidence that the package is unsafe to use.
The repository has no security policy. For a WordPress plugin handling administrative editing features, this weakens vulnerability-reporting transparency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers Version ^1.2|^2.0 | — | — |
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.