Search results

CRITICAL SECURITY ALERT: @fairwords/websocket v1.0.38 and v1.0.39 contain sophisticated self-propagating malware

Status: Open.

#502 In theturtle32/WebSocket-Node;

· ashishkurmi opened on Apr 22, 2026

Websocket Client: Consider adding headers for caches

Status: Open.

#474 In theturtle32/WebSocket-Node;

· svnhub opened on Sep 11, 2025

EPIPE which cannot be caught by try/catch and terminates the process

Status: Open.

#462 In theturtle32/WebSocket-Node;

· hills opened on Jun 5, 2025

Unhandled error event on request reject

Status: Open.

#458 In theturtle32/WebSocket-Node;

· pieterD7 opened on Apr 24, 2025

websocket doesn't work under bun

Status: Open.

#454 In theturtle32/WebSocket-Node;

· glorand-harmonicinc opened on Mar 7, 2024

Update UTF-8 Validation Code

Status: Open.

#452 In theturtle32/WebSocket-Node;

· theturtle32 opened on Jan 20, 2024

Unable to connect with auth info in url and special characters

bug

Status: Open.

#448 In theturtle32/WebSocket-Node;

· chriscoindeskindices opened on Apr 23, 2023

install of websocket and immediatly disapear

Status: Open.

#441 In theturtle32/WebSocket-Node;

· pedefe opened on Nov 16, 2022

Ssl using cloudflare

Status: Open.

#437 In theturtle32/WebSocket-Node;

· OlympicAngel opened on Oct 2, 2022

Error: connect EINVAL 117.71.xx.xx:443 - Local (undefined:undefined)

Status: Open.

#423 In theturtle32/WebSocket-Node;

· wangyibai opened on Nov 10, 2021

Custom ReasonCode not passed in closeEvent

Status: Open.

#420 In theturtle32/WebSocket-Node;

· hazaart opened on Jul 5, 2021

Modernize

Status: Open.

#418 In theturtle32/WebSocket-Node;

· jimmywarting opened on Jun 10, 2021