There have been no commits in three months and no release in the past year, so fixes may be slow. The organization-owned project and MIT license provide continuity, but the repository does not mention this package in its README.
62%
Total Score
75
100
81
75
The package has 13 releases over roughly seven years with a historical median interval of about 80 days, but no release appeared in the past 12 months. This indicates a meaningful slowdown, though not abandonment by itself.
The repository had no commits and no active maintainers in the past three months. Combined with the lack of recent registry releases, this raises the risk that defects will not be addressed promptly.
The repository name does not match the package name and its README does not mention the package. Organization backing and the matching package contents partly reduce concern, but the relationship is less transparent.
Composer build tooling is present, but no security scanning tool was detected. That is a transparency and maintenance gap, though it is not severe on its own.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This lowers transparency but does not by itself make the release unfit.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.3|^7.0.1 | — | — |
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.