Its broad 18-package runtime dependency set increases upkeep burden, while the repository has no security scanning or policy. The matching repository, license, changelog, and release notes provide useful transparency.
42%
Total Score
25
50
81
50
The package has only one release, published nearly four years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the long release gap rather than showing ongoing maintenance.
The package declares 18 runtime dependencies, including WordPress, plugins, and installers, creating substantial ongoing compatibility and update burden for an inactive project.
Only one registry maintainer is listed. That is a thin publishing base for a user-owned project and increases continuity risk when combined with absent recent activity.
Composer build tooling is present, but no security scanning tools were detected. The build setup is positive, while the missing security checks modestly lower confidence in maintenance hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
oscarotero/env Version ^2.1 | — | — |
roots/wp-config Version ^1.0 | — | — |
vlucas/phpdotenv Version ^5.3 | — | — |
composer/installers Version ^1.10.0 | — | — |
johnpbloch/wordpress Version 6.0.2 | — | — |
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.