The package has a clear README, MIT license, matching repository, and organization backing. It lacks a security policy and security scanning, which adds transparency and maintenance risk.
45%
Total Score
50
71
75
There has been only one release, published over five years ago, with no releases in the last 12 months. This is strong evidence that the package is no longer actively maintained.
The repository had zero commits and zero active maintainers in the last three months. Combined with the old last push, this indicates sharply reduced maintenance capacity.
The repository uses Composer, but no security scanning tools were detected. That is a modest supply-chain hygiene gap, not evidence that the package is unsafe by itself.
No security policy was found in the repository, reducing transparency about vulnerability reporting and response. This matters more for a package intended to form part of a deployed WordPress application.
Version 0.1.0 is not a stable major release, which indicates an immature release line. The absence of later versions reinforces that it has not matured since its initial publication.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
roots/wordpress Version ^5.0.0 | — | — |
ffraenz/private-composer-installer Version ^5.0 | — | — |
whitespace-se/wordpress-bundle-standard Version ^4.0.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.