Clear licensing, documentation, and organization backing support adoption. The package has seen no registry release for nearly 7 years, and repository activity has been inactive for more than 5 years; install-time scripts add a small operational concern.
52%
Total Score
75
100
75
67
The latest release was published nearly 7 years ago, with no releases in the last 12 months. Its earlier eight-release history shows an established package, but not current maintenance.
The package runs post-install and post-update Composer scripts, adding execution during dependency operations. This is relevant operational risk, though the signal does not show that the scripts are unsafe.
There were no new or closed issues or pull requests in the last month, while two issues and one pull request remain open. This indicates little recent project activity.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a minor hygiene gap rather than evidence of abandonment by itself.
The repository is not archived, which preserves a path for maintenance, but it was last pushed more than 5 years ago. That inactivity reinforces the release-history concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/composer Version ^1.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.