A general purpose HTTP reverse proxy and forwarding tool. Now written in Go!
C-Rank Grade: A (Welcoming) - 56/100
External PR Merge Rate: 68%
Response Time: 11h
First Timer Success: 60%
tobychui/zoraxy has a recorded first-timer success rate of 60.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in tobychui/zoraxy respond to incoming external pull requests in approximately 11.0 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 56.2 places tobychui/zoraxy in the A tier.
The external contributor pull request merge rate for tobychui/zoraxy is 68.0%, based on public PR activity from non-core contributors.
tobychui/zoraxy currently has 10 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
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/tobychui/zoraxy?utm_source=github&utm_medium=badge)
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
What happened? Hello ! I am trying to setup a header authentication mechanism for my music service Navidrome coupled with Pocket ID. The OIDC login works but the userid is not properly catched afterwards. Describe what have you tried Here is what I have as config : Security --> SSO/OAUTH2 : I have setup the client id & secret, as well as the .well-known URL (https://pocket.mydomain.be/.well-known/openid-configuration) On the navidrome host definition --> Security : Authentication Provider --> OAUTH2 Headers --> custom headers : Zoraxy >> origin with key X-Auth-User & value... well that's the issue. If I put plainly franky which is a defined user in navidrome, it works. But ! If I put something like username, $username, {username}, ${username}, ... it will login to navidrome and create a userid with username, $username, {username} or ${username}, but not with franky. So I believe something is missing here, I can't figure out how to give the proper OIDC response from pocket into a dyna
What happened? Navigating to 10.10.100.223:9091 loads the transmission web UI just fine. However, attempting to access the service through Zoraxy consistently fails with an error 521. This is after fixing the firewall rules that caused my problems last time. Describe what have you tried I have tried basically every option Zoraxy has. Describe the networking setup you are using Here are some example, commonly asked questions from our maintainers: Non-Docker Zoraxy V3.3.2 No CloudFlare 10.10.120.2 for the proxy server and 10.10.100.0/24 for everything else. Firewall rules allow direct connections from the proxy. I have a record transmission.internal that points to 10.10.100.223. So Zoraxy sees transmission.internal:9091 as its upstream. Additional context When loading the page directly, there are a number of fairly immediate redirects to /transmission/rpc and /transmission/web. These may be interfering. I'd like to know where I can activate more verbose logging on the Zoraxy side that
What happened? I have added a custom 521 error page in the root dir of the server [www], named 521.html, but the error page is not being displayed/applied. Any help or correct procedure will be appreciated.
What happened? I am running a domain that hosts multiple web applications under different subdomains. Some of these applications are published internally only, while others are published both internally and externally. For external publishing, I am using Cloudflare together with a cloudflared Tunnel in proxy mode. The cloudflared tunnel connects back into my local network via the loopback interface, where it forwards all traffic to Zoraxy using a wildcard redirect. As an additional security layer for externally exposed subdomains, I am using oauth2-proxy with Microsoft Entra ID (Azure AD) as the identity provider. To differentiate between internal and external access, I am using a hairpin DNS approach: Internal clients resolve the subdomains to the internal network interface of Zoraxy and access the applications directly without Cloudflare. External clients resolve the same subdomains via public DNS, go through Cloudflare, enter via the cloudflared tunnel, and then reach Zoraxy over th
What happened? I am attempting to configure NetBird but getting 400/404s on some of the virtual directory endpoints Describe what have you tried Using h2c:// for gRPC endpoints, port numbers, trailing slashes Describe the networking setup you are using Here are some example, commonly asked questions from our maintainers: Docker compose: services: zoraxy-docker: image: zoraxydocker/zoraxy:latest container_name: zoraxy ports: - 80:80 - 443:443 networks: [main] volumes: - ./config:/opt/zoraxy/config/ environment: ARGS: '-noauth=false' networks: main: external: true Zoraxy version: 3.3.1 Cloudflare: no No NAT DNS: *.domain.tld and domain.tld point to public IP of server. Additional context I found a GitHub issue where someone had a working config, but I wasn't able to replicate it. NetBird shouldn't need any extra certificates like the person in the issue described. The issue is also a bit old, so Zoraxy / NetBird might have chan
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 tobychui/zoraxy, 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 tobychui/zoraxy acknowledge new external contributions in approximately 11 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 68.0% were successfully merged into the primary branch.
tobychui/zoraxy has a recorded first-timer success rate of 60.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~11 hours. 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 56.2 places tobychui/zoraxy in the Welcoming tier.
The external pull request merge rate is 68.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, tobychui/zoraxy currently has 10 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for tobychui/zoraxy 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.