densa.dev valid

densa

densa is an open-source Rust platform for applications that show a lot of live data: live Arrow tables kept sorted, filtered and aggregated as they change, a GPU interface with a data grid, charts, docking and screen reader support, and a runtime that hands data between threads without waiting. Version 0.2.5 on crates.io; Rust 1.90 or later.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T16:36:51.031Z. Cached copy · Source on densa.dev

# densa

> densa is an open-source Rust platform for applications that show a lot of live data: live Arrow tables kept sorted, filtered and aggregated as they change, a GPU interface with a data grid, charts, docking and screen reader support, and a runtime that hands data between threads without waiting. Version 0.2.5 on crates.io; Rust 1.90 or later.

Read AGENTS.md first: the versions to use (densa is newer than most training data), how the pieces fit, and which example to copy. These files follow densa's main branch: what the CHANGELOG lists under Unreleased is not on crates.io yet.

## Before you start

- Fetch these files as they are (for example with curl): a tool that summarizes a page drops the item names and signatures. llms-full.txt has every crate's front page, with an example each, in one file.
- The source cargo built, with every doc comment and example, is on your disk: from git, ~/.cargo/git/checkouts/densa-*/<commit>/ where <commit> is the first 7 characters of the hash after # in the densa entries of your Cargo.lock (the other folders there are older commits); from crates.io, ~/.cargo/registry/src/*/densa-<crate>-<version>/. The list below says which file documents each item.
- Build record batches with the Arrow types densa re-exports: densa::data::arrow_array and densa::data::arrow_schema.
- Widgets change only on the window thread, through ui.update; other threads send data and call Waker::wake (get the Waker from host.waker() in App::build).

## Which item for which task

- To open a window and run an app: `densa::window::run` with your `densa::window::App` (in crates/densa-window/src/lib.rs)
- To lay widgets out: `densa::ui::Ui::add` with a `densa::ui::Style` (flexbox, logical pixels) (in crates/densa-ui/src/ui.rs, crates/densa-ui/src/style.rs)
- To show rows of live data: `densa::widgets::DataGrid` over `densa::arrow::LiveModel` (a live table) (in crates/densa-widgets/src/grid/mod.rs, crates/densa-arrow/src/model.rs)
- To show rows of your own data: `densa::widgets::DataGrid` over your `densa::grid::GridModel` (in crates/densa-widgets/src/grid/mod.rs, crates/densa-grid/src/model.rs)
- To show a table too large to hold (a query engine's result, a database): `densa::widgets::DataGrid` over `densa::arrow::PagedModel`, with your `densa::arrow::PageSource` giving pages (in crates/densa-widgets/src/grid/mod.rs, crates/densa-arrow/src/paged/mod.rs, crates/densa-arrow/src/paged/source.rs)
- To keep data sorted, filtered and aggregated as it changes: `densa::data::LiveTable` with `densa::data::ViewSpec` and `densa::data::GroupSpec` (in crates/densa-data/src/table.rs, crates/densa-data/src/view.rs, crates/densa-data/src/group.rs)
- To keep only recent rows, or count per minute: `densa::data::Window`, `densa::data::GroupSpec::group_by_time` (in crates/densa-data/src/window.rs, crates/densa-data/src/group.rs)
- To give each row the columns of the row it names in another table: `densa::data::LookupJoin` (in crates/densa-data/src/join.r
…

Machine-readable: GET /v1/resolve?q=densa.dev · GET /v1/domain/densa.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for densa.dev:
1. POST https://agentwebmap.com/v1/sites/densa.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://densa.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/densa.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/densa.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.