The package is documented, tested, and licensed, with a repository that matches its name. Its last release and repository push were about 11 years ago, and no recent commits or security policy are visible; pinning it would carry substantial maintenance risk.
38%
Total Score
0
71
50
The latest release was published about 11 years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a dependency whose compatibility may need ongoing maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release hiatus. No provided signal shows current maintenance capacity.
Composer build tooling is present, but no security scanning tools were detected. This is a modest hygiene gap rather than evidence that the release is unsafe on its own.
The linked repository is not archived, which avoids the strongest repository-level abandonment signal. However, its last push was still about 11 years ago, so this does not offset the stale activity.
The repository has no security policy. This is a transparency and response-process gap, and no other provided signal compensates for it.
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.