The MIT license, tests, and normal dependency setup are positives. A single maintainer and missing security policy leave little evidence of ongoing support.
42%
Total Score
50
60
50
The package includes a README and tests, but the README's getting-started and usage sections are still marked TODO. The missing changelog is normal packaging practice, while the unfinished consumer documentation is a genuine gap.
The package has had no releases in the last 12 months, and its latest release was in September 2017, about 9 years ago. This is strong evidence of abandonment risk despite the four-release history.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the old latest release and indicating no current maintenance activity.
Composer build tooling is present, but no security-scanning tools were detected. This is a transparency and maintenance weakness, though it is less serious than the lack of recent development.
The linked repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This adds a transparency gap for a package that makes external API requests.
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.