shadowsocks/shadowsocks-c

Self-contained Shadowsocks implementation in C with libuv, asynchronous DNS, and portable static builds for Linux, macOS, Windows, and FreeBSD.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 15 minutes ago
Added to GitGenius on September 3rd, 2026
Created on December 15th, 2012
Open Issues & Pull Requests: 31 (+0)
GitHub issues: Enabled
Number of forks: 6,223
Total Stargazers: 16,179 (+0)
Total Subscribers: 729 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 1
Closed in 7 days: 1
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 1
Events in 7 days: 3

Top labels

No label distribution available yet.

Most active issues this week

Detailed Description

shadowsocks-libev is a C-based SOCKS proxy implementation that provides encrypted tunneling for network traffic.

The tool solves the problem of routing internet traffic through an encrypted tunnel to circumvent network restrictions or enhance privacy. It works by establishing a proxy connection that encrypts data between a client and server using the shadowsocks protocol, allowing traffic to pass through firewalls or censorship systems that might otherwise block direct connections.

The project is maintained in bug-fix-only mode, meaning it receives patches for critical issues but no new features. Developers should adopt this tool only if they require a lightweight, C-based shadowsocks implementation for existing deployments or systems where the libev event loop is already in use. For new projects or those seeking active feature development, the project's README directs users toward the Rust-based implementation instead, which serves as the primary focus for ongoing work.

The project operates in a maintenance-only capacity with updates limited to addressing bugs rather than expanding functionality. Development activity centers on preserving stability in the existing codebase while steering new initiatives toward the successor implementation.