windtf/wireproxy

Wireguard client that exposes itself as a socks5 proxy

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 12 minutes ago
Added to GitGenius on September 11th, 2026
Created on March 11th, 2022
Open Issues & Pull Requests: 79 (+0)
GitHub issues: Enabled
Number of forks: 405
Total Stargazers: 5,795 (+0)
Total Subscribers: 34 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 14.2 days
Mean response time: 93.6 days
90th percentile: 293.4 days
Tracked items: 43

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 5% of issues opened in the past year have been closed. Three people close 63% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 50
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 506 days
Stale 30+ days: 48
Stale 90+ days: 42

Recent activity

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

Top labels

  • enhancement (4)

Most active issues this week

Detailed Description

Wireproxy is a userspace Wireguard client that exposes itself as a SOCKS5 or HTTP proxy.

The tool solves the problem of routing traffic through a Wireguard connection without requiring root permissions or creating a new network interface. It runs entirely in userspace, connecting to a Wireguard peer and exposing a proxy that applications can use selectively. This approach lets users route specific traffic through a remote Wireguard server while keeping the rest of their network configuration unchanged. The proxy supports TCP static routing, SOCKS5 and HTTP CONNECT tunneling, and transparent TLS proxying via SNI inspection. A health monitoring endpoint can expose Wireguard daemon metrics and check connectivity to specified addresses via ping.

Wireproxy suits developers and users who want selective traffic routing through Wireguard without system-level configuration. It works well for scenarios like routing browser traffic to specific sites through a remote peer, or any situation where you need Wireguard connectivity without elevated privileges. The tool is particularly useful on systems where creating new network interfaces is impractical or where you want isolation between your normal network and proxied traffic. It requires no special setup beyond a Wireguard configuration file and can be run as an unprivileged user.

The project has attracted a substantial base of real-world users who report issues from production use. However, responses to issues and pull requests often take weeks or longer, indicating limited maintainer availability. Enhancement requests dominate the issue tracker, suggesting users are actively requesting new capabilities rather than reporting critical bugs.