Tunnel all your traffic over Websocket or HTTP2 - Bypass firewalls/DPI - Static binary available
C-Rank Grade: B (Solid) - 52/100
External PR Merge Rate: 61%
Response Time: 4d
First Timer Success: 60%
erebe/wstunnel has a recorded first-timer success rate of 60.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in erebe/wstunnel respond to incoming external pull requests in approximately 93.5 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 51.8 places erebe/wstunnel in the B tier.
The external contributor pull request merge rate for erebe/wstunnel is 61.1%, based on public PR activity from non-core contributors.
erebe/wstunnel currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Established Rust ecosystem in erebe/wstunnel. Maintains structured code review standards for external contributors.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/erebe/wstunnel?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~61 hours (76% approval). Large PRs (>500 lines) take ~449 hours (28% approval). Keep your diff compact for rapid review.
Describe the goal Trying to tunnel into wstunnel.exe server --restrict-http-upgrade-path-prefix "/wsproxy" ws://0.0.0.0:5000 with a powershell script as a client, through nginx listening on wss://sitename/wsproxy, config: location /wsproxy { proxy_pass http://127.0.0.1:5000; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } Describe what does not work With proxy_pass http://127.0.0.1:5000; I get ←[2m2026-05-08T10:07:00.552967Z←[0m ←[33m WARN←[0m ←[1mcnx←[0m←[1m{←[0m←[3mpeer←[0m←[2m=←[0m"127.0.0.1:49809"←[1m}←[0m←[2m:←[0m←[1mtunnel←[0m←[1m{←[0m←[3mforwarded_for←[0m←[2m=←[0m"remote IP"←[1m}←[0m←[2m
Describe the goal I've been able to use redirect-gateway and iptables masquerade rules and port 1194 and it's working. However I need to tunnel. Not behind a proxy and it's all tcp openvpn Describe what does not work When wstunnel is running, It connects to vpn yes and even creates tun0 on client but I cannot receive internet or ping 10.8.0.1 Describe your wstunnel setup client wstunnel client -L tcp://127.0.0.1:1194:127.0.0.1:1194 --log-lvl=DEBUG wss://server_hostname.net client openvpn remote is remote 127.0.0.1 1194 server /wstunnel server --tls-certificate fullchain.pem --tls-private-key privkey.pem --restrict-to 127.0.0.1:1194 --log-lvl=DEBUG wss://0.0.0.0:443 Desktop (please complete the following information): OS: server is debian 13, client is arch
Describe the goal My main domain (foo.com) is used for multiple purposes. Thus, I'd like to add a domain (bar.foo.com) to use for wstunnel. My setup is: Foreign <=> Cloudflare <=> NGINX (a.b.c.d) <=> Wstunnel (e.f.g.h) Describe what does not work When testing the websocket locally: curl -i -N -H "Connection: Upgrade" -H "Upgrade: websocket" -H "Sec-WebSocket-Version: 13" -H "Sec-WebSocket-Key: $(echo -n 'randomkey123' | base64)" --http0.9 http://localhost:3932 --output - 2 When attempting to test remotely I get a 502 error, and get the following in error logs: 2026-02-04T00:22:40.607689Z ERROR cnx{peer="a.b.c.d:41390"}: wstunnel::tunnel::server::server: error while accepting TLS connection received corrupt message of type InvalidContentType Describe your wstunnel setup Command line used: /home/app/wstunnel server --restrict-to localhost:51825 wss://0.0.0.0:3932 inside docker container with port passthrough. My nginx config: upstream server_backend { server e.f.g.h:3
Describe the goal Goal is to make wstunnel work behind a reverse proxy. Describe what does not work The wireguard handshake packet is twisted. This worked in the past, but it was long time ago. I added cloudflare recently but I don't think it changes the content of packets. Probably something changed in new versions. The setup works until the wireguard packets are "decapsulated" from the wstunnel packet. The standard wireguard handshake initial packet have patterns, I'll list down what it should be and what I see. I will include 2 packets that are sent for handshake initiation. The 2nd packet is sent about 2s after the 1st packet. bytes wireguard pattern packet 1 packet 2 first 4 bytes 01 00 00 00 a5 e6 db 7f 7d 51 dd c1 last 4 bytes mac2 00 00 00 00 a4 e6 db 7f 7c 51 dd c1 The payload length is correct, all payloads are 148 bytes long, as the length of handshake initiation payload. But the contents are obviously twisted. This looks like encryption but I don't know where th
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to erebe/wstunnel, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of erebe/wstunnel acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 61.1% were successfully merged into the primary branch.
erebe/wstunnel has a recorded first-timer success rate of 60.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 51.8 places erebe/wstunnel in the Solid tier.
The external pull request merge rate is 61.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, erebe/wstunnel currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for erebe/wstunnel are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.