/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

ansible/ansible

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T12:04:20.856Z

3mo ago

ansible/ansible

Ansible/ansible is the upstream Ansible automation platform repository. It is a mature, active Python project for IT automation, configuration management, deployment, cloud provisioning, network automation, and orchestration. The repo is large, well-established, and highly forked, with recent commits through 2026-03-28 on the `devel` branch.

Loading tags...

Stars68,370

Forks24,164

Default branchdevel

Last pushed2026-03-28T12:19:07Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer this fork only if you need its existing custom behavior and are prepared to maintain a large Ansible divergence yourself; otherwise upstream is the safer choice because this fork is stale and likely missing many later fixes.

Prefer this fork only if you need its legacy behavior or custom module set and are prepared to own maintenance. For most adopters, upstream Ansible is the safer choice because this fork is heavily outdated and far removed from current development.

Choose this fork only if you need its vendor-specific or legacy behaviors and are willing to own the maintenance gap. For most users, upstream Ansible is the safer choice because this fork is materially behind and highly divergent.

Choose this fork only if you need its legacy customizations and are prepared to maintain a long-stale, deeply diverged Ansible branch. For most adopters, upstream is the safer and more complete choice.

Choose this fork only if its older baseline and added vendor/network coverage are the point. For most users, upstream Ansible is the safer default because this fork is stale and materially behind.

Choose this fork only if you want its custom divergence and are prepared to maintain it yourself. Do not choose it as a general-purpose replacement for upstream Ansible; it is stale, substantially different, and likely incompatible with current Ansible workflows.

Choose this fork only if you specifically need legacy Juniper/Junos behavior. For most adopters, upstream Ansible is the safer and more capable base.

Choose this fork only if Huawei CloudEngine support is the primary requirement and you are committed to legacy maintenance. For general Ansible use, upstream is the better choice because this fork is far behind and likely missing years of fixes and ecosystem progress.

Choose this fork only if you need its specific legacy customizations and are prepared to maintain a large downstream codebase. For most adopters, upstream Ansible is the safer and far more complete choice.

Choose this fork only if you need an old Ansible baseline and are willing to live without modern upstream improvements. For new work or active maintenance, upstream is the better choice.

Fork comparison

tanveerpot/ansible

38/100

stale

significant_divergence

Prefer this fork only if you need its existing custom behavior and are prepared to maintain a large Ansible divergence yourself; otherwise upstream is the safer choice because this fork is stale and likely missing many later fixes.

Likely purpose

A heavily customized Ansible fork that appears to preserve an older 2023-era codebase while carrying large local changes around templating, packaging, Windows/network support, and core modules.

Best for

Teams maintaining an older internal Ansible baseline; Organizations that need custom Windows or network automation behavior and are willing to own a fork; Engineers who prefer patching Ansible internals over following upstream releases

Additional features

Expanded or customized templating behavior in `lib/ansible/template` and `_jinja_bits`
Windows execution and test support changes in `lib/ansible/executor/powershell` and related Windows integration code
Network automation test/support changes, including `network_cli` and `ipaddress` compatibility code
Package manager module rewrites and fixes around `yum` and `dnf` handling
More explicit task/error handling such as better `delegate_to` errors and stricter module validation
Adds or extends platform-specific client support, such as mobile, Android, iOS, or desktop packaging.

Missing features

Falls behind upstream Ansible development by roughly 200 commits each way from the comparison point, so it likely misses newer core fixes and features from 2024-2026
Upstream work since late 2023 on apt, Windows, packaging, templating, and test infrastructure is not present in this fork state
The fork looks inactive since 2023-12-04, so adopters should expect slower security and compatibility updates
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
Some upstream plugin, tool, or MCP-style integration paths may be reduced or disabled.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Could suit teams that need a frozen or customized Ansible core with local patches already embedded
Likely useful for environments that rely on specific Windows, network, or package-management behavior
Large test and support-code footprint suggests deliberate adaptation for specialized workflows

Risks

Very stale compared with upstream activity
Large divergence makes rebasing and security backports expensive
Behavior may differ materially from upstream docs and community troubleshooting guidance

ansible/ansible · Discofork