The package is small and easy to inspect, with a focused dependency profile, tests, usage documentation, and an MIT license. Its lack of security policy or scanning leaves vulnerability response dependent on a project with little visible activity.
43%
Total Score
0
100
72
50
The latest release was published in July 2020, with no releases in the last 12 months despite the package being over six years old. This is strong evidence of abandonment risk, although the package has eight historical releases.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the release gap and indicating no recent maintenance capacity.
The repository has zero stars and forks and only one watcher, providing little supporting evidence of community adoption or outside oversight. Popularity is not decisive for a small package, but it does not offset the inactivity.
Composer build tooling is present, but no security-scanning tools were detected. That weakens automated oversight, though the small 21-file codebase limits the significance of this gap.
The repository has no security policy, so there is no documented channel or process for reporting and handling vulnerabilities. This is a meaningful transparency gap for a network- and socket-facing client.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.