C-Rank Grade: S (Elite) - 72/100
External PR Merge Rate: 84%
Response Time: 2d
First Timer Success: 83%
bisq-network/bisq2 has a recorded first-timer success rate of 83.3%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in bisq-network/bisq2 respond to incoming external pull requests in approximately 48.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 72.2 places bisq-network/bisq2 in the S tier.
The external contributor pull request merge rate for bisq-network/bisq2 is 83.9%, based on public PR activity from non-core contributors.
bisq-network/bisq2 currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in bisq-network/bisq2. Reviews community pull requests with focus on project quality.
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/bisq-network/bisq2?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 04:00 UTC (04:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~32 hours (96% approval). Large PRs (>500 lines) take ~233 hours (38% approval). Keep your diff compact for rapid review.
It seems the version.txt is not written if the app is not installed via the in-app downloader.
On a VPS server I got those results with locale: LANG=C.UTF-8 LANGUAGE= LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=en_US.UTF-8 -> LANG=C.UTF-8 ← generic “C” locale (no country) It caused a NPE in the code. I could temp fix it by adding -Duser.language=en -Duser.country=US to the jvm args. We should already handle the cases where no OS locale is provided, but seems there is some check missing.
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 bisq-network/bisq2, 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 bisq-network/bisq2 acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.9% were successfully merged into the primary branch.
bisq-network/bisq2 has a recorded first-timer success rate of 83.3%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 72.2 places bisq-network/bisq2 in the Elite tier.
The external pull request merge rate is 83.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, bisq-network/bisq2 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 bisq-network/bisq2 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.