The repository is tiny and uses one runtime dependency, which limits complexity. Organization backing and a non-archived repository help, but there is no security policy or license evidence to support long-term adoption.
40%
Total Score
50
100
67
50
This package has had only one release, published about seven years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and indicating no observable current maintenance.
Neither the package metadata nor the artifact or repository contains recognized license evidence. Developers cannot clearly establish the terms for using or redistributing this dependency.
Composer is used as a build tool, but no security scanning tooling is present. This is a modest hygiene gap rather than a standalone adoption blocker.
The repository has no security policy, leaving vulnerability reporting and maintainer response expectations undocumented. This is a transparency gap, though it is less serious than the lack of maintenance.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| 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.