Server-side anti-wallhack for Counter-Strike 2 community servers, built for Metamod:Source.
C-Rank Grade: B (Solid) - 45/100
External PR Merge Rate: 33%
Response Time: 7h
First Timer Success: 100%
karola3vax/CS2FOW has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in karola3vax/CS2FOW respond to incoming external pull requests in approximately 7.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 45.4 places karola3vax/CS2FOW in the B tier.
The external contributor pull request merge rate for karola3vax/CS2FOW is 33.3%, based on public PR activity from non-core contributors.
karola3vax/CS2FOW currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing C++ project in karola3vax/CS2FOW welcoming community pull requests and bug fixes.
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/karola3vax/CS2FOW?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 23:00 UTC (23:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~5 hours (42% approval). Large PRs (>500 lines) take ~34 hours (15% approval). Keep your diff compact for rapid review.
Environment CS2FOW 0.3.3 (linux-x86_64), Metamod:Source Public community server, 64-tick, baked maps in use Summary Players consistently report two related visual artifacts from the CheckTransmit hide/reveal: Frozen "ghost": when an enemy leaves line-of-sight, a frozen copy of them stays at their last-seen position. Aiming at that spot shows the player's name / target-ID floating in the air. Teleport: when that enemy is re-revealed after moving while hidden, they snap/jump from the old frozen position to their real new position. These look like two sides of the same CheckTransmit mechanic. Configs we tried (sv_enable_donttransmit 0 for the first three) cs2fow_visibility_hold_ms Result 1000 (0.3.3 default) Enemy stays revealed ~1s after LOS, then freezes → strong "stays where last seen" ghost + name tag 100 Shorter ghost trail, but frequent teleports (brief LOS breaks now hide → reveal → snap) 500 Compromise — fewer teleports than 100, longer trail; both artifacts
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 karola3vax/CS2FOW, 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 karola3vax/CS2FOW acknowledge new external contributions in approximately 6 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 33.3% were successfully merged into the primary branch.
karola3vax/CS2FOW has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~6 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 45.4 places karola3vax/CS2FOW in the Solid tier.
The external pull request merge rate is 33.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, karola3vax/CS2FOW currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for karola3vax/CS2FOW 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.