Its six-file artifact has a short usage README and only one runtime dependency, limiting integration and maintenance complexity. The repository is not archived or deprecated, but it has no security scanning and no recent issue or pull-request activity.
42%
Total Score
63
100
81
75
The latest release was published in July 2016, and there have been no releases in the past 12 months. Four releases over the package's lifetime show some history, but the long period without a release raises abandonment risk.
The repository recorded zero commits and zero active maintainers in the past three months, consistent with the package's long release gap. This is strong evidence that maintenance capacity is currently absent.
There are no open issues or pull requests and no issue or pull-request activity in the past month. This does not prove abandonment alone, but it provides no evidence of active maintenance.
Composer is used as a build tool, but no security scanning tools are configured. The missing scanning is a modest transparency and maintenance concern, not evidence of malicious behavior.
The repository has no security policy. For a small package this is a hygiene gap, though it is less significant than the lack of ongoing release and commit activity.
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.