Open-source software for volunteer computing and grid computing.
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 76%
Response Time: -
First Timer Success: 63%
BOINC/boinc has a recorded first-timer success rate of 62.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in BOINC/boinc 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.3 places BOINC/boinc in the A tier.
The external contributor pull request merge rate for BOINC/boinc is 76.3%, based on public PR activity from non-core contributors.
BOINC/boinc currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in BOINC/boinc. 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/BOINC/boinc?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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (95% approval). Large PRs (>500 lines) take ~115 hours (34% approval). Keep your diff compact for rapid review.
Describe the problem Build scripts need to be migrated to use core26 instead of core24. Important: core26 is not shipped with the Python environment, so it need to be updated correspondingly since Python is used during vcpkg build. Describe the solution you'd like No response Additional context No response
Describe the problem Currently we are building samples/nvcuda on Linux for x64 platform only. It would be nice to have a possibility to make a crosscompilation on Linux x64 for Linux arm64. Ref: https://developer.nvidia.com/cuda-downloads?target_os=Linux https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html Describe the solution you'd like No response Additional context No response
Describe the bug The “Disk” page's pie chart renders atop other elements, such that they are rendered unreadable. Steps to reproduce #!/usr/bin/env sh lookandfeeltool -a org.kde.breeze.desktop && \ run0 dnf5 install --refresh -y boinc-manager && \ boincmgr Select "Disk". Expected behavior The chart should not render atop any other elements. Screenshots System information OS Details #!/usr/bin/env sh cat /etc/os-release | jc --ini | jq 'with_entries(.value |= (if type=="string" and test("^[0-9]+$") then tonumber else . end))| {NAME, VARIANT, VERSION_ID}' | yq -P NAME: Fedora Linux VARIANT: KDE Plasma Desktop Edition VERSION_ID: 43 Boinc Details #!/usr/bin/env sh rpm -qf $(command -v boincmgr) \ --queryformat "$( cat <<'EOF' Name: %{NAME} Version: %{VERSION} Release: %{RELEASE} Architecture: %{ARCH} Install Date: %{INSTALLTIME:date} Size: %{SIZE} Signature: %{SIGPGP:pgpsig} Source RPM: %{SOURCERPM} Build Date: %{BUILDTIME:date} Build Host: %{BUILDHOST} Packag
Describe the problem Somewhere there is an issue in the Windows code (soething with double buffering I believe) that makes the BOINC Manager window in Advanced View to be blurred when freshly opened. This blur is gone when the window is resized the first time, and never happens again. Describe the solution you'd like No response Additional context No response
Describe the problem With the latest release of Kotlin, this is now should be possible. Describe the solution you'd like No response Additional context No response
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 BOINC/boinc, 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 BOINC/boinc acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 76.3% were successfully merged into the primary branch.
BOINC/boinc has a recorded first-timer success rate of 62.5%. 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.3 places BOINC/boinc in the Welcoming tier.
The external pull request merge rate is 76.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, BOINC/boinc currently has 6 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for BOINC/boinc 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.