Documentation is clear, the package is licensed, and the repository includes tests. Its single-maintainer project has seen no commits or releases for nearly six years, so fixes and compatibility work are unlikely.
38%
Total Score
25
100
75
75
The package has only two releases, both published in November 2020, with no releases in the last 12 months. This indicates prolonged abandonment risk despite the short initial release interval.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's nearly six-year release gap. The repository is not archived, but there is no observed recent maintenance.
Only one registry account has publishing access. This is a thin publishing base, and no provided project-backing signal shows organizational ownership to compensate for that concentration.
Composer build tooling is present, but no security-scanning tool was detected. This is a modest hygiene gap rather than evidence that the release is unsafe.
The linked repository has no security policy. This reduces transparency for reporting and handling vulnerabilities, although it is secondary to the much larger maintenance concern.
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.