Desktop app for managing BibTeX and BibLaTeX (.bib) libraries
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 67%
Response Time: -
First Timer Success: 49%
JabRef/jabref has a recorded first-timer success rate of 49.0%. 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 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.6 places JabRef/jabref in the A tier.
The external contributor pull request merge rate for JabRef/jabref is 67.0%, based on public PR activity from non-core contributors.
JabRef/jabref currently has 14 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 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (84% approval). Large PRs (>500 lines) take ~115 hours (30% approval). Keep your diff compact for rapid review.
See also #17355 I have @Article{Agrawal2015, author = {Agrawal, Shikha and Agrawal, Jitendra}, date = {2015}, journaltitle = {Procedia Computer Science}, title = {Survey on Anomaly Detection using Data Mining Techniques}, doi = {10.1016/j.procs.2015.08.220}, issn = {1877-0509}, pages = {708-713}, volume = {60}, journal = {Procedia Computer Science}, publisher = {Elsevier BV}, } I press Ctrl+A and then Ctrl+C Then I go into LibreOffice I press Ctrl+V Expectection: highlighted code but I get
JabRef version Latest development branch build (please note build date below) Operating system GNU / Linux Details on version and operating system JabRef 6.0-beta.56--2026-09-26--eb78c4b Linux 7.2.8-200.nobara.fc44.x86_64 amd64 Java 25.0.4.1 JavaFX 27+30 Checked with the latest development build 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 Switch to dark mode via File > Preferences > General > Color Scheme Choose Theme: Primer Add an entry Open the entry editor and scroll down to the "Files and links" section. Click on the header to make the "file" field content visible. Add at least three files to the entry (How to link them) Unlink two of the three files (JabRef should still find them automatically in the chosen file directory) See that the background colour is dark and the text colour is also dark (Not good!) Select the files one by one. See
Open Welcome Tab Click on "New example library" Double click "Tan_2021" Select tab "Citations" Click on BibTeX source for "Effect of ..." See Click "OK" Double click "Effect of ..." entry. Go to tab "biblatex source" See syntax highlight (introduced at #16328) Expected: At step 6, also the syntax highlighting is in place Task: Add the syntax highlighting also to the popup at step 6. Rename window title from "Show BibTeX source" to "BibTeX source". (If possible) Add button "Cancel", which cancels the edits. (This refs #12706, but I could not came up with nice button labels. "Accept edits" and "Cancel edits"? But IDK if we already have these translations)
JabRef version Latest development branch build (please note build date below) Operating system Windows Details on version and operating system No response 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 Welcome Tab Click on "New example library" Double click "Tokede_2011" Double click "Hooper_2012" Double click "Richard_2017" Right lick on "Hooper_2012". Select "Delete entry". Confirm Click on Back Expected: Richard_2017 selected Actual behavior: WARN: Tried to access out of bounds index -1 in entriesViewModel Click on Back Now, Richard_2017 is selected Appendix No response
On the Welcome tab, click "New example library" (opens Chocolate.bib) In the search bar, enter cocoa Click the "Search across libraries in a new window" button (right of the search field) In the dialog "Search results from open libraries", select the entry "Cocoa and Cardiovascular Health" Press Ctrl+C Paste into a text editor Expected at step 6: The selected entry is pasted, same as when copying from the main table Current behavior at step 6: nothing (or old clipboard content) is pasted. Hints: Dialog: GlobalSearchResultDialog.java Reuse the copy handling of the main table (MainTable) instead of reimplementing it Keyboard shortcuts documentation Ctrl+C in the dialog has to respect the "copy" key binding from preferences (i.e., go through KeyBindingRepository)
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 -. Out of all submitted pull requests from non-core authors in the last 180-day window, 67.0% were successfully merged into the primary branch.
JabRef/jabref has a recorded first-timer success rate of 49.0%. 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.6 places JabRef/jabref in the Welcoming tier.
The external pull request merge rate is 67.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, JabRef/jabref currently has 14 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.