The package has a clear README, tests, MIT licensing, and a small dependency surface. Its sole publisher and repository owner show no commits or releases for nearly four years, while the repository has no security policy or scanning. Pin this version only if its stable API meets your needs.
52%
Total Score
50
100
80
50
Only one registry account has publishing access. That is a limited publisher base and creates a meaningful continuity risk for a user-owned project.
The package has made no releases in nearly four years, despite eight releases clustered in its first two days. This strongly lowers confidence in ongoing maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating possible abandonment.
Composer build tooling is present, but no security scanning tools are configured. The absence of scanning is a modest hygiene weakness, not a severe risk by itself.
The repository has no security policy, leaving no documented process for reporting or handling security issues. This is a transparency and maintenance gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.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.