The repository is actively updated, tested, licensed, and backed by an organization. Maintenance is concentrated in one contributor, and workflow actions are all unpinned; there is also no security policy or scanning.
78%
Total Score
75
100
94
75
One contributor made all 25 commits in the last three months, creating a meaningful continuity risk despite the repository's organizational ownership.
The repository recorded 25 commits in the last three months, showing current activity, but all activity came from one maintainer.
Composer build tooling is present, but no security-scanning tools were detected, leaving automated security coverage unclear.
The repository has no security policy, so users have no documented private reporting path or stated security-maintenance process.
Both workflows were analyzed without high-confidence findings, have no untrusted checkouts or script injection, and one scopes permissions at job level. However, all six action references are unpinned, weakening build reproducibility and update control.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^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.