Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)
C-Rank Grade: A (Welcoming) - 56/100
External PR Merge Rate: 54%
Response Time: 1d
First Timer Success: 39%
usebruno/bruno has a recorded first-timer success rate of 39.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in usebruno/bruno respond to incoming external pull requests in approximately 34.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 56.4 places usebruno/bruno in the A tier.
The external contributor pull request merge rate for usebruno/bruno is 53.8%, based on public PR activity from non-core contributors.
usebruno/bruno currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)
Rigorous architecture standards (61% critical review signals). Ensure PRs strictly follow guidelines before requesting review in usebruno/bruno.
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/usebruno/bruno?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~22 hours (67% approval). Large PRs (>500 lines) take ~163 hours (24% approval). Keep your diff compact for rapid review.
REF - BRU-4540 I have checked the following: I have searched existing issues and found nothing related to my issue. This bug is: Making Bruno unusable for me. Slowing me down but I'm able to continue working. Annoying. This feature was working in a previous version but is broken in the current release. Bruno version 4.1.0 💻 Operating System macOS Specific OS Version / Distro No response 🐞 Describe the bug Description When using Bruno on macOS with a German or Swiss-German keyboard layout, typing ⌥ Option + G (the standard shortcut for the @ character) does not input the symbol. Instead, it triggers the built-in Monaco Editor command "Jump to line". Since this shortcut is hardcoded within the embedded editor engine, it completely overrides the macOS system layout behavior, making it impossible to type @ symbols (e.g., in scripts or documentation) without using external workarounds. Expected Behavior The @ character should be inserted into the text field. Actual Behavior
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 usebruno/bruno, 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 usebruno/bruno acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 53.8% were successfully merged into the primary branch.
usebruno/bruno has a recorded first-timer success rate of 39.3%. 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 56.4 places usebruno/bruno in the Welcoming tier.
The external pull request merge rate is 53.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, usebruno/bruno 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 usebruno/bruno 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.