The package has a clear README, a declared Apache-2.0 license, and only two runtime dependencies. It offers little evidence of testing or security oversight, and the linked repository does not identify the package in its README.
38%
Total Score
0
100
71
75
Only two releases were published, both in August 2022, with no release in the last four years. This is strong evidence of abandonment for a package developers may need to rely on for fixes.
The repository has recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving little evidence of ongoing maintenance.
The repository name does not match the package name and its README does not mention the package, so the source-package relationship is less transparent and warrants caution.
Composer build tooling is present, but no security scanning tools are configured. This weakens automated oversight without indicating a direct dependency risk by itself.
The repository has no security policy. That is a transparency gap, although the package's small scope and simple dependency profile limit how much weight this carries.
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.