The tiny package and narrow dependency set are easy to understand, but security documentation and automated scanning are absent. Its old, inactive project context makes long-term compatibility and support uncertain; pinning 3.0.2 is prudent if adoption is necessary.
30%
Total Score
0
58
50
The last registry release was in October 2016, nearly ten years ago, with no releases in the last 12 months. This strongly indicates abandonment risk despite the package having five historical releases.
The repository had zero commits and zero active maintainers in the last three months, consistent with a project that has not been maintained for years. The small package size does not remove the support risk.
No declared license or license file was found. Without licensing terms, legal reuse and redistribution are unclear.
Composer build tooling is present, but no security scanning tools were detected. For an old, dependency-bearing package, this is a modest transparency and maintenance gap.
The repository has no security policy. This is a hygiene gap that leaves vulnerability reporting and response expectations undocumented.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
sanatorium/path-installers Version >=1.0.0 | — | — |
cartalyst/composer-installers Version >=1.2.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.