There is no detectable license or security policy, limiting transparency and making reuse harder to assess. The single runtime dependency and organization-owned repository provide some useful context, but do not offset the long maintenance gap.
48%
Total Score
50
100
75
75
The latest release was published in December 2017, about 8 years and 9 months ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the repository remaining available.
The repository recorded zero commits and zero active maintainers in the last 3 months. That reinforces the stale release history and indicates no current maintenance capacity.
No license declaration or license file was detected in the package or repository. That creates a concrete reuse and legal-transparency concern.
The linked repository has no security policy. This is a maintenance and vulnerability-reporting gap, although it is not evidence of malicious behavior.
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.