theturtle32/websocket-node

A WebSocket Implementation for Node.JS (Draft -08 through the final RFC 6455)

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 53 minutes ago
Added to GitGenius on September 18th, 2026
Created on April 9th, 2011
Open Issues & Pull Requests: 74 (+0)
GitHub issues: Enabled
Number of forks: 596
Total Stargazers: 3,781 (+0)
Total Subscribers: 134 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.0 hours
Mean response time: 912.5 days
90th percentile: 1825.1 days
Tracked items: 2

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 375 days
Stale 30+ days: 4
Stale 90+ days: 4

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

websocket-node is a WebSocket implementation for Node.js that supports protocol versions 8 and 13, written primarily in JavaScript.

The tool solves the problem of establishing bidirectional communication channels between Node.js servers and clients over WebSocket connections. It implements the WebSocket protocol as specified in RFC 6455 and earlier draft versions, providing both server and client functionality through a mostly pure JavaScript approach. The implementation includes support for protocol negotiation and handles the handshake and frame parsing required by the WebSocket specification.

Developers should choose this tool if they need WebSocket support in Node.js environments and prefer a pure JavaScript implementation. It suits projects requiring both client and server WebSocket capabilities, with browser compatibility extending across Firefox, Chrome, Internet Explorer, and Safari. The README does not make explicit comparisons to alternative WebSocket libraries, so no comparative guidance can be offered.

The project maintains a stable codebase with infrequent but deliberate updates focused on compatibility improvements rather than frequent feature additions. Development activity centers on addressing specific interoperability issues and updating browser compatibility shims as JavaScript standards evolve. The maintainers validate implementation correctness through the Autobahn test suite, which provides comprehensive spec compliance verification.