A plugin to integrate rand for ECS optimised RNG for the Bevy game engine.
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
Bluefinger/bevy_rand has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Bluefinger/bevy_rand respond to incoming external pull requests in approximately 0.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 8.0 places Bluefinger/bevy_rand in the D tier.
The external contributor pull request merge rate for Bluefinger/bevy_rand is 0.0%, based on public PR activity from non-core contributors.
Bluefinger/bevy_rand currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
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/Bluefinger/bevy_rand?utm_source=github&utm_medium=badge)
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Creating this issue as a reminder for myself, or for whoever wants to have a go at doing this themselves. Basically, I should look at the viability of bsn to interact with the spawning of RNG seeds and relations, and whether that needs any work on my end, or just to update documentation.
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 Bluefinger/bevy_rand, 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 Bluefinger/bevy_rand acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
Bluefinger/bevy_rand has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 8.0 places Bluefinger/bevy_rand in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Bluefinger/bevy_rand 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 Bluefinger/bevy_rand 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.