The repository matches the package and provides a README, release notes, and an MIT license. No commits or releases have appeared for roughly nine and ten years, and the project has no security scanning or policy. Pinning this release is risky for a current integration.
38%
Total Score
25
71
75
The package has had no releases in roughly ten years, with zero releases in the last 12 months. Its five-release history shows an established package but no current maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with a project that has been inactive for roughly nine years.
There were no new or closed issues or pull requests in the last month, while four issues and nine pull requests remain open. This suggests unresolved maintenance demand without recent response.
Composer build tooling is present, but no security scanning tools were detected. For a client handling API credentials, that is a meaningful repository hygiene gap.
The repository has no security policy. This reduces transparency about how vulnerabilities should be reported, although it does not by itself show that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzle/guzzle Version ~3.8 | — | — |
commerceguys/guzzle-oauth2-plugin Version ~1.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.