Cap vs iced

Cap and iced share 8 technologies: Tokio, softbuffer, winit, image, resvg, tracing, log, and rfd. Both are written in Rust.

Read it as markdown

What they share and what sets them apart

Side by side

SizeLines written by people and agents, without generated ones; code files, without tests.
Cap1,176,626 lines written2,208 code files
iced102,496 lines written280 code files
Who writes itA commit counts as AI's when it carries its signature: a Co-Authored-By line, its author name or the merge of its branch.
Cap7.9% of its commits signed by AIWith Cursor, Codex, Claude Code, CodeRabbit, GitHub Copilot, and Devin
iced0.1% of its commits signed by AIWith Claude Code and Cursor
ActivityFrom GitHub and its history, on the day SeeRepo read it.
CapLast push November 4, 202610,666 commits24,340 stars
icedLast push November 1, 20265,914 commits31,958 stars
TestsThe files that test the code, and the share of code files a test imports.
Cap687 test files32.3% of its code files have a test that imports them
iced15 test files15.4% of its code files have a test that imports them

Frequently asked questions

Which is bigger, Cap or iced?
Cap, with 1,176,626 lines written; iced has 102,496.

The proof: CapSoftware/Cap's code at commit 81ef0e4

Which has more GitHub stars, Cap or iced?
iced, with 31,958 stars; Cap has 24,340.

The proof: iced-rs/iced on GitHub

Which has more tests, Cap or iced?
Cap, with 687 test files; iced has 15.

The proof: CapSoftware/Cap's code at commit 81ef0e4

Which was updated more recently, Cap or iced?
Cap: its last push was on November 4, 2026, and iced's on November 1, 2026.

The proof: CapSoftware/Cap's commits on GitHub

Which has more commits signed by AI, Cap or iced?
Cap: an AI signed 7.9% of its commits, with Cursor, Codex, Claude Code, CodeRabbit, GitHub Copilot, and Devin; in iced, 0.1%.

The proof: the commits each tool signed in CapSoftware/Cap

See inside your code, today.

Paste your repo and see it drawn, part by part: a medium one in under a minute.

Free, no account.

Or look inside SeeRepo's own →