The README is extremely brief, and the repository has no security policy or security scanning. Its dependency set is modest and installation has no lifecycle scripts, but the project shows little evidence of ongoing care.
42%
Total Score
100
58
75
Only two releases were published, both in May 2018, with no releases in the last 12 months. This is strong evidence that maintenance has stopped for a package intended as a reusable client.
The package includes a README, but it is only 51 characters and provides little integration guidance. Missing tests and changelog files are normal for published artifacts and are not treated as gaps here.
Composer is used for builds, which is appropriate, but no security-scanning tooling is present. This is a hygiene gap that adds to the project's limited maintenance evidence.
The repository is not archived, but it was last pushed in May 2018, matching the long release gap and indicating that the unarchived status does not show active maintenance.
The linked repository has no security policy. For a network client, this reduces transparency around vulnerability reporting and response.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^1.0 | — | — |
lanzhi/php-coroutine-socket Version >=0.1 | — | — |
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.