TopGit
GitHub Repo Review

Deno review: 108,941 stars, few firsthand opinions

DTopGit review image for denoland/deno
Review by Topgit.dev for denoland/deno, with GitHub repository stats and README context.
Quick verdict

Deno is a runtime for JavaScript, TypeScript, and WebAssembly, built with the V8 engine, Rust, and the Tokio async framework. Its quickstart runs a .ts file straight through deno run and blocks network access until you add --allow-net. Reach for Deno when you want TypeScript executed without a separate build step and permissions set on the command line; skip it if your project already leans on Node-specific tooling you don't want to touch.

Stars
โ˜… 108.9k
Forks
โ‘‚ 7.3k
Contributors
๐Ÿ‘ฅ 1.3k
Language
Rust
License
MIT
Topic
Frontend
Updated
Oct 2026

denoland/deno has 108,941 stars and 6,970 forks, yet the opinions I could verify are a thin slice of the Hacker News and GitHub material collected for it. Much of what mentions the repo is link-sharing, release announcements, feature requests and maintainer replies, none of which tells you what depending on it feels like. What is left is a handful of users scattered across 2018, 2020 and 2026.

The oldest complaint is about design. In a GitHub issue from the project's earliest days (GitHub lists 2018-05-15 as its creation date), hstarorg, 2018-05-31 wrote "Import from url is very hard to use." and gave "Heavily dependent on the network" as one of the reasons.

The 2020 Hacker News thread is more split. 205g0, 2020-12-10 argued that a runtime which does not integrate the build step leaves room for others, writing "You allow competition and the market comes up with great ideas like Vercel did with pkg." In a second comment, 205g0, 2020-12-10 added that "Deno as great as it sounds doesn't offer enough benefits" to replace Node. On the other side, breatheoften, 2020-12-10 wrote "deno seems really amazing" and liked the "single file distribution of a secure runtime for application code". nikisweeting, 2020-12-10 described a practical snag: "Last time I tried deno there was some friction with depending on npm packages that didn't natively support deno without vendoring", then asked whether that had improved. The excerpt contains no answer.

The 2026 voices are fewer. On Hacker News, antalis, 2026-10-09 compared Deno with QuickJS for yt-dlp: "QuickJS works fine for yt-dlp and is way smaller: less than 1 MB vs 34 MB + its many dependencies for Deno." And Tiberium, 2026-06-25 said "those two issues recently directly affected my projects", adding that "Seems like the core of these issues was a Claude-coauthored PR". That is one commenter's reading, and the excerpt is cut off. The PR's author bartlomieju replied in the thread that using AI was not really at fault and that it was a giant rewrite of how `node:http` is done in Deno, so it should not be treated as a finding about the project as a whole.

Set against the star count, this is quiet evidence. The repo is MIT-licensed, written in Rust, carries 1,716 open issues and was last pushed on 2026-10-29, so it is plainly alive; what the mentions do not show is how many people run it in production and how they rate it. Every item comes from two platforms, and the 2018 and 2020 comments predate the current releases, so their npm and URL-import complaints may be out of date.

View on GitHub โ†—

Related repositories

Source & attribution

Facts and quotes sourced from the denoland/deno GitHub repository and its README.

GitHub data ยท last synced Nov 10, 2026Reviewed by Henry
โ† Back to TopGit

Is deno worth your time?

ChatGPT, Claude and Perplexity can all read this page. Ask one of them what it makes of deno.

GitHub