The project has no tests or security scanning, and only one registry maintainer. Its repository is still active enough to avoid abandonment being certain, but releases stopped about 5 years and 7 months ago.
45%
Total Score
50
75
75
The latest release was published on March 1, 2021, with no releases in the last 12 months. That long gap materially raises abandonment and compatibility risk.
Only one account has registry publishing access, leaving little visible publishing redundancy. The linked repository is user-owned rather than organization-backed, so there is no provided organizational support signal to offset this.
The repository recorded zero commits and zero active maintainers in the last 3 months; its last push was about 2 years and 8 months ago. This supports the aging release history as a maintenance concern.
Composer build tooling is present, but no security-scanning tool was detected. That is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy. For a package that sends application telemetry and handles configuration such as server tokens, this reduces the clarity of vulnerability reporting and maintenance expectations.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version >=6.0.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.