Organization backing, a clear package layout, and release notes provide useful context. Pin the workflow's container image and note that no security policy is published.
58%
Total Score
67
83
50
The latest release was published over five years ago, with no releases in the last 12 months. This materially raises maintenance and compatibility risk despite the package's earlier release history.
All recent commits came from one contributor. Organization ownership provides some ability to hand off maintenance, but current contributor concentration remains a modest continuity concern.
The repository had two commits in the last three months, showing some current activity, but that activity is too limited to fully compensate for the absence of registry releases.
The repository has no published security policy. For an SDK handling API credentials, this reduces transparency around vulnerability reporting and response.
The audit found a high-confidence use of a floating container image tagged latest. The workflow otherwise uses read-only permissions and has no untrusted checkout or script-injection findings, so this is a hygiene caution rather than a standalone severe risk.
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.