MuseScore is an open source and free music notation software. For support, contribution, bug reports, visit MuseScore.org. Fork and make pull requests!
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 80%
Response Time: -
First Timer Success: 55%
musescore/MuseScore has a recorded first-timer success rate of 55.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in musescore/MuseScore 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 66.4 places musescore/MuseScore in the A tier.
The external contributor pull request merge rate for musescore/MuseScore is 79.5%, based on public PR activity from non-core contributors.
musescore/MuseScore currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in musescore/MuseScore. 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/musescore/MuseScore?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (36% approval). Keep your diff compact for rapid review.
Issue type UX/Interaction bug (incorrect behaviour) Description with steps to reproduce Dragging a stave spacer on top of another of a different type replaces the original spacer correctly, but Undo removes any spacers rather than reinstating the original. Supporting files, videos and screenshots Screen.Recording.2026-07-31.at.12.31.25.mov In which versions of MuseScore Studio is this issue present? Latest main Regression No. Operating system macOS 26.5.2 Additional context No response Checklist This report follows the guidelines for reporting bugs and issues I have verified that this issue has not been logged before, by searching the issue tracker for similar issues I have attached all requested files and information to this report I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
Issue type UI bug (incorrect info or interface appearance) Description with steps to reproduce Upon opening the app & selecting a score (previously having set the app to dark mode, as well as having the invert score option ticked), the whole app gets much brighter than expected—a pale purplish/reddish hue. This makes everything harder to read (including the settings) & could be considered to look bad. This issue also affects light mode, although I don't use it enough to know anything specific. The only workaround is to open a new instance of MuseScore & closing that score. This somehow reverts the 1st instance to normal. Repeat for subsequent open windows. Normal hex values for Main UI: #2D2D30 Score Background: #000000 Observed hex values for Main UI: #807F89 Score Background: #1D191A Text color is normal #FFFFFF, Home/Publish pages are normal, & Preferences & other windows are also normal (I have not checked everything, though). Supporting files, videos and screenshots In which ve
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 musescore/MuseScore, 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 musescore/MuseScore acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 79.5% were successfully merged into the primary branch.
musescore/MuseScore has a recorded first-timer success rate of 55.3%. Repositories ranked Welcoming 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 66.4 places musescore/MuseScore in the Welcoming tier.
The external pull request merge rate is 79.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, musescore/MuseScore currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for musescore/MuseScore 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.