Atmos is the open-source runtime for infrastructure — it builds, authenticates, and ships Terraform, OpenTofu, Packer, Ansible, Kubernetes, Helm, and containers the same way on your laptop, in CI, and with AI agents.
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 71%
Response Time: -
First Timer Success: 47%
cloudposse/atmos has a recorded first-timer success rate of 47.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in cloudposse/atmos 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 67.3 places cloudposse/atmos in the A tier.
The external contributor pull request merge rate for cloudposse/atmos is 70.8%, based on public PR activity from non-core contributors.
cloudposse/atmos currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in cloudposse/atmos welcoming community pull requests and bug fixes.
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/cloudposse/atmos?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 Tuesday - Thursday from 19:00 to 23:00 UTC (19:00 - 23:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (88% approval). Large PRs (>500 lines) take ~115 hours (32% approval). Keep your diff compact for rapid review.
Describe the Feature Add native support for GitLab CI/CD OIDC authentication to the Atmos authentication framework, similar to the existing github/oidc provider. GitLab CI can issue OIDC ID tokens for jobs using the id_tokens configuration. These tokens can be used to authenticate to cloud providers such as AWS without storing long-lived credentials in GitLab CI/CD variables. It would be useful if Atmos could consume a GitLab-issued OIDC token directly and use it as an authentication provider, for example: auth: providers: gitlab-oidc: kind: gitlab/oidc region: eu-west-1 identities: deploy: kind: aws/assume-role via: provider: gitlab-oidc principal: assume_role: arn:aws:iam::123456789012:role/GitLabDeployRole This would provide the GitLab equivalent of the existing github/oidc provider. Expected Behavior Atmos should be able to authenticate from a GitLab CI job using a GitLab-issued OIDC ID token and use that identity to assume
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 cloudposse/atmos, 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 cloudposse/atmos acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.8% were successfully merged into the primary branch.
cloudposse/atmos has a recorded first-timer success rate of 47.1%. Repositories ranked Welcoming 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 67.3 places cloudposse/atmos in the Welcoming tier.
The external pull request merge rate is 70.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, cloudposse/atmos 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 cloudposse/atmos 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.