GO Simple Tunnel - a simple tunnel written in golang
C-Rank Grade: B (Solid) - 46/100
External PR Merge Rate: 100%
Response Time: 2d
First Timer Success: -
go-gost/gost has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in go-gost/gost respond to incoming external pull requests in approximately 52.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 46.1 places go-gost/gost in the B tier.
The external contributor pull request merge rate for go-gost/gost is 100.0%, based on public PR activity from non-core contributors.
go-gost/gost currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in go-gost/gost. Maintains strict focus on technical quality and test standards.
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/go-gost/gost?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~34 hours (96% approval). Large PRs (>500 lines) take ~250 hours (45% approval). Keep your diff compact for rapid review.
Hello, I need to simulate a NGINX UDP proxy via the NGINX Stream Module. I need it to explicity forward the packets, and not create new "sessions" for each packet as it is interfering with my backend application. How can i make a classic UDP proxy that simply forwards packets. It needs to send and recieve packets as the client sense and receives (as the server sends packets back as well)
Hello. I am trying to make TCP + UDP socks5 proxy working in Gost 3. I started the next command: gost -L :1300?udp=true -F socks5://217.217.217.217:1400 Where socks5://217.217.217.217:1400 is the second Socks5 with UDP support. Then I try to send UDP data via :1301 Socks5 proxy but I get an error: "handler":"auto","kind":"handler","level":"error","listener":"tcp","msg":"route(retry=0) get socks5 UDP tunnel failure" Socks5 via TCP is working correctly and send data via the second Socks5 proxy (217.217.217.217:1400). But UDP is not working correctly. How to make it work with UDP support. I am newbie in Gost. I tried to find this solution in Google and Wiki here. But I couldn't . Thanks.
我现在使用 gost v3.2.5 的版本，当前使用services 配置了监听的端口，chain配置了两个IP地址，一个v4地址，一个v6地址，我想达到的效果是当两个地址任何一地址不通时都能切换到另一个地址。如果两个地址都通可以选择任意一个延迟底的进行访问即可。 现在的问题是当v6不通了，流量还是会发送到v6，能否当v6故障的时候流量就不走v6了，只是检测即可，当v6恢复后在进行根据延迟判断是走v6还是v4呢？ 针对改需求如下的配置，请各位大佬指点： services: # 39810 关联 chain-39810 - name: tcp-39810 addr: ":39810" handler: { type: tcp, chain: chain-39810 } listener: { type: tcp } - name: udp-39810 addr: ":39810" handler: { type: udp, chain: chain-39810 } listener: { type: udp } chains: # 策略 1 (39810) - name: chain-39810 hops: - name: hop-39810 selector: strategy: round maxFai
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 go-gost/gost, 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 go-gost/gost acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
go-gost/gost has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 46.1 places go-gost/gost in the Solid tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, go-gost/gost currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for go-gost/gost 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.