There is no README, security policy, or automated security scanning to support consumers and maintainers. The MIT declaration, clean install scripts, and release notes help, but the project offers limited transparency around ongoing care.
38%
Total Score
50
100
72
88
The package has had only two releases, with the latest published over seven years ago and none in the last 12 months. This is strong evidence of abandonment risk, despite the stable 1.1 version.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. No newer activity is provided to compensate for that stagnation.
The package has no README, which makes integration harder for consumers, while the GitHub release notes for this exact version provide some release documentation. Missing tests and changelog files in the artifact are normal packaging practice.
The repository has two stars, zero forks, and one watcher, providing little supporting evidence of broad community review or adoption. Popularity is only supporting evidence and does not independently determine health.
Composer build tooling is present, but no security scanning tools were detected. That weakens ongoing maintenance assurance, although the absence of scanning alone is not severe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ~6.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.