The release includes a license, README, and changelog, and it comes from an organization-owned repository. Its lone runtime dependency and lack of install scripts reduce packaging concerns, but do not offset the maintenance risk.
34%
Total Score
50
100
71
75
Only one release exists, published about seven years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk.
The repository had no commits and no active maintainers in the last three months, consistent with the package's long release gap and indicating little current maintenance capacity.
Composer is used as a build tool, but no security scanning tools are present. The missing scanning is a hygiene weakness, not the main adoption concern given the much stronger maintenance warning.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This adds a transparency gap, though it is secondary to the prolonged inactivity.
The assessed version is a prerelease alpha, and all recent releases are prereleases. That reduces confidence in stability for a dependency.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers Version ^1.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.