repowiserepowise

Library

anomalyco / rune

Rune: Native UI framework

★ 7,712stars on GitHubRustMIT

Claude Code, Cursor, Codex or VS Code. No key. You approve one sign-in in your browser.

Repowise maps public repos from their source. Not affiliated with anomalyco. What is Repowise?

github.com/anomalyco/runeIndexed at eb5ae6c

What is rune?

Rune is a native GPU-rendered Rust UI framework for building apps on macOS, Windows, Linux and the web. Its core idea is that an app describes its screen as a function of its state, and the toolkit rebuilds that description as the state changes. It includes its own renderer, text, layout and springs, and it is written in Rust. Its code health is 8.1 out of 10 (Good), ranked #65 of 4,000+ indexed repos. The last commit to rune was on Nov 16, 2026, and 5 people have contributed.

As of commit eb5ae6c, indexed Nov 17, 2026. What it is comes from a model reading the README; the rest is measured from the source and git history, not from the maintainer.

For agentsrune.md

Repo facts: type, license, health, rank, contributors
rune facts
TypeLibrary
LicenseMIT
Code health8.1 / 10 (Good)
Health rank#65 of 4,000+ indexed repos
Last commitNov 16, 2026
Contributors5
Bus factor1
Size2,707 files, 322,464 lines

Explore rune

Ask about this code in your agent

This connects Repowise to rune's code. It does not install rune.

Useful if you want to change or fork rune: your agent can ask how it is put together and get answers that cite its files.

Ask about rune

Answers come from rune's README and source, with the files they cite. Two free answers a day without an account.

Featured answer

Rune is a native, GPU-rendered UI framework written in Rust for building apps on macOS, Windows, Linux and the web. An app describes its screen as a function of its state, and the crates/rune package rebuilds that description as the state changes while also routing input and running animations. The toolkit includes its own renderer, text, layout and springs, and crates/procwatch supplies process statistics and frame timing to the main renderer. The rune-fx crate's entry point is crates/rune-fx/src/lib.rs, and the repository holds 2707 files, with 1991 in the Application layer and 367 in Docs & Tooling. To start reading, open examples/hello as the README suggests, then look at crates/rune-fx/examples/gallery/main.rs, and note that apps can run headless to render frames to PNG and dump the element tree.

Files per layer in rune6 layers.

Basis: Inferred · knowledge graph· as of eb5ae6c

Want this for your own codebase? Map your repo free

About this page

Get a page like this for your own codebase

Repowise built this map of anomalyco/rune from its source and git history. It parses every symbol, draws the dependency graph, scores each file's health from complexity, duplication, coverage and churn, finds hotspots and owners in the history, and writes documentation for every module. Your coding agent reads the same index over MCP, so its answers cite real files.

Free for 2 public repos, with a page like this one. No card. See how Repowise works

Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed. Star Repowise on GitHub

anomalyco/rune FAQ

What is Rune?

Rune is a native GPU-rendered Rust UI framework for macOS, Windows, Linux and the web. It has its own renderer, text, layout and springs, and every app can run headless.

How does Rune work?

Rune apps describe their screen as a function of their state, and the crates/rune toolkit rebuilds that description as the state changes. The toolkit also draws the interface, routes input and runs animations.

What language is Rune written in?

Rust is the primary language of Rune. The repository also contains Python, TypeScript, JavaScript, shell and Swift files.

Who is Rune for?

Rune is for developers who build apps with it. Coding agents can also run those apps headless to render PNG frames and inspect the element tree.

What license does Rune use?

Rune uses the MIT license.

Code health

8.1out of 10Good

Hotspots average 5.5, the place fixes pay off most.

On the leaderboards:#4 of 24 Rust repos

Key features of rune

  • Renders apps on the GPU for macOS, Windows, Linux and the web, using its own renderer, text, layout and springs.
  • Runs every app headless so that a script or coding agent can render frames to PNG.
  • Dumps the element tree of an app so its structure can be inspected.
  • Drives an app with scripted input to check its behavior without a window.
  • Provides examples/hello as a starting point for new apps.

How anomalyco/rune works

The README points to examples/hello as the starting point for a new app. The crates/rune package is the toolkit that draws an app's interface, routes its input and runs its animations. Each app's screen description is rebuilt by crates/rune as its state changes. The crates/rune-fx/src/lib.rs file is an entry point of the rune-fx crate, and crates/rune-fx/examples/gallery/main.rs is its gallery example. The crates/procwatch package supplies process statistics and frame timing that the main renderer uses. Apps can run headless, which renders frames to PNG and dumps the element tree so the output can be inspected.

The codebase has 2,707 files and 45,278 symbols in 10 modules, led by Rust, Python and TypeScript. Code health is 8.1 out of 10, rated good.