Risky to adopt: the package has had no release or repository activity for nearly four years. Its license, documentation, tests, and clean workflow checks are positives, but they do not offset the strong abandonment risk.
42%
Total Score
50
67
67
The latest release was published nearly four years ago, with no releases in the last 12 months; the seven releases were concentrated within about 10 days. This is strong evidence of abandonment for an SDK that must track an external API.
The repository recorded zero commits and zero active maintainers in the last three months, providing no evidence of ongoing maintenance to compensate for the stale release history.
The repository uses Composer for builds, showing basic project tooling, but it has no security scanning configured. That is a modest transparency and maintenance gap, not a standalone severe risk.
The linked repository is not archived, which avoids the strongest abandonment signal, but its last push was nearly four years ago and therefore does not offset the lack of current activity.
No security policy was found in the repository, leaving vulnerability-reporting expectations unclear. The mature documentation and repository structure provide some compensation, so this is a limited concern.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.5 || ^7.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.