Risky to depend on: the last release and repository activity were in October 2016, with no releases or commits in the past three months. It is small and transparent enough to inspect, but its long abandonment period makes compatibility and maintenance a liability.
28%
Total Score
0
71
75
The package has only 3 releases, all concentrated around September–October 2016, and none in the last 12 months. This long release gap is strong evidence of abandonment risk.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the release history showing no activity since October 2016. This materially lowers confidence in ongoing maintenance.
The repository has 1 star, 0 forks, and 1 watcher, providing little evidence of broad community use or external support. Low popularity is supporting evidence rather than a verdict, but it offers no meaningful buffer against the stale maintenance record.
The linked repository is not archived, which avoids the strongest abandonment signal, but its last push was still in October 2016. The unarchived status does not compensate for nearly a decade without observed activity.
No security policy was found in the repository. For a library that performs self-update behavior, this is a transparency gap, although the absence of a policy is less decisive than the prolonged inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version 6.* | — | — |
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.