Its documentation is brief, and there is no security policy or automated workflow evidence. The MIT declaration, matching repository, and release notes provide basic transparency, but ongoing support remains uncertain.
55%
Total Score
50
75
75
Only two releases were published, both within about one day in March 2024, with no releases in the following roughly two and a half years. This is strong evidence of limited ongoing maintenance.
A single user account has registry publishing access, giving the project a thin operational base. The matching user-owned repository provides some accountability but does not offset the limited maintenance capacity.
The repository has zero stars and forks and only one watcher, indicating little visible adoption or community support. Popularity is supporting evidence rather than a verdict, so this is a modest concern.
The linked repository has no security policy. This is a transparency and issue-handling gap, though it is not by itself evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.8 | — | — |
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.