Discofork
Repository brief

yarnpkg/yarn

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-31T09:29:34.874Z
1mo ago

yarnpkg/yarn

yarnpkg/yarn is the Yarn 1.x codebase for fast, reliable, secure dependency management. The repository is active but explicitly frozen for 1.x: new releases and ongoing maintenance have moved to yarnpkg/berry, with this repo kept mainly for historical purposes and occasional hotfixes.

GitHub
Loading tags...
Stars41,525
Forks2,733
Default branchmaster
Last pushed2026-03-30T18:04:45Z
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

Prefer this fork only if the cnpm/Taobao registry default is the primary requirement and you are intentionally staying on Yarn 1.x. For most adopters, the staleness and divergence make upstream Yarn Berry or a maintained alternative the safer choice.

Choose this fork if you need classic Yarn 1.x with a small set of practical performance and reliability improvements. Do not choose it if you want active maintenance, broad feature growth, or a path toward newer Yarn capabilities.

Prefer this fork only if you need the old Esy-specific compiled-language workflow and can accept a frozen, highly diverged codebase. For general Yarn usage, upstream Yarn Berry or stock Yarn 1 is the safer choice.

Prefer this fork only if you need Yarn 1.x with a narrow manifest-bin safety fix and can tolerate a stale codebase. If you want ongoing maintenance or broader fixes, upstream or Yarn Berry is the better choice.

Prefer this fork only if you need its exact legacy behavior and local build workflow; otherwise upstream Yarn 1.x or Yarn Berry is the safer choice.

Prefer upstream over this fork unless you specifically need an older historical snapshot. This fork adds no visible functionality and is too stale to be a good default choice for new or ongoing installs.

Choose this fork only if you want the classic Yarn 1.x codebase in essentially upstream form. It offers no clear fork-specific advantage, so most users should treat it as equivalent to upstream 1.x rather than a differentiated distribution.

Prefer upstream Yarn 1.x only if you need an unchanged snapshot; otherwise this fork offers no clear advantages and is behind upstream, so it is a weak choice for adopters unless legacy pinning is the goal.

Choose this fork only if you specifically need an old, frozen Yarn 1.x snapshot. For most users, the lack of changes plus the stale state makes upstream or a more current maintained fork a better choice.

Prefer upstream Yarn 1.x over this fork unless you specifically need a dormant historical snapshot. It adds no visible value and appears behind on maintenance.