klzgrad/naiveproxy

Make a fortune quietly

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 11 minutes ago
Added to GitGenius on September 7th, 2026
Created on January 27th, 2018
Open Issues & Pull Requests: 9 (+0)
GitHub issues: Enabled
Number of forks: 1,033
Total Stargazers: 9,435 (+0)
Total Subscribers: 129 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 14.6 hours
Mean response time: 4.6 days
90th percentile: 9.3 days
Tracked items: 187

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

How this project is maintained

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

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 1
Closed in 7 days: 4
Avg open age: 264 days
Stale 30+ days: 5
Stale 90+ days: 1

Recent activity

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

Top labels

No label distribution available yet.

Detailed Description

NaïveProxy is a proxy tool that uses Chromium's network stack to camouflage traffic with strong censorship resistance and low detectability.

The tool addresses traffic analysis attacks that censors use to identify and block proxy connections. It mitigates website fingerprinting through HTTP/2 traffic multiplexing and preamble parroting, defeats TLS parameter fingerprinting by reusing Chrome's network stack, resists active probing through application fronting behind standard frontend servers, and reduces length-based traffic analysis through padding and fragmentation. The architecture places a NaïveProxy client between a browser and a censor, connecting to a frontend server that routes based on HTTP authorization headers, which then connects to a NaïveProxy server that acts as a forward proxy with packet length padding.

NaïveProxy suits users who need to circumvent censorship and want traffic that resembles ordinary Chrome browser connections. The frontend server can be any well-known reverse proxy supporting HTTP/2 routing by authorization headers, such as Caddy with its forwardproxy plugin or HAProxy. The project provides a fork of Caddy's forwardproxy that adds NaïveProxy's padding layer. The tool runs on Windows, Linux, macOS, Android, and OpenWrt, with client setup requiring only a configuration file to expose a SOCKS5 proxy locally. Users should maintain the latest version to keep traffic signatures identical to Chrome.

Development activity shows consistent maintenance with automated build workflows. The project accepts third-party integrations, as evidenced by GUI client support. Documentation covers server setup with example configurations, client parameter usage, and performance tuning guidance. The codebase is written in C++ and built from Chromium's network stack components.