The next-generation game engine that you deserve implemented in rust https://pulsarnative.com/ Developer_Blogs: https://pulsarnative.com/blog/ Research: https://pulsarnative.com/Research/ UI-Framework: https://pulsarnative.com/UI/
C-Rank Grade: S (Elite) - 74/100
External PR Merge Rate: 85%
Response Time: 21h
First Timer Success: 60%
Far-Beyond-Pulsar/Pulsar-Native has a recorded first-timer success rate of 60.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Far-Beyond-Pulsar/Pulsar-Native respond to incoming external pull requests in approximately 21.2 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 74.4 places Far-Beyond-Pulsar/Pulsar-Native in the S tier.
The external contributor pull request merge rate for Far-Beyond-Pulsar/Pulsar-Native is 85.4%, based on public PR activity from non-core contributors.
Far-Beyond-Pulsar/Pulsar-Native currently has 9 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
The next-generation game engine that you deserve implemented in rust https://pulsarnative.com/ Developer_Blogs: https://pulsarnative.com/blog/ Research: https://pulsarnative.com/Research/ UI-Framework: https://pulsarnative.com/UI/
Highly welcoming maintainers in Far-Beyond-Pulsar/Pulsar-Native. Prompt code reviews with positive guidance for new contributors.
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/Far-Beyond-Pulsar/Pulsar-Native?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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~14 hours (96% approval). Large PRs (>500 lines) take ~102 hours (38% approval). Keep your diff compact for rapid review.
thread 'Helio Render' (29276) panicked at C:\Users\redst\.cargo\registry\src\index.crates.io-1949cf8c6b5b557f\wgpu-30.0.1\src\backend\wgpu_core.rs:1965:22: wgpu error: Validation Error Caused by: In Queue::write_buffer Buffer with 'HiZ Mip Uniform' label is invalid note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [HELIO RENDER THREAD PANIC] Helio render thread panicked: wgpu error: Validation Error Caused by: In Queue::write_buffer Buffer with 'HiZ Mip Uniform' label is invalid Backtrace: 0: std::backtrace_rs::backtrace::win64::trace at /rustc/48a229ceaefd4985c50990b14116b6d856af0985/library\std\src\..\..\backtrace\src\backtrace\win64.rs:85 1: std::backtrace_rs::backtrace::trace_unsynchronized at /rustc/48a229ceaefd4985c50990b14116b6d856af0985/library\std\src\..\..\backtrace\src\backtrace\mod.rs:66 2: std::backtrace::Backtrace::create at /rustc/48a229ceaefd4985c50990b14116b6d856af0985/library
wgpui: several window tests fail intermittently when the suite runs in parallel. cargo test --lib in crates/ui/wgpui with default threads intermittently fails a different scroll/texture test each run (seen: a_texture_retained_layer_composites_from_a_surface, a_plain_scrolled_div_shifts_without_rerecording_then_refills, an_overscroll_buffer_shifts_without_rerecording_then_refills). With -- --test-threads=1 the whole suite passes (337 passed, 1 ignored), so this looks like shared process-global state (layer/env toggles) between tests. Not confirmed against a baseline build or root-caused.
Vs expected position: As of this time this is clearly a bug in the UI framework but I am unsure if it is particularly widespread it doesn't seem to be appearing anywhere else which is strange
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 Far-Beyond-Pulsar/Pulsar-Native, 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 Far-Beyond-Pulsar/Pulsar-Native acknowledge new external contributions in approximately 21 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 85.4% were successfully merged into the primary branch.
Far-Beyond-Pulsar/Pulsar-Native has a recorded first-timer success rate of 60.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~21 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 74.4 places Far-Beyond-Pulsar/Pulsar-Native in the Elite tier.
The external pull request merge rate is 85.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Far-Beyond-Pulsar/Pulsar-Native currently has 9 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for Far-Beyond-Pulsar/Pulsar-Native 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.