Usable with caveats: the release is licensed, stable, backed by an organization, and recently updated, but it has only two releases across roughly two and a half years, one active contributor, and limited documentation and security-process evidence.
68%
Total Score
83
100
75
50
The package has no README, which makes this must-use plugin harder to understand and adopt. However, the exact release has GitHub release notes, which provide some change documentation.
There are only two releases over about 2 years and 8 months, with a median gap of about 2 years and 6 months; this indicates a sparse maintenance history despite one release in the last 12 months.
All two recent commits came from one contributor, creating a thin individual maintenance base. Organization ownership provides some handoff capacity, so this is a caution rather than a severe abandonment signal.
The repository name does not exactly match the registry package name, and no README mention was available, leaving some uncertainty about package-to-repository identity. The repository URL nevertheless closely reflects the package's distinctive name, so this is a limited concern.
Composer is used as a build tool, which fits the package ecosystem, but no security-scanning tools were detected, leaving a security-process gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers Version ^1.0 | ^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.