Clear licensing and documentation make integration straightforward. The project has no security policy, and recent work is concentrated in one contributor.
70%
Total Score
67
100
88
75
The latest registry release was published nearly seven years ago, with no releases in the last 12 months. This creates meaningful version-staleness risk even though the package has a stable release history.
All two recent commits came from one contributor, leaving maintenance activity concentrated. Wikimedia organization backing provides some handoff capacity but does not remove the current concentration concern.
The repository recorded two commits in the last three months, showing recent activity despite the old registry release. Activity is limited, so it does not fully offset release staleness.
The project uses Composer build tooling, but no security-scanning tools were detected. The small package and organization backing partly reduce the significance of this tooling gap.
No repository security policy was found, reducing transparency for reporting and handling vulnerabilities. This is a hygiene concern rather than evidence of an unsafe release.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers Version ~1.0.1 | — | — |
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.