astral-sh/uv

Choose this fork only if you need its older, patched behavior and can accept falling far behind upstream. For most users, upstream uv is the better default because this fork is stale and significantly diverged.

Choose this fork only if you need its custom workflow/auth/automation changes and can absorb ongoing merge work. If you mainly want a fast, maintained Python package manager, upstream uv is the safer default.

Choose this fork only if you need its custom workflow/tooling changes and are willing to own a materially divergent codebase. If you mainly want a fast, current Python package manager, upstream `astral-sh/uv` is the safer choice.

Choose this fork only if you want an old but heavily customized uv codebase and are prepared to own divergence. If you want current packaging behavior, bug fixes, and upstream compatibility, use upstream instead.

Choose this fork only if you need its specific behavior changes and are comfortable owning long-term divergence. For most adopters, upstream `uv` is the safer choice because this fork is materially stale and likely missing many current fixes and workflows.

Choose this fork if you need `uv` embedded as a Python-native library and want to avoid CLI overhead. Choose upstream if you want the full, latest `uv` feature set with less divergence and easier maintenance.

Choose this fork only if you need its custom workflow integration or internal behavior and are prepared to own a stale, highly divergent codebase. If you want current uv behavior, upstream is the safer default.

Prefer this fork only if its custom behavior is exactly what you need. For most adopters, upstream `uv` is the safer choice because this fork is substantially behind and likely missing a large amount of recent bugfix and UX work.

Choose this fork only if you need its custom output/logging behavior or other fork-specific workflow changes. If you want a stable, current `uv`, upstream is the better choice because this fork is stale and significantly diverged.