WebSocket protocol handler with pluggable I/O
65%
Total Score
67
92
50
Only one registry account has publish access, leaving publishing capacity dependent on a single person; organization backing provides some compensation but does not remove the concentration risk.
The repository recorded zero commits and zero active maintainers in the past three months, which weakens evidence of ongoing maintenance despite the recent package release and push.
The repository reports no build tooling or security scanning. This is a hygiene gap, though the project still has tests and a straightforward small source tree.
All two action references are unpinned, and the high-confidence audit found an adhoc package installation outside a lockfile. The audit is complete and found no untrusted checkout or script-injection path, limiting the impact.
| Title | Versions | Severity |
|---|---|---|
CVE-2026-54490 websocket-driver is vulnerable to Allocation of Resources Without Limits or Throttling in versions 0.0.0 - 0.7.5. | 0.0.0 - 0.7.5 | Medium |
CVE-2026-54466 websocket-driver is vulnerable to Improper Handling of Length Parameter Inconsistency in versions 0.0.0 - 0.7.5. | 0.0.0 - 0.7.5 | Critical |
| Dependency | Last Release | Score |
|---|---|---|
safe-buffer Version >=5.1.0 | — | — |
http-parser-js Version >=0.5.1 | — | — |
websocket-extensions Version >=0.1.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.