norns is many sound instruments.
C-Rank Grade: A (Welcoming) - 58/100
External PR Merge Rate: 36%
Response Time: 13h
First Timer Success: 50%
monome/norns has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in monome/norns respond to incoming external pull requests in approximately 12.6 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 57.7 places monome/norns in the A tier.
The external contributor pull request merge rate for monome/norns is 35.7%, based on public PR activity from non-core contributors.
monome/norns currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly encouraging & supportive maintainers (75% positive review sentiment). Active code reviews with constructive guidance for new contributors in monome/norns.
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/monome/norns?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 19:00 UTC (19:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~8 hours (45% approval). Large PRs (>500 lines) take ~61 hours (16% approval). Keep your diff compact for rapid review.
buffer_read_stereo and related methods do not attempt to take the source sample rate into account. however, the function arguments are given in seconds, somewhat implying that resampling will occur. the non-resampling behavior should be spelled out in the API reference at least. even better would be to just add resampling on file import, which is not difficult. options and considerations: link libsamplerate and use that API. (i am sure the runtime library is included on the norns image already, but not sure about the -dev package.) roll a simple resampler using linear or cubic interpolation. (main reason to consider linear, IMHO (besides simplicity,) is that polynomial interpolation can cause small amplitude overshoots, which is a problem when importing 0db-normalized samples. so kind of necessitaties an optional downward-normalization step.)
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 monome/norns, 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 monome/norns acknowledge new external contributions in approximately 12 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 35.7% were successfully merged into the primary branch.
monome/norns has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~12 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 57.7 places monome/norns in the Welcoming tier.
The external pull request merge rate is 35.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, monome/norns 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 monome/norns 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.