A free cross-platform game engine focusing on fast prototyping and having fun with Luau scripting
C-Rank Grade: B (Solid) - 43/100
External PR Merge Rate: 50%
Response Time: -
First Timer Success: -
vanyle/vectarine has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in vanyle/vectarine 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 42.8 places vanyle/vectarine in the B tier.
The external contributor pull request merge rate for vanyle/vectarine is 50.0%, based on public PR activity from non-core contributors.
vanyle/vectarine currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Rust project in vanyle/vectarine 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/vanyle/vectarine?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 22:00 UTC (22: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 ~16 hours (62% approval). Large PRs (>500 lines) take ~115 hours (22% approval). Keep your diff compact for rapid review.
Describe the feature Add to the Io module functions to get controller input: Check if there is a controller plugged-in Check what buttons are pressed Get joystick position information We name this API Gamepad to fit the naming used by SDL The difference between a joystick and a gamepad is that a gamepad tells you where a button or axis is on the device. You don't speak to gamepads in terms of arbitrary numbers like "button 3" or "axis 2" but in standard locations: the d-pad, the shoulder buttons, triggers, A/B/X/Y (or X/O/Square/Triangle, if you will). How goes this feature fit into the design principles of Vectarine This fits into the principle: "Empowering makers" because we want to allow game makers to create games that use controllers. Luau API We probably want the following functions in the Io module: -- There might be multiple gamepads plugged into the computer / console function getGamepadCount(): number function getGamepadState(gamepadId: number): { -- We use standard ga
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 vanyle/vectarine, 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 vanyle/vectarine acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 50.0% were successfully merged into the primary branch.
vanyle/vectarine has a recorded first-timer success rate of 0.0%. Repositories ranked Solid 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 42.8 places vanyle/vectarine in the Solid tier.
The external pull request merge rate is 50.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, vanyle/vectarine 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 vanyle/vectarine 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.