Client for IBM Quantum Compute (formerly known as Qiskit Runtime)
C-Rank Grade: S (Elite) - 70/100
External PR Merge Rate: 83%
Response Time: 1d
First Timer Success: 73%
Qiskit/qiskit-ibm-runtime has a recorded first-timer success rate of 73.3%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Qiskit/qiskit-ibm-runtime respond to incoming external pull requests in approximately 31.9 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 70.1 places Qiskit/qiskit-ibm-runtime in the S tier.
The external contributor pull request merge rate for Qiskit/qiskit-ibm-runtime is 83.2%, based on public PR activity from non-core contributors.
Qiskit/qiskit-ibm-runtime currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in Qiskit/qiskit-ibm-runtime. 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/Qiskit/qiskit-ibm-runtime?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 Wednesday - Friday from 17:00 to 21:00 UTC (17:00 - 21:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~21 hours (96% approval). Large PRs (>500 lines) take ~153 hours (37% approval). Keep your diff compact for rapid review.
What is the expected enhancement? Related to #2607. We are using pproxy for our proxying needs. In #2607, an approach using mitmproxy was attempted, as pproxy is not compatible with 3.14 and seems to be not maintained anymore. This issue is about using mitmproxy instead, which is compatible with Python 3.14 and seems to provide some features to use it programmatically (so we don't need to invoke it as a separate process and use it as a black box, providing better control over it). There might be other alternatives as well, ideally should be explored when tackling this issue. Acceptance criteria pproxy is replaced with an equivalent maintained package that works under 3.14, and ideally it is invoked as a Python library as opposed to as a new process.
What is the expected feature or enhancement? Particular jobs are submitted with a calibration id (or it is absent to use the default one). The requested enhancement is to provide a public interface for fetching the calibration id of a particular job instance. This information is available via private methods as follows: job._api_client.job_get(job_id=job.job_id(), exclude_params=True).get("calibration_id", None) Acceptance criteria There is a method or attribute of the job object to fetch the calibration id that it was submitted with.
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 Qiskit/qiskit-ibm-runtime, 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 Qiskit/qiskit-ibm-runtime acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.2% were successfully merged into the primary branch.
Qiskit/qiskit-ibm-runtime has a recorded first-timer success rate of 73.3%. Repositories ranked Elite 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 70.1 places Qiskit/qiskit-ibm-runtime in the Elite tier.
The external pull request merge rate is 83.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Qiskit/qiskit-ibm-runtime 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 Qiskit/qiskit-ibm-runtime 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.