MulNX：立志做 CS2 内容创作核心支柱。 底层操控、实时渲染、并发架构、媒体管线、网络、UI——在一套体系内全部打通，完整开源。 Demo分析、精细录制、运镜导播、画面增强、智能控制、脚本扩展——庞大功能集任你取用。 专做他人认为办不到、划不来、做不完的事，只因相信技术普惠。 完全免费，可审计。UGC 版权丝毫不取，为CS2社区添砖加瓦。 仅限合法合规使用。
C-Rank Grade: B (Solid) - 46/100
External PR Merge Rate: 33%
Response Time: 18h
First Timer Success: 100%
Co1Swet/MulNX_CS2 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 Co1Swet/MulNX_CS2 respond to incoming external pull requests in approximately 18.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.0 places Co1Swet/MulNX_CS2 in the B tier.
The external contributor pull request merge rate for Co1Swet/MulNX_CS2 is 33.3%, based on public PR activity from non-core contributors.
Co1Swet/MulNX_CS2 does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Collaborative maintainer environment in Co1Swet/MulNX_CS2. Reviews community pull requests with focus on project quality.
Discussions in Co1Swet/MulNX_CS2 focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/Co1Swet/MulNX_CS2?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~12 hours (42% approval). Large PRs (>500 lines) take ~87 hours (15% approval). Keep your diff compact for rapid review.
No cached good first issues currently tracked for Co1Swet/MulNX_CS2.
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 Co1Swet/MulNX_CS2, 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 Co1Swet/MulNX_CS2 acknowledge new external contributions in approximately 18 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.
Co1Swet/MulNX_CS2 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 ~18 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 46.0 places Co1Swet/MulNX_CS2 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.
Co1Swet/MulNX_CS2 does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for Co1Swet/MulNX_CS2 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.