Usable with caveats: the package is clearly licensed, documented, correctly backed by its repository, and has no install-time scripts or deprecation notice. However, it has only two releases, no release in roughly 22 months, and no commits or active maintainers in the last three months, so maintenance appears stalled.
58%
Total Score
33
100
83
90
The repository had zero commits and zero active maintainers in the last three months. Combined with the old latest release, this is the main abandonment concern.
The package is backed by an individual-owned repository rather than an organization, so the single registry maintainer reflects a genuinely thin maintainer base rather than ordinary organization publishing hygiene.
Only two releases were published, both within about four days, and there have been no releases in roughly 22 months. That weakens evidence of ongoing maintenance for a package integrating with an external API.
There are no open issues or pull requests, and no issue or pull-request activity in the last month. This is not severe alone, but it offers no evidence of current maintenance or user support.
Composer is used for the build, but no security-scanning tools are configured. The missing scanning is a transparency gap, though it is partly mitigated by the package's simple dependency profile.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^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.