Discofork
Repository brief

xtekky/gpt4free

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:51:33.477Z
3mo ago

xtekky/gpt4free

xtekky/gpt4free is a very large, actively maintained Python project for accessing multiple language-model and media-generation providers through a unified interface. It includes a Python client, async client, OpenAI-compatible FastAPI API, web GUI, CLI, Docker images, and browser JS client support. The repo is highly popular and actively developed, with 65,943 stars, 13,646 forks, and commits from 2026-03-21.

GitHub
Loading tags...
Stars65,943
Forks13,646
Default branchmain
Last pushed2026-03-21T20:56:29Z
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

8 of 8 fork briefs
Selected

Prefer upstream unless you specifically want this fork’s custom behavior or are intentionally working from an older, heavily modified base. This fork looks more like a divergent customization branch than a healthy replacement for upstream.

Choose this fork only if you want its older, customized UI and are comfortable owning maintenance yourself. For most adopters, upstream is the safer choice because this fork is stale, heavily diverged, and likely missing many current fixes and features.

Choose upstream unless you explicitly want this older customized snapshot. The fork is materially stale and has likely shed more functionality than it added, so its main value is for narrow legacy or compatibility use cases.

Choose this fork if you want a customized, narrower, and more opinionated gpt4free with specific provider and routing changes. Prefer upstream if you want the broadest provider coverage, freshest fixes, and lower maintenance risk.

Adopt this fork only if you want its narrower, customized provider stack and are willing to own maintenance. If you want the broadest and freshest gpt4free feature set, upstream is the safer choice.

Prefer this fork only if you specifically want its customizations and are prepared to own maintenance. For most adopters, upstream is the safer choice because this fork is far behind and likely missing newer provider support and fixes.

Choose this fork only if you specifically want a clean, unmodified snapshot. For most adopters, upstream is the better default because this fork is stale and adds no visible functionality.

Choose this fork if you want a customized, self-hostable gpt4free variant and are willing to absorb maintenance burden. Choose upstream if you want broader provider coverage, fresher fixes, and lower integration risk.