C-Rank Grade: B (Solid) - 50/100
External PR Merge Rate: 52%
Response Time: 12h
First Timer Success: 63%
opentofu/setup-opentofu has a recorded first-timer success rate of 62.5%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in opentofu/setup-opentofu respond to incoming external pull requests in approximately 12.3 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 50.1 places opentofu/setup-opentofu in the B tier.
The external contributor pull request merge rate for opentofu/setup-opentofu is 52.0%, based on public PR activity from non-core contributors.
opentofu/setup-opentofu currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Open-source repository analyzed with precision C-Rank telemetry.
Balanced & professional review environment in opentofu/setup-opentofu. 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/opentofu/setup-opentofu?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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~8 hours (65% approval). Large PRs (>500 lines) take ~59 hours (23% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in JavaScript.
Run Claude Desktop’s Cowork mode natively on Linux — no macOS or VM required
JavaScript security CLI that allow you to deeply analyze the dependency tree of a given package or local Node.js project.
Advanced Subscription Manager for QX, Loon, Surge, Stash, Egern and Shadowrocket!
When executing the action, we get: set -euo pipefail CONSTRAINT="~1.11" TAG=$(python3 - <<PYEOF import json, urllib.request, sys, re constraint = "${CONSTRAINT}" req = urllib.request.Request( "https://api.github.com/repos/opentofu/opentofu/releases?per_page=50", headers={"Accept": "application/vnd.github+json"} ) with urllib.request.urlopen(req) as r: releases = json.load(r) versions = [] for rel in releases: tag = rel.get("tag_name", "") if rel.get("prerelease") or rel.get("draft"): continue m = re.fullmatch(r'v(\d+\.\d+\.\d+)', tag) if m: versions.append((list(map(int, m.group(1).split("."))), tag)) versions.sort(reverse=True) if constraint in ("latest", ""): print(versions[0][1]) sys.exit(0) # ~MAJOR.MINOR -> latest patch of that minor m = re.fullmatch(r'~(\d+)\.(\d+)', constraint) if m: major, minor = int(m.group(1)), int(m.group(2)) for parts,
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 opentofu/setup-opentofu, 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 opentofu/setup-opentofu acknowledge new external contributions in approximately 12 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 52.0% were successfully merged into the primary branch.
opentofu/setup-opentofu has a recorded first-timer success rate of 62.5%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~12 hours. 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 50.1 places opentofu/setup-opentofu in the Solid tier.
The external pull request merge rate is 52.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, opentofu/setup-opentofu currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for opentofu/setup-opentofu 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.