Reference implementation of the ChordPro standard for musical lead sheets.
C-Rank Grade: B (Solid) - 51/100
External PR Merge Rate: 100%
Response Time: <1h
First Timer Success: -
ChordPro/chordpro 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 ChordPro/chordpro respond to incoming external pull requests in approximately 0.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 51.1 places ChordPro/chordpro in the B tier.
The external contributor pull request merge rate for ChordPro/chordpro is 100.0%, based on public PR activity from non-core contributors.
ChordPro/chordpro currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in ChordPro/chordpro 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/ChordPro/chordpro?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 Monday - Wednesday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~3 hours (45% approval). Keep your diff compact for rapid review.
Steps to reproduce the behavior: Visit https://github.com/ChordPro/chordpro/releases/tag/R6.090.1 Download ChordPro-Installer-6-90-1-2-msw-x64.exe Use Norton 360 to scan the executable before executing it Norton instead quarantined the entire executable, and deleted it. See attached image for specifics. Expected behavior I expect the scan to return no issues. Attachments System information: OS: Windows 11 Home, 22H2 Where did you get ChordPro from? Githib, see above ChordPro version: 6.090.1 Additional Context I decided to ensure that Norton application and virus definition was up to date, so I opened Norton, updated the application, which required a reboot, which I performed. I opened up Norton, verified the virus definition was up to date, and repeated the above steps, and obtained the same outcome. As of this writing, this is the Norton app version and virus definition: I attempted to submit the executable to Norton as a False-Positive(after reading #621 ), but for some reason
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 ChordPro/chordpro, 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 ChordPro/chordpro 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.
ChordPro/chordpro 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 ~<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 51.1 places ChordPro/chordpro in the Solid 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, ChordPro/chordpro 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 ChordPro/chordpro 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.