Regular releases, a clear README, tests, and an explicit license support ongoing use. Workflow actions are unpinned and the project lacks a security policy, limiting maintenance hygiene.
68%
Total Score
75
100
88
75
All four recent commits came from one contributor, so maintenance depends entirely on a single person despite the recent activity.
The repository name does not match the package name and its README does not mention the package, so the linkage is not clearly established by the source project.
The project uses Make and Composer, but no security-scanning tools were detected, leaving automated security coverage limited.
The repository has no security policy, reducing transparency about how vulnerability reports are handled.
The only workflow was fully analyzed with no dangerous triggers or audit findings, but both of its two action references are unpinned, weakening build reproducibility.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.0|^8.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.