Source: https://seerepo.com/compare/denoland/deno/vs/meta/flow
Markdown source: https://seerepo.com/compare/denoland/deno/vs/meta/flow.md
Description: deno and flow share 4 technologies: React, Tokio, log, and tracing. Both are written in Rust.

# deno vs flow

deno and flow share 4 technologies: React, Tokio, log, and tracing. Both are written in Rust.

- [denoland/deno](https://seerepo.com/r/denoland/deno): A modern runtime for JavaScript and TypeScript.
- [meta/flow](https://seerepo.com/r/meta/flow): Adds static typing to JavaScript to improve developer productivity and code quality.

## What they share and what sets them apart

- In common: React, Tokio, log, tracing
- Only in deno: rusqlite, SQLite, tower, wgpu, crossterm, ed25519-dalek, hmac, keyring, argon2, hkdf, image, zip, plist, opentelemetry, tracing-opentelemetry, env_logger, tracing-subscriber
- Only in flow: ora

## Side by side

| | deno | flow |
|---|---|---|
| Size | 1,217,015 lines written, 1,355 code files | 1,067,786 lines written, 1,098 code files |
| Who writes it | 2.4% of its commits signed by AI. With Claude Code, GitHub Copilot, Cursor, and Codex | 0% of its commits signed by AI |
| Activity | Last push October 29, 2026, 17,392 commits, 108,801 stars | Last push November 5, 2026, 22,732 commits, 22,307 stars |
| Tests | 4,394 test files. 6.1% of its code files have a test that imports them | 8,664 test files. 19.1% of its code files have a test that imports them |

- Size: Lines written by people and agents, without generated ones; code files, without tests.
- Who writes it: A commit counts as AI's when it carries its signature: a Co-Authored-By line, its author name or the merge of its branch.
- Activity: From GitHub and its history, on the day SeeRepo read it.
- Tests: The files that test the code, and the share of code files a test imports.

## Frequently asked questions

### Which is bigger, deno or flow?

deno, with 1,217,015 lines written; flow has 1,067,786.

The proof: [denoland/deno's code at commit e7b39eb](https://github.com/denoland/deno/tree/e7b39ebd55c85aaf6a29290c1f5a99e2e21e09dd)

### Which has more GitHub stars, deno or flow?

deno, with 108,801 stars; flow has 22,307.

The proof: [denoland/deno on GitHub](https://github.com/denoland/deno)

### Which has more tests, deno or flow?

flow, with 8,664 test files; deno has 4,394.

The proof: [meta/flow's code at commit 4449099](https://github.com/meta/flow/tree/444909947c29cac2c0d5bed541abba4388aa6899)

### Which was updated more recently, deno or flow?

flow: its last push was on November 5, 2026, and deno's on October 29, 2026.

The proof: [meta/flow's commits on GitHub](https://github.com/meta/flow/commits)

### Which has more commits signed by AI, deno or flow?

deno: an AI signed 2.4% of its commits, with Claude Code, GitHub Copilot, Cursor, and Codex.

The proof: [the commits each tool signed in denoland/deno](https://seerepo.com/r/denoland/deno/ai)

## Sources

- denoland/deno: Read on November 4, 2026, at commit e7b39eb (https://github.com/denoland/deno/tree/e7b39ebd55c85aaf6a29290c1f5a99e2e21e09dd)
- meta/flow: Read on November 5, 2026, at commit 4449099 (https://github.com/meta/flow/tree/444909947c29cac2c0d5bed541abba4388aa6899)

## What is your repo built with?

Any public repo, with no account: https://seerepo.com/r/owner/repo/built, with the owner and name it has on GitHub.