AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 48%
Response Time: -
First Timer Success: 36%
ansible/awx has a recorded first-timer success rate of 36.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ansible/awx 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 59.6 places ansible/awx in the A tier.
The external contributor pull request merge rate for ansible/awx is 47.9%, based on public PR activity from non-core contributors.
ansible/awx currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in ansible/awx. 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/ansible/awx?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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (60% approval). Large PRs (>500 lines) take ~115 hours (22% approval). Keep your diff compact for rapid review.
Please confirm the following I agree to follow this project's code of conduct. I have checked the current issues for duplicates. I understand that AWX is open source software provided for free and that I might not receive a timely response. I am NOT reporting a (potential) security vulnerability. (These should be emailed to [email protected] instead.) Bug Summary Summary When running AWX with multiple task replicas (>1), jobs fail immediately with FileExistsError on /var/lib/awx/projects when triggered in parallel. The root cause is a TOCTOU race condition in acquire_lock(). AWX Version 24.6.1 (also present in latest devel branch as of 2026-05-05) Steps to Reproduce Deploy AWX with replicas: 3 and a RWX PVC for projects (CephFS/NFS) Trigger 2+ jobs simultaneously targeting different projects Observe immediate failure on some jobs Error File "awx/main/tasks/jobs.py", line 379, in acquire_lock os.mkdir(settings.PROJECTS_ROOT) FileExistsError: [Errno 17] File exists: '/var/lib/
Please confirm the following I agree to follow this project's code of conduct. I have checked the current issues for duplicates. I understand that AWX is open source software provided for free and that I might not receive a timely response. I am NOT reporting a (potential) security vulnerability. (These should be emailed to [email protected] instead.) Bug Summary When using input_inventories on a constructed inventory, the module internally calls resolve_name_to_id('inventories', item) without scoping the lookup to any organisation. If the same inventory name exists in multiple organisations, the lookup returns more than one result and the module fails with: Request to /api/v2/inventories/?name=<inventory_name> returned 2 items, expected 1 This occurs despite the organization parameter being correctly set on the constructed inventory itself. The organization parameter scopes the constructed inventory lookup correctly (as seen in module.get_one with data={'organization': org_id
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 ansible/awx, 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 ansible/awx acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 47.9% were successfully merged into the primary branch.
ansible/awx has a recorded first-timer success rate of 36.0%. 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 59.6 places ansible/awx in the Welcoming tier.
The external pull request merge rate is 47.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ansible/awx currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for ansible/awx 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.