websockets/ws

Simple to use, blazing fast and thoroughly tested WebSocket client and server for Node.js

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 48 minutes ago
Added to GitGenius on September 2nd, 2026
Created on November 9th, 2011
Open Issues & Pull Requests: 5 (+0)
GitHub issues: Enabled
Number of forks: 2,590
Total Stargazers: 22,802 (+0)
Total Subscribers: 363 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.3 hours
Mean response time: 2.2 days
90th percentile: 29.0 hours
Tracked items: 73

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 9% of issues opened in the past year have been closed. Three people close 69% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 3,266 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

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

Top labels

  • discussion (1)

Most active issues this week

Detailed Description

ws is a WebSocket client and server library for Node.js.

The library addresses the need for real-time bidirectional communication in Node.js applications by implementing the WebSocket protocol as defined in RFC 6455. It provides both client and server implementations that handle the WebSocket handshake, frame parsing, and message delivery. The approach emphasizes simplicity in the API while maintaining performance through efficient underlying implementation.

Developers should choose this library when building Node.js applications that require WebSocket functionality, whether for real-time data streaming, live notifications, or interactive features. It suits projects ranging from small prototypes to production systems where WebSocket support is needed without additional complexity. The library includes support for WebSocket compression, allowing developers to reduce bandwidth usage for message transmission.

The project demonstrates sustained active development with regular maintenance and bug fixes. The codebase receives consistent updates addressing issues and improving stability. Testing is thorough, with comprehensive test coverage ensuring reliability across different use cases and edge cases. The maintainers respond to issues and pull requests, indicating ongoing engagement with the user community.