The package offers little consumer documentation and no security policy; its organization ownership is the main counterweight. Its tiny, dependency-light implementation may be easy to inspect, but long-term support is not evident.
28%
Total Score
50
100
33
50
The package has had only two releases, both in September 2016, with no releases in the last 12 months and no release for nearly 10 years. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push occurring in 2016. No provided signal shows ongoing maintenance.
No license declaration or license file was found in the package or repository, leaving developers without clear permission to use or redistribute it.
The published artifact has no README, which is a meaningful documentation gap for a library consumers must integrate; the absence of tests and a changelog is normal packaging practice and is not penalized.
The repository has no security policy. This is a transparency and vulnerability-reporting gap, although the small package size limits its practical weight.
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.