Open source IaC Automation and Collaboration Software.
C-Rank Grade: S (Elite) - 72/100
External PR Merge Rate: 78%
Response Time: -
First Timer Success: 65%
terrakube-io/terrakube has a recorded first-timer success rate of 64.7%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in terrakube-io/terrakube 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 71.7 places terrakube-io/terrakube in the S tier.
The external contributor pull request merge rate for terrakube-io/terrakube is 77.9%, based on public PR activity from non-core contributors.
terrakube-io/terrakube currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in terrakube-io/terrakube. 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/terrakube-io/terrakube?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 22:00 UTC (22:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (35% approval). Keep your diff compact for rapid review.
Feature description 💡 Bitbucket Data Center / Server (self-hosted) is currently not usable with Terrakube's webhook-driven or PR workflows. The existing BITBUCKET provider targets Bitbucket Cloud, and the gap is not reachable through configuration — unlike GitHub Enterprise or self-hosted GitLab, which work today by overriding the API URL. I'd like to request Bitbucket Data Center as a first-class VCS provider, covering push-triggered runs and the Atlantis-style PR workflow added in 2.33.1. Anything else? No response
Feature description 💡 To save on run resources, Terrakube should cancel runs from previous commits when a new commit to target branch has been received. This should only happen only on Pull Requests event - not direct pushes to a branch event. Benefit This helps reduce the resource usage by Terrakube by stopping unnecessary runs. Anything else? Just a feature suggestion for anyone to take on when they can.
Feature description 💡 Following what is also implemented on Terraform Cloud, a way to set modules and provider versions as deprecated or remove them from usage. In case it's marked as deprecated, show a warning message (the message to show could be customizable - example a date until removal could be set). If the version is removed, normal implementation that returns that version not available or, if possible, also a custom message on what steps to make (upgrade modules, etc.). This could be helpful also in case a provider launches a new version that doesn't work (as occurred recently with aws provider) and just by removing it from the registry everything works again. Anything else? No response
Feature description 💡 Currently, when a workspace execution requires plan approval (added as a task to the template), the system does not track or display which user approved the plan before the apply phase. This makes it difficult to audit who authorized infrastructure changes and reduces accountability in team environments. Proposed Solution: Add a new field to store the user who approved the plan Update the approval workflow to capture and save the user ID/email when a plan is approved Display the approver information in the job details UI, similar to how the job creator is currently shown Include this information in job history and audit logs Benefits: Improved audit trail for infrastructure changes Better accountability in team environments Enhanced security and compliance tracking Clear visibility into who authorized specific changes Implementation Notes: Backend changes to capture approver information Frontend updates to display approver details in the job details view
Bug description 🐞 After workspace creation and template import. the Terrakube web ui is locked up. Instead an error page shows up - Unexpected Application Error! Failed to construct 'URL': Invalid URL This happened on a "new" Terrakube installation, we encounter this error after some updates Unexpected Application Error! Failed to construct 'URL': Invalid URL TypeError: Invalid URL at pe (https://<hostname>/assets/OrganizationDetailsPage-DlFfmGmY.js:1:7141) at be (https://<hostname>assets/OrganizationDetailsPage-DlFfmGmY.js:1:9602) at fo (https://t<hostname>/assets/antd-B7aNw2sr.js:8:47557) at ac (https://<hostname>/assets/antd-B7aNw2sr.js:8:70163) at Sc (https://<hostname>/assets/antd-B7aNw2sr.js:8:80446) at ku (https://<hostname>assets/antd-B7aNw2sr.js:8:116007) at Eu (https://<hostname>/assets/antd-B7aNw2sr.js:8:115054) at Tu (https://<hostname>/assets/antd-B7aNw2sr.js:8:114887) at pu (https://<hostname>/assets/antd-B7aNw2sr.js:8:111714) at
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 terrakube-io/terrakube, 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 terrakube-io/terrakube acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 77.9% were successfully merged into the primary branch.
terrakube-io/terrakube has a recorded first-timer success rate of 64.7%. 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 71.7 places terrakube-io/terrakube in the Elite tier.
The external pull request merge rate is 77.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, terrakube-io/terrakube 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 terrakube-io/terrakube 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.