The README and two runtime dependencies make the plugin straightforward to integrate. Its source is clearly tied to the package, but the long period without maintenance and proprietary licensing create substantial adoption risk.
38%
Total Score
50
50
The package has only one release, published about five years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency that may need compatibility or security updates.
The manifest declares a proprietary license, but no license file was detected in the package or repository. This creates a material transparency and redistribution concern for an open-source dependency.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide no meaningful community-maintenance signal.
Composer is used as the build tool, but no security scanning tooling is present. This is a modest supply-chain hygiene gap rather than evidence that the package is unmaintained by itself.
The repository has no security policy. That reduces transparency around vulnerability reporting, although the absence alone is not proof of a security problem.
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.