A clear README, MIT licensing, tests, and no install scripts make adoption straightforward. Unpinned workflow actions and the project's four-day history leave some maturity and build-integrity risk.
78%
Total Score
100
100
88
67
The package is only 4 days old, with 7 releases and a median interval of about 7 hours, so long-term maintenance and stability cannot yet be established.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest gap in repository security hygiene.
The repository has no security policy, which makes vulnerability-reporting expectations less transparent; this is a hygiene concern rather than evidence of abandonment.
Both workflows were analyzed without high-confidence audit findings or unsafe untrusted triggers, but all 7 action references are unpinned and one workflow grants top-level write access, weakening build reproducibility and token minimization.
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.