Tunneling data over webrtc to bypass censorship
C-Rank Grade: A (Welcoming) - 58/100
External PR Merge Rate: 47%
Response Time: 16h
First Timer Success: 25%
kulikov0/whitelist-bypass has a recorded first-timer success rate of 25.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kulikov0/whitelist-bypass respond to incoming external pull requests in approximately 16.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 57.7 places kulikov0/whitelist-bypass in the A tier.
The external contributor pull request merge rate for kulikov0/whitelist-bypass is 46.7%, based on public PR activity from non-core contributors.
kulikov0/whitelist-bypass currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in kulikov0/whitelist-bypass. 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/kulikov0/whitelist-bypass?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 Wednesday - Friday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~10 hours (58% approval). Large PRs (>500 lines) take ~77 hours (21% approval). Keep your diff compact for rapid review.
Creater перестал создавать ссылку для WB. Похоже что то поменяли. tunnel-logs-2026-10-10T09-17-22-355Z.txt
Setup: v0.4.4 linux-x64, headless telemost-creator (Ubuntu 22.04, Paris VPS) ↔ telemost-joiner (Ubuntu 24.04, LXC), flags --dual-track --vp8-batch 60 --vp8-fps 30. One creator, one joiner, fresh conference, no duplicate processes. Problem: SOCKS5 connections reset mid-transfer. Out of 8 sequential 10MB downloads via curl --socks5-hostname, 0 completed (all curl exit 56), aborting after 62KB-3.3MB. Smaller sizes do not help: 500KB completes 2/4, 1MB completes 1/4. Peak speed when it does flow is good - 9.3 Mbit/s. Logs. Joiner: relay: SOCKS 5 read error: read tcp 127.0.0.1:1080->127.0.0.1:53870: read: connection reset by peer (sent 4 times, 747B) relay[joiner]: drop msgType=4 for unknown conn 5 (payload=1126B), NACK once Creator: relay: conn 5 read error: read tcp [...]:45140->[...]:443: use of closed network connection (read 3385 times, 3797727B) relay[creator]: drop MsgClose for unknown conn 5 Tunnel itself reports healthy: TUNNEL CONNECTED, screenshare sub-tunnel live, tracks=2, Te
Сервер: Intel i5-6600k Intel HD 530 Windows 10 LTSC 2021 x86-64 Клиент: Android 13 (Poco F3; HyperOS) Регион, оператор: Свердловская область, на сервере Planeta, на клиенте Yota ВК через DC Joiner даёт WebSocket error, а через Video просто закрывается после десяти секунд Другие тоже не дают подключится, могу скинуть от них логи Логи с ВК (DC, Joiner): 12:32:37.156 Loading: https://vk.ru/call*** 12:32:37.188 Relay started DC mode (SOCKS5 2i5x2b0ie2jsq9pw:[email protected]:1080, WS :9000) 12:32:37.197 dc-joiner: SOCKS5 on 127.0.0.1:1080 12:32:37.198 dc-joiner: WebSocket on 127.0.0.1:9000 12:32:39.329 Page loaded, injecting hook for https://vk.ru/call*** 12:32:39.332 Injecting autofill for https://vk.ru/call*** 12:32:39.342 [HOOK] Hook installed 12:32:39.343 [HOOK] [autoclick] Autoclick installed 12:3
Продолжение #156 Всё ещё не работает, застревает на капче. Один раз смог запуститься, но это было не на долго. Логи: tunnel-logs-2026-07-27T06-38-13-458Z.txt relay.log
Telemost headless Linux: VPS Creator connects TCP but Joiner never receives MsgConnectOK Summary Telemost headless works when both headless-telemost-creator and headless-telemost-joiner run on the same local Linux machine, but fails in a real VPS Creator -> home Linux Joiner setup. In the VPS setup the Creator receives the SOCKS CONNECT request and successfully opens the outbound TCP connection, but the Joiner never receives MsgConnectOK and times out after 20s. This looks like the return VP8/video path from Creator to Joiner is not reliably bound/delivering relay frames when Creator is on a VPS/datacenter IP. Version whitelist-bypass: v0.3.6 binaries: whitelist-bypass-cli-linux-x64.zip Creator: headless-telemost-creator Joiner: headless-telemost-joiner Telemost protocol in logs: sdk 5.29.0 app 197.3.0 Topology Home Linux PC -> headless-telemost-joiner -> local SOCKS5 127.0.0.1:18080 -> Telemost SFU -> headless-telemost-creator on Ubuntu 24.04 VPS -> Internet VPS Creator r
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 kulikov0/whitelist-bypass, 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 kulikov0/whitelist-bypass acknowledge new external contributions in approximately 15 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 46.7% were successfully merged into the primary branch.
kulikov0/whitelist-bypass has a recorded first-timer success rate of 25.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~15 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 57.7 places kulikov0/whitelist-bypass in the Welcoming tier.
The external pull request merge rate is 46.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kulikov0/whitelist-bypass 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 kulikov0/whitelist-bypass 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.