The 0.x version line and absent security scanning reduce confidence for long-lived integrations. Clear licensing, tests, documentation, and release notes provide useful transparency.
58%
Total Score
25
100
71
83
The package has made no registry release in roughly eight years, with zero releases in the last 12 months. The repository was pushed in 2024, which provides some compensating evidence but does not show current publishing activity.
There were zero commits and zero active maintainers in the last three months, indicating no current development momentum. This is consistent with the long gap in registry releases.
There were no new or closed issues or pull requests in the last month, while seven pull requests remain open. That suggests limited recent project activity, although issue totals are partly unknown.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a hygiene gap rather than evidence of unsafe code.
The repository has no security policy, leaving users without a documented reporting and response process. This matters for a client handling OAuth credentials and API access.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.3 | — | — |
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.