The small project has limited safeguards and no security policy, which adds uncertainty for a production dependency. Its license, documentation, and organization-backed repository are helpful, but they do not offset the long maintenance gap.
42%
Total Score
100
70
50
There has been only one release, published about 6 years and 8 months ago, with no releases in the last 12 months. This is strong evidence of an unmaintained package, though the repository is not archived.
Composer is used as the build tool, but no security scanning tools are reported. For a package handling clustered websocket and Redis infrastructure, this is a modest transparency and maintenance gap.
The repository has no security policy. That leaves vulnerability-reporting and response expectations unclear, which matters for a network-facing websocket component.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
swoft/bean Version ~2.0.0 | — | — |
swoft/redis Version ~2.0.0 | — | — |
swoft/stdlib Version ~2.0.0 | — | — |
devweyes/queue Version ^1.0 | — | — |
swoft/serialize Version ~2.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.