The package is clearly licensed, documented, and tied to the matching organization repository. No recent commits or releases reduce confidence that this exact version will keep up with WordPress and its dependencies.
63%
Total Score
75
50
88
75
Seven runtime dependencies, including deployment, database, media, and WordPress tooling, create a meaningful dependency surface that may require coordinated maintenance. No separate evidence shows those dependencies are currently problematic.
The package has 29 releases, but its latest registry release was over three years ago and there were no releases in the last 12 months. That materially raises maintenance risk for a WordPress deployment package.
The repository had no commits and no active maintainers in the preceding three months. This weakens evidence of ongoing maintenance even though it was pushed more recently overall.
Composer is used for builds, but no security-scanning tooling is reported. This is a modest transparency and hygiene gap rather than evidence that the release is unsafe.
The repository has no published security policy, leaving vulnerability reporting and response expectations undocumented.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
wp-cli/wp-cli Version ~2.1 | — | — |
deployer/deployer Version ~7.0 | — | — |
sourcebroker/deployer-loader Version ^4 | — | — |
wp-cli/search-replace-command Version ~2.0 | — | — |
sourcebroker/deployer-extended Version ^18 | — | — |
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.