The package includes tests, a changelog, release notes, a license, and a security policy. Its registry has had no release in 12 months, and the repository shows no commits in the last 3 months, so maintenance looks uncertain.
62%
Total Score
50
100
83
100
The registry namespace and repository owner match, so the source ownership is consistent. The owner is an individual account, which offers less organizational redundancy than an organization-backed project.
Only two releases were published, both about 603 days ago, with no release in the last 12 months. That unusually limited cadence lowers confidence in ongoing maintenance.
There were zero commits and zero active maintainers in the last 3 months. This is direct evidence of currently stalled development and is the main maintenance concern.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, so this lowers corroboration but is not decisive for a small or specialized package.
The repository uses Make and Composer, showing a defined build process, but no security-scanning tools were detected. This is a modest hygiene gap rather than a standalone adoption blocker.
We didn't find any vulnerabilities for this package.
| 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.