The repository has tests, release notes, and organization backing, while the package has no install scripts. Workflow actions are unpinned and no security policy is published, and recent work is concentrated in one contributor.
68%
Total Score
67
100
94
67
One contributor made all one recent commit, giving the project a concentrated short-term bus factor. Organization ownership provides some handoff capacity, but recent individual activity remains narrow.
Only one commit was recorded in the last three months, so maintenance activity is currently light. The recent release and organization backing provide some compensation, but not enough to remove the concern.
Composer is used for builds, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap rather than evidence of an unsafe release.
The repository has no published security policy. For an API client handling authentication credentials, this leaves vulnerability-reporting expectations unclear.
The single workflow was fully analyzed with no injection or high-severity findings, but both of its two action references are unpinned. That weakens build reproducibility and action supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.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.