Discofork
Repository brief

vadimdemedes/ink

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-30T20:13:33.505Z
1mo ago

vadimdemedes/ink

Ink is a widely used, actively maintained React-based renderer for building interactive command-line apps. The repository is large, with examples, recipes, benchmarks, tests, and a TypeScript source tree, and it targets modern Node.js 22+. Forks are potentially interesting if you want a mature CLI UI framework with strong ecosystem adoption and ongoing upstream activity.

GitHub
Loading tags...
Stars35,846
Forks883
Default branchmaster
Last pushed2026-03-27T07:24:19Z
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 you specifically want SolidJS in the terminal and accept a stale, highly divergent codebase. For most adopters, upstream Ink is the safer default because it is active, modern, and far better maintained.

Choose this fork if you want Ink as a platform for renderer experiments and advanced terminal UI behavior. Choose upstream if you want the safest, most current, least surprising base for ordinary CLI apps.

Choose this fork if you want Ink-like React CLI rendering but need the added batching/throttling behavior and stdin-focused changes. Avoid it if you want the most compatible, up-to-date Ink base or depend on focus helpers and `retainState`.

Choose this fork if your priority is terminal input behavior and prompt-workflow tweaks, and you can absorb divergence from upstream. Choose upstream if you want the newest fixes, lower maintenance risk, and a cleaner upgrade path.

Choose this fork only if you want an unchanged historical snapshot of Ink. For most adopters, upstream is the better choice because this fork has no unique features and is materially behind on fixes.

Prefer upstream Ink unless you need this exact snapshot; this fork does not show added capability and appears behind on recent fixes, so it is a poorer default choice for new adopters.

Prefer upstream Ink unless you specifically need this fork's exact historical snapshot. This fork shows no added capabilities, while remaining materially behind upstream, so it offers little adoption value beyond pinning.

Prefer upstream if you want the current, actively maintained Ink. Prefer this fork only if you specifically need an older, highly customized branch and are willing to own the maintenance burden.

Prefer upstream unless you specifically need this older snapshot or its custom examples/tests. For new work, the fork’s staleness and divergence make it a risky base; for legacy preservation, it may be useful as a starting point.

Prefer upstream unless you are locked to this fork’s historical behavior. This fork is stale, heavily diverged, and likely missing most of the modern maintenance and compatibility work that makes Ink attractive today.