The MIT license, clear README, matching repository, and small runtime dependency set make the package straightforward to inspect and integrate. Its release and commit activity stopped years ago, with no security scanning or policy to indicate ongoing maintenance.
42%
Total Score
0
79
50
The latest release was in September 2017, with no releases in the last 12 months despite eight total releases. Nearly nine years without a release is strong evidence of abandonment for a package used as an integration dependency.
There were zero commits and zero active maintainers in the last three months, consistent with the repository having been inactive for over eight years. This materially raises abandonment risk.
Composer is used for builds, but no security-scanning tooling is present. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This adds a maintenance gap alongside the prolonged inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers 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.