The package includes a README, tests, an MIT declaration, and no install-time scripts. Its small release history and single publisher provide little evidence of sustained support, while the repository’s lack of a package reference makes ownership less clear.
45%
Total Score
50
100
69
75
There were no commits and no active maintainers in the last three months. Combined with the long release gap, this materially increases abandonment risk.
Only two releases exist, with none in the last 12 months and about 975 days between releases. This is strong evidence of low maintenance activity, though it does not prove abandonment by itself.
The repository name does not match the package name and its README does not mention this package. That makes the package-to-source relationship less clear and raises a genuine provenance concern.
The repository has zero stars and forks and only two watchers. Popularity is supporting evidence rather than a verdict, but these numbers provide little independent evidence of community support.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and hygiene gap rather than evidence of an unsafe release.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.2 | — | — |
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.