usebruno/bruno - Open Source PR Review Scorecard

Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)

C-Rank Grade: B (Solid) - 46/100

External PR Merge Rate: 55%

Response Time: 3d

First Timer Success: 34%

Frequently Asked Questions

Is usebruno/bruno welcoming to first-time open-source contributors?

usebruno/bruno has a recorded first-timer success rate of 33.9%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in usebruno/bruno respond to incoming external pull requests in approximately 64.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 46.5 C-Rank™ score (B Tier) represent?

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 46.5 places usebruno/bruno in the B tier.

What is the external contributor pull request merge rate for usebruno/bruno?

The external contributor pull request merge rate for usebruno/bruno is 54.7%, based on public PR activity from non-core contributors.

Are there Good First Issues available in usebruno/bruno?

usebruno/bruno currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

usebruno
usebruno/brunoBSolid46.6k
GitHub
Back to Explorer
usebruno

usebruno/bruno

46,642
BSolid(46/100)JavaScript

Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)

Compare
Jump to:
Response Velocity
2 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
54.7%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
33.9%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
83 core
Highly collaborative maintainer core
Diagnostic Health HUD
54.7%
Merge Gauge
33.9%
1st-Timer
Community Vibe32/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for usebruno/bruno
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/usebruno/bruno)](https://getmerged.abhishekco.de/usebruno/bruno?utm_source=github&utm_medium=badge)

Active Good First Issues (1)

View on GitHub

This repository currently has 1 open good first issue tickets available for newcomers.

View all good first issues directly on GitHub

Looking for more JavaScript beginner tasks?Explore JavaScript GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for usebruno/bruno

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 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 54.7% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to usebruno/bruno

01

Is usebruno/bruno welcoming to first-time open-source contributors?

usebruno/bruno has a recorded first-timer success rate of 33.9%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~2 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 46.5 C-Rank™ score represent?

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 46.5 places usebruno/bruno in the Solid tier.

04

What is the external contributor pull request merge rate for usebruno/bruno?

The external pull request merge rate is 54.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in usebruno/bruno?

Yes, usebruno/bruno currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

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.