The MIT license, release notes, and matching repository provide useful transparency for integration. The single-user project has no recent commits or security policy, so ongoing maintenance capacity remains uncertain.
60%
Total Score
50
86
83
The repository is owned by an individual user rather than an organization, so there is no visible organizational backing to offset the thin maintenance base.
All six releases were published during a short period in December 2025, and the latest release was about 9 months ago. This suggests an unfinished or inactive maintenance pattern rather than an established cadence.
The repository recorded zero commits and zero active maintainers in the last 3 months. That is a meaningful maintenance concern for a library consumers may need to rely on for API compatibility and fixes.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not evidence that the release is unsafe.
The repository has no published security policy, leaving the reporting and response process unclear for a client that handles API credentials.
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.