Discofork
Repository brief

python-poetry/poetry

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-30T19:51:58.178Z
1mo ago

python-poetry/poetry

Poetry is a large, actively maintained Python packaging and dependency-management project. It targets users who want a single `pyproject.toml`-based workflow for declaring, installing, locking, and publishing dependencies, with recent commits focused on bug fixes, installer/security behavior, Windows path handling, and PEP 639 support. It appears mature and high-visibility, with 34k+ stars and 2.4k+ forks, so forks are most likely interesting for teams working on packaging tooling, dependency resolution, installers, or ecosystem compatibility.

GitHub
Loading tags...
Stars34,266
Forks2,421
Default branchmain
Last pushed2026-03-30T18:08:40Z
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
Selected

Choose this fork only if its custom locking/cache behavior is the goal and you are prepared to maintain a very outdated, highly divergent codebase. For most adopters, current upstream Poetry is the safer default.

Choose this fork if you need the Replit-specific install and workflow behavior and can accept lag versus upstream; choose upstream if you want the newest Poetry fixes, broader compatibility, and lower maintenance risk.

Prefer upstream unless you specifically need legacy Poetry behavior or these older installer/workaround changes. This fork looks useful as a compatibility-oriented customization base, not as a current replacement for maintained Poetry.

Choose this fork only if you need its legacy compatibility or old behavior. For general use, upstream is far better: this fork is far behind, heavily diverged, and likely missing important modern fixes and standards support.

Use this only if you specifically want a private mirror of upstream Poetry; otherwise upstream is the better choice because this fork adds nothing and is already behind current fixes.

Choose upstream unless you specifically need a private, unmodified fork. This fork adds no visible value and trails upstream by 53 commits, so adopters would mainly be taking on stale-code risk without receiving new capabilities.

Prefer this fork only if you need its installer and workflow changes and can absorb heavy divergence. For most adopters, upstream Poetry is the safer choice because this fork looks materially behind and more disruptive to integrate.

Choose this fork only if you explicitly want an older, customized Poetry line and can own the maintenance burden. For most adopters, upstream is the safer choice because this fork appears significantly behind on recent fixes and standards support.

Prefer upstream unless you explicitly need this frozen snapshot; this fork adds no visible features and is already far behind on fixes.

Choose upstream Poetry unless you specifically need this older snapshot; this fork adds no visible capabilities and appears stale relative to the active project.