Home of the Renovate CLI: Cross-platform Dependency Automation by Mend.io
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 62%
Response Time: 2d
First Timer Success: 46%
renovatebot/renovate has a recorded first-timer success rate of 45.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in renovatebot/renovate respond to incoming external pull requests in approximately 42.2 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 64.0 places renovatebot/renovate in the A tier.
The external contributor pull request merge rate for renovatebot/renovate is 62.3%, based on public PR activity from non-core contributors.
renovatebot/renovate currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Home of the Renovate CLI: Cross-platform Dependency Automation by Mend.io
Balanced & professional review environment in renovatebot/renovate. Maintains strict focus on technical quality and test standards.
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/renovatebot/renovate?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 10:00 UTC (10: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 ~27 hours (78% approval). Large PRs (>500 lines) take ~203 hours (28% approval). Keep your diff compact for rapid review.
In the Gitlab platform we are using merge_status do determine the status of a merge request. Tough this field has been deprecated since 15.6 ( support ended on the 22th of February 2023). https://docs.gitlab.com/api/merge_requests/#retrieve-a-merge-request Instead we should use detailed_merge_status which is a defined enum https://docs.gitlab.com/api/merge_requests/#merge-status This will be part of v44 as we will increase with that the minimal version of Gitlab required
Per #44035, having support to extract: [tool.uv] required-version = "0.10.12" would be useful There may be other patterns we can capture, too
Similar to #42987, via #39276
Via #37723, extend the support in the Renovate config manager to bump: { "$schema": "https://docs.renovatebot.com/renovate-schema.json", "extends": [ "local>project-blue/components/renovate//src/renovate.json5#0.10.6" ], }
As noted in #41438, when we're not making sure that the isExecutable flag in renovate/lib/util/git/types.ts Line 63 in 42ee883 isExecutable?: boolean; is set. For instance, using the minimal repro: % copier --version copier 9.14.0 % copier update --skip-answered --defaults --answers-file .copier-answers.yml --vcs-ref v1.1.0 Updating to template version 1.1.0 jamietanna@caerbannog .venv tmp 41438 (git)-[main]* % gst ## main...origin/main M .copier-answers.yml ?? bin/ jamietanna@caerbannog .venv tmp 41438 (git)-[main]* % ls bin deploy.sh jamietanna@caerbannog .venv tmp 41438 (git)-[main]* % ls -al bin total 4 drwxr-xr-x 3 jamietanna staff 96 Mar 30 09:45 . drwxr-xr-x 8 jamietanna staff 256 Mar 30 09:45 .. -rwxr-xr-x 1 jamietanna staff 48 Mar 30 09:45 deploy.sh This does correctly copy an executable file, but when Renovate commits it does not set the isExecutable flag. We n
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 renovatebot/renovate, 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 renovatebot/renovate acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 62.3% were successfully merged into the primary branch.
renovatebot/renovate has a recorded first-timer success rate of 45.8%. 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 64.0 places renovatebot/renovate in the Welcoming tier.
The external pull request merge rate is 62.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, renovatebot/renovate currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for renovatebot/renovate 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.