eooce/node-ws

基于serverless实现的vless+trojan+shadowsocks+vmess四协议,无内核,node环境通用项目

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 17 minutes ago
Added to GitGenius on September 10th, 2026
Created on September 7th, 2023
Open Issues & Pull Requests: 2 (+0)
GitHub issues: Enabled
Number of forks: 10,262
Total Stargazers: 6,229 (+0)
Total Subscribers: 10 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.9 hours
Mean response time: 47.0 hours
90th percentile: 7.1 days
Tracked items: 11

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

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

node-ws is a serverless proxy implementation that supports multiple protocols in a Node.js environment.

The project implements four proxy protocols—VLESS, Trojan, Shadowsocks, and VMess—designed to run on serverless platforms without requiring a separate kernel. It operates as a general-purpose Node.js application, allowing deployment in serverless environments where traditional proxy solutions may be impractical due to resource constraints or architectural limitations.

This tool suits developers who need multi-protocol proxy functionality within serverless constraints and have Node.js as their runtime environment. It is particularly relevant for those building applications on serverless platforms who require protocol flexibility without the overhead of kernel-dependent solutions. The approach of consolidating four protocols into a single Node.js application reduces deployment complexity compared to managing separate proxy implementations.

The project shows active development with ongoing commits and updates to its codebase. The repository maintains focus on the core serverless proxy functionality with regular refinements to the implementation.