Licensing and documentation are in place, and the project is not archived or deprecated. Its old WordPress stack and absent security tooling make long-term maintenance and safe upgrades difficult.
32%
Total Score
0
75
50
The latest release was published over 10 years ago, with no releases in the last 12 months. Twelve releases show some historical activity, but the prolonged pause strongly raises abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release gap and indicating no visible ongoing maintenance.
Composer is used for builds, but no security scanning tool is configured. That is a modest transparency and maintenance gap rather than evidence of an unsafe release by itself.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This matters more for a WordPress stack with multiple runtime dependencies.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
asmbs/wp-ip Version ^1.0 | — | — |
asmbs/wp-unblog Version ^1.1 | — | — |
vlucas/phpdotenv Version ^2.2 | — | — |
composer/installers Version ^1.0 | — | — |
johnpbloch/wordpress Version ^4.4 | — | — |
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.