awx

ansible/awx

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.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 2, 2026
today
Ship score
85/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 15,525 → 15,575 (Aug 18 – Sep 29, 2026)
+35 stars in the 28 days to 2026-09-29

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
15.6K
Forks
3.7K
Open issues
1.9K
Watchers
359
Primary language
Python
License
Other
Created
May 17, 2017
Owner
ansible · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. License unknown — GitHub’s own license field, not legal advice. 110 startups in the directory ship primarily in Python.

Topics

#ansible#automation#awx#django#django-rest-framework#hacktoberfest#python#reactjs

How it got here

What the classifier decided, and when.

Read by Jev, TypeSafe’s classifier, on Sep 22, 2026, which did not call this an open-source startup — it chose a package or library instead, and put os_startup at 31% (self-hostable 85%, hosted offering 56%). The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory. This one is in that queue, waiting for a person — removing a listing is a pull request a human opens.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-02This is the badge for ansible/awx, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/ansible/awx.svg)](https://ossean.com/ansible/awx)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.