Tests, a README, and a matching source repository improve transparency, while the project has only one star and no security scanning. The package has seen no commits or releases since 2018, making maintenance uncertain.
42%
Total Score
50
100
78
75
The repository is owned by an individual account rather than an organization. This is not inherently unhealthy, but it provides no organizational backing to offset the long inactivity.
The package has made only three releases, all within about six days in June 2018, and none in the last eight years. This is a substantial abandonment concern despite the package not being deprecated.
There were zero commits and zero active maintainers in the last three months, consistent with the repository's last push in 2018. This materially increases abandonment risk.
The repository has one star, one fork, and one watcher, indicating very limited visible adoption. Popularity is supporting evidence rather than a verdict, but it provides little confidence in long-term support.
Composer build tooling is present, but no security scanning tools were detected. That is a real hygiene gap for a dependency intended for application integration.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version 6.3 | — | — |
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.