Clear licensing and a matching source repository improve transparency. The solo maintainer and absent security policy leave little evidence of ongoing support.
48%
Total Score
50
86
50
The registry lists one maintainer, which limits the visible publishing bus factor. The matching personal repository provides some continuity, but not broader maintenance capacity.
The latest release was published in March 2019, with no releases in the past seven years. That long release gap is a substantial abandonment concern for a dependency.
The repository recorded zero commits and zero active maintainers in the past three months, consistent with the long release gap and providing no evidence of current maintenance.
The project uses Composer, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the release is unsafe.
The linked repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. The package's age and inactive development make this gap more relevant.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers Version >=1.0.8 | — | — |
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.