Clear licensing, tests, release notes, and organization backing improve confidence. The missing security policy and weak workflow pinning add practical maintenance overhead.
60%
Total Score
75
100
88
50
Only two releases were published, both within a short launch window, and no later release has appeared for about 200 days. This limited history leaves maturity and ongoing maintenance uncertain.
The repository recorded zero commits and zero active maintainers in the last three months. With only two releases overall, this is meaningful evidence of currently quiet maintenance.
The project uses Composer, but no security-scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk.
The repository has no published security policy, leaving the process for reporting and handling vulnerabilities unclear.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, or audit findings. However, all three action references are unpinned, weakening build reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.5 | — | — |
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.