The package has a clear README and a source repository that matches its name, but it has no security scanning and relies on one publisher. Its install-time automation makes compatibility with current WordPress and Composer versions especially important.
47%
Total Score
25
79
50
The latest release was published in March 2022, and there have been no releases in the last 12 months despite the package being over four years old. The five-release history shows an initially active project but not current maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and indicating a strong abandonment risk.
One registry publisher is a limited maintainer base, so ongoing support depends on a single person. The matching source repository provides some ownership clarity but does not offset the lack of recent activity.
The project uses Composer, which provides basic build structure, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The source repository has no security policy, leaving no documented route for reporting or handling vulnerabilities. This matters for a package that automates WordPress deployment.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/composer Version ^2.1.8 | — | — |
composer/installers Version ^2.0 | — | — |
johnpbloch/wordpress Version ^5.8.1 | — | — |
cweagans/composer-patches Version ^1.7 | — | — |
wpackagist-plugin/akismet Version ^4.2.1 | — | — |
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.