AI agents, automations and apps that run your operations. Model agnostic.
C-Rank Grade: S (Elite) - 73/100
External PR Merge Rate: 73%
Response Time: -
First Timer Success: 78%
Budibase/budibase has a recorded first-timer success rate of 77.8%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Budibase/budibase respond to incoming external pull requests in approximately 0.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 72.8 places Budibase/budibase in the S tier.
The external contributor pull request merge rate for Budibase/budibase is 73.4%, based on public PR activity from non-core contributors.
Budibase/budibase currently has 24 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
AI agents, automations and apps that run your operations. Model agnostic.
Highly welcoming maintainers in Budibase/budibase. 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/Budibase/budibase?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (92% approval). Large PRs (>500 lines) take ~115 hours (33% approval). Keep your diff compact for rapid review.
Checklist I have searched budibase discussions and github issues to check if my issue already exists Hosting Cloud Describe the bug I was assigning users to a group when I noticed that the scrollbar in the popover was not loading new users. I had to search for them to be revealed. To Reproduce Steps to reproduce the behavior: Have many users, e.g. 20 Add a group Assign users See that only 10 will ever show Expected behavior While ten users should be within the scroll view port at one time, I should be able to continuously scroll loading new users in the 'Assign users' popover. Screenshots
I would like the ability to duplicate a view so i don’t have to recreate similar views from scratch. I would duplicate an existing View and make the changes.
Issue In QA, clicking Go to tenant can redirect to a chat-link handoff endpoint rather than opening the intended tenant. This appears to be session-dependent: the issue no longer occurs after clearing browser cookies. Actual result Clicking Go to tenant redirects the browser to a URL similar to: https://<qa-tenant>/api/chat-links/{appId}/{linkId}/handoff The user is therefore not taken directly to the target tenant. Expected result Clicking Go to tenant should consistently open the relevant tenant, regardless of any existing browser session or cookies. Investigation / suspected cause The behaviour may be caused by a conflict involving agent-related cookies or stale authentication/session state: The issue was observed with existing browser cookies. After clearing cookies and retrying, the redirect behaved correctly. This suggests that one or more cookies may cause the tenant navigation flow to resolve to the chat-link handoff URL instead of the tenant destination. We should investiga
Describe the feature request Currently, CSV exports are downloaded with a generated filename like ta4124352314523413412.csv, which is not user-friendly. It would be useful to add a field to the CSV export action where users can provide a custom filename to override the default name, so that exported files can be saved with a descriptive name like customer-export.csv or sales-report.csv. id: cnv_1cpbyuae Screenshots
v3.43.0 JSON is not an option when creating a new column on Postgres. If there is already a JSON column in the DB, it fetches it and all works ok. So, this looks like a UI issue. Worth checking for all SQL Dbs
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 Budibase/budibase, 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 Budibase/budibase acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 73.4% were successfully merged into the primary branch.
Budibase/budibase has a recorded first-timer success rate of 77.8%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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.8 places Budibase/budibase in the Elite tier.
The external pull request merge rate is 73.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Budibase/budibase currently has 24 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for Budibase/budibase 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.