The MIT license, clear README, release notes, and repository tests support basic transparency. But the project has been inactive for more than six years, making fixes and compatibility uncertain.
42%
Total Score
25
100
79
50
Only two releases were published, with the latest more than six years ago and none in the last 12 months. This is strong evidence of abandonment risk despite the stable 1.0.1 version.
The repository recorded zero commits and zero active maintainers in the last three months, corroborating the long release gap and leaving little evidence of ongoing maintenance.
A single registry maintainer is consistent with this user-owned project, but it provides a thin maintenance base and no demonstrated continuity to offset the inactivity.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not a standalone adoption blocker.
The repository has no security policy, so there is no documented path for reporting vulnerabilities or coordinating fixes. The inactive project makes this gap more significant.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.2 | — | — |
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.