Terraform Grafana provider
C-Rank Grade: B (Solid) - 50/100
External PR Merge Rate: 72%
Response Time: 10d
First Timer Success: 76%
grafana/terraform-provider-grafana has a recorded first-timer success rate of 75.8%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in grafana/terraform-provider-grafana respond to incoming external pull requests in approximately 240.7 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 49.6 places grafana/terraform-provider-grafana in the B tier.
The external contributor pull request merge rate for grafana/terraform-provider-grafana is 72.2%, based on public PR activity from non-core contributors.
grafana/terraform-provider-grafana currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in grafana/terraform-provider-grafana.
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/grafana/terraform-provider-grafana?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 12:00 to 16:00 UTC (12:00 - 16: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 ~156 hours (90% approval). Large PRs (>500 lines) take ~1155 hours (33% 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 Go.
Panurs provides a collection of APIs and services that streamline development for token-based distributed applications.
Packer is a tool for creating identical machine images for multiple platforms from a single source configuration.
Yet another codex remote in feishu
Feature Request Description Today, the Grafana Terraform provider does not expose a way to configure signed SAML authentication requests for Grafana SSO. This makes it impossible for users who require signed AuthnRequests to fully manage their SAML configuration via Terraform. While SAML request signing is supported in Grafana, the corresponding option is not currently available in the Terraform provider, which can lead to configuration drift or force users to manage part of their SSO setup outside of Infrastructure as Code. Problem / Motivation Many IdPs (for example Okta, Azure AD, and Ping) require or strongly recommend signed SAML AuthnRequests. Without Terraform support for this setting: Users cannot fully manage SSO via Infrastructure as Code Terraform runs may overwrite or revert manually configured SSO settings Teams with security or compliance requirements are blocked from adopting Terraform for SSO Proposed Solution Extend the grafana_sso_settings resource to support conf
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 grafana/terraform-provider-grafana, 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 grafana/terraform-provider-grafana acknowledge new external contributions in approximately 10 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 72.2% were successfully merged into the primary branch.
grafana/terraform-provider-grafana has a recorded first-timer success rate of 75.8%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~10 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 49.6 places grafana/terraform-provider-grafana in the Solid tier.
The external pull request merge rate is 72.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, grafana/terraform-provider-grafana 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 grafana/terraform-provider-grafana 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.