Desktop app for managing BibTeX and BibLaTeX (.bib) libraries
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 72%
Response Time: 1d
First Timer Success: 46%
JabRef/jabref has a recorded first-timer success rate of 45.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in JabRef/jabref respond to incoming external pull requests in approximately 33.5 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 59.2 places JabRef/jabref in the A tier.
The external contributor pull request merge rate for JabRef/jabref is 72.2%, based on public PR activity from non-core contributors.
JabRef/jabref currently has 22 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in JabRef/jabref. 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/JabRef/jabref?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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~22 hours (90% approval). Large PRs (>500 lines) take ~161 hours (33% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Java.
26.2 Lightweight Minecraft server
MCreator is an open-source software used to make Minecraft Java Edition mods, Minecraft Bedrock Edition Add-Ons, resource packs, and data packs using an intuitive easy-to-learn interface or with an integrated code editor. It is used worldwide by Minecraft players, aspiring mod developers, for education, online classes, and STEM workshops.
Native Telegram client for Android based on TDLib
When a linked file is broken, performing OCR can't be run, but it's still shown in the menu We need it to be faded like the other options.
JabRef version Latest development branch build (please note build date below) Operating system macOS Details on version and operating system JabRef 100.0.0 Mac OS X 26.5.2 aarch64 Java 25.0.3 JavaFX 26.0.2+3 Checked with the latest development build (copy version output from About dialog) I made a backup of my libraries before testing the latest development version. I have tested the latest development version and the problem persists Steps to reproduce the behaviour Open Preferences > Keyboard shortcuts Type some characters in the Search box Notice that text in the search box is the same color as the background, and isn't visible unless the text is selected. Appendix ... Log File Not applicable
Folow-up to #16569 The button should be in the same line as the other buttons
Follow-up to #16569 Highlighting of diff Follow-up: Offer diff-type selection similar as merge dialog
Open example library Save Set up Git from File -> Git Make some changes in the library but don't save (or make no changes at all) Go to git -> commit and put a commit message, and commit Notice that no warning is shown even though there were no changes and thus no commit pushed - giving the user a false impression that a commit was pushed (or more dangerously, they may think their library was indeed saved after the change which it was not). Show the message "Working tree clean, nothing to commit" to the user in that case.
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 JabRef/jabref, 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 JabRef/jabref acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 72.2% were successfully merged into the primary branch.
JabRef/jabref has a recorded first-timer success rate of 45.8%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 59.2 places JabRef/jabref in the Welcoming tier.
The external pull request merge rate is 72.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, JabRef/jabref currently has 22 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for JabRef/jabref 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.