Security scanning and a security policy are absent, reducing transparency for a package with substantial WordPress integration. The package is licensed and includes a substantial readme, while its simple dependency profile and lack of install scripts reduce integration risk.
35%
Total Score
0
100
75
75
The latest release was October 24, 2019, with no releases in the last 12 months and a package age of 2,744 days. This is strong evidence that the assessed release is no longer actively maintained.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the prolonged lack of maintenance shown by the release history.
Composer is used for builds, but no security scanning tools are configured. The missing scanning reduces supply-chain transparency, though it is not by itself evidence of an unsafe release.
The repository has no security policy, leaving vulnerability reporting and maintenance expectations undocumented. This is a transparency gap for a plugin that integrates deeply with WordPress sites.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers Version >=1.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.