Documentation, tests, and licensing are in place, and the repository still matches the package. The project has shown no release or commit activity for over seven years, with no security scanning or policy, so maintenance risk is substantial.
42%
Total Score
25
100
72
75
The package has had 17 releases but none in the last 12 months; its latest release was published over seven years ago. This strongly raises abandonment risk despite its established release history.
There were zero commits and zero active maintainers in the last three months. Combined with the last release being over seven years ago, this is strong evidence that maintenance has stopped.
The registry namespace and repository owner match, and the owner is an individual account rather than an organization. This is consistent ownership but offers limited backing capacity.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these very low counters provide little evidence of an active user or contributor base.
Composer is used for builds, but no security scanning tools are configured. The missing scanning is a transparency and hygiene gap, though it is less significant than the long inactivity period.
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.