Documentation is present, and the small dependency set keeps integration relatively simple. The declared Apache-2.0 license conflicts with the BSD-2-Clause file, and no security policy is provided.
30%
Total Score
0
100
50
50
The package has only two releases, both in June 2017, with no releases in the last 12 months. This long release gap 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 being in June 2017. There is no observed current maintenance capacity.
A license file is present, but it identifies BSD-2-Clause while the manifest declares Apache-2.0. The mismatch creates uncertainty about which terms govern this release.
The linked repository has no security policy. For an API client handling access tokens, this is a transparency and vulnerability-reporting gap.
The latest version is 1.0.0-alpha, so the package remains prerelease despite its age. That reduces confidence in API stability and ongoing maturity.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ~5.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.