.NET for the NES game console
C-Rank Grade: A (Welcoming) - 72/100
External PR Merge Rate: 100%
Response Time: <1h
First Timer Success: 100%
jonathanpeppers/dotnes has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in jonathanpeppers/dotnes respond to incoming external pull requests in approximately 0.1 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 72.3 places jonathanpeppers/dotnes in the A tier.
The external contributor pull request merge rate for jonathanpeppers/dotnes is 100.0%, based on public PR activity from non-core contributors.
jonathanpeppers/dotnes currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in jonathanpeppers/dotnes 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/jonathanpeppers/dotnes?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 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 17:00 to 21:00 UTC (17:00 - 21:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~1 hours (45% approval). Keep your diff compact for rapid review.
The 0.3.1-beta release added pad_dpad_x() and pad_dpad_y() (#462) which return signed -1/0/+1 deltas, collapsing 4-branch directional code into 2 simple increments. Samples to update snake pong climber metacursor movingsprite game2048 siegegame shoot2 Acceptance criteria 4-way PAD.LEFT/RIGHT/UP/DOWN branches that adjust coordinates replaced with x += pad_dpad_x(0) / y += pad_dpad_y(0) style code where the semantics match. Gameplay behavior unchanged. .verified.bin updated if ROM bytes change. All tests pass.
The 0.3.1-beta release added apu_play_tone() / apu_stop() helpers (#460) for simple sound effects without the full music engine. No sample currently uses them. Samples to update Game samples without a music engine that would benefit from simple SFX: pong (paddle/wall hits) snake (eat / death) siegegame climber Acceptance criteria At least 2-3 game samples gain simple sound effects via apu_play_tone / apu_stop. No regression in samples that already use the full APU/music engine. .verified.bin updated. All tests pass.
The 0.3.1-beta release added oam_spr_2x2 (#446) and meta_spr_2x2 / meta_spr_2x2_flip (#433) helpers for drawing 16x16 sprites from 4 sequential tiles. No sample currently uses them. Samples to update / showcase bigsprites metasprites flicker sprites animation Pick the samples where 16x16 sprite drawing is a natural fit and convert manual 4x oam_spr patterns to oam_spr_2x2 / meta_spr_2x2. Acceptance criteria At least one sample demonstrates each of oam_spr_2x2, meta_spr_2x2, and meta_spr_2x2_flip. Visual output unchanged. .verified.bin updated if ROM bytes change. All tests pass.
The 0.3.1-beta release introduced the OamScope ref struct (#444, #448, #475) so samples can use a using block to manage the OAM index automatically: using (new OamScope()) { oam_spr(...); oam_spr(...); } PR #449 adopted this in several samples. The remaining sprite-drawing samples still manage OAM manually. Samples to update horizmask horizscroll statusbar sprites animation bigsprites (any other sample calling oam_spr / oam_meta_spr outside a using (new OamScope()) block) Acceptance criteria Each listed sample wraps OAM drawing in a using (new OamScope()) block. .verified.bin files updated if ROM bytes change. All tests pass.
The 0.3.1-beta release added rect_overlap and sprite_overlap collision detection helpers (#439). Game samples in the repo still hand-roll bounding-box arithmetic. Samples to update pong snake siegegame shoot2 game2048 climber Acceptance criteria Manual collision math replaced with rect_overlap / sprite_overlap where applicable. Gameplay behavior unchanged. .verified.bin files updated if ROM bytes change. All tests pass.
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 jonathanpeppers/dotnes, 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 jonathanpeppers/dotnes acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
jonathanpeppers/dotnes has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 72.3 places jonathanpeppers/dotnes in the Welcoming tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, jonathanpeppers/dotnes currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for jonathanpeppers/dotnes 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.