Discofork
Repository brief

denoland/deno

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-29T22:24:47.311Z
3mo ago

denoland/deno

Deno is a large, active open-source JavaScript/TypeScript/WebAssembly runtime built on Rust and V8. It is very widely adopted in fork/star terms (5,982 forks, 106,441 stars) and was updated and pushed on 2026-03-29, so forks are likely to stay relevant. The repository is broad and production-oriented, with runtime, CLI, extensions, libraries, tests, and tooling all in one Rust workspace.

GitHub
Loading tags...
Stars106,441
Forks5,982
Default branchmain
Last pushed2026-03-29T18:13:20Z
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

6 of 6 fork briefs
Selected

Prefer upstream unless you specifically need this fork's older baseline or are committed to maintaining a deep custom divergence. For most adopters, the fork is too stale and too far from current Deno to be a safe starting point.

Choose this fork only if built-in window system integration is the core requirement. If you mainly want current Deno behavior, compatibility, or long-term maintainability, upstream is the safer choice.

Choose this fork only if you specifically need its desktop-oriented customizations and are willing to own a heavily outdated codebase. For most adopters, upstream Deno is the safer choice because this fork is far behind and significantly diverged.

Prefer this fork only if subprocess sandboxing is the main requirement. If you want current Deno compatibility, tooling, and bugfixes, upstream Deno is the safer default.

Adopt only if you specifically want an old experimental Rust prototype to study or extend. If you want a usable Deno fork, the fork is too stale and too far behind upstream to be a good base.

Choose this fork only if native code sandboxing is the goal and you are prepared to own a large compatibility and maintenance burden. For general Deno users, upstream is the safer default because this fork is materially behind and heavily diverged.