xleak
A fast terminal Excel viewer with an interactive TUI. Features full-text search, formula display, lazy loading for large files, clipboard support, and export to CSV/JSON. Built with Rust and ratatui.
Runssource: GitHubRustMITcommit ef6560c8e168
Rust, MIT licensed. The project labels itself: cli, excel, ratatui, rust, rust lang, spreadsheet, spreadsheets and tui.
xleak runs. An Argusic agent installed it in 1.5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
xleak 0.2.6 builds, passes all 104 tests, and correctly displays, exports, and queries .xlsx files from the CLI.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Rust toolchain not installed0.3 minutes
- openpyxl missing (test fixture generator)0.2 minutes
- Install time
- 2 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- cargo test -> 65 passed, 39 passed; xleak test_comprehensive.xlsx -> rendered 14 rows x 3 cols; xleak --export csv/json -> valid output; xleak --sheet Formulas -f -> formulas displayed; xleak --list-tables -> 3 tables listed; xleak test_large.xlsx -n 5 -> 5 of 10000 rows shown
- Model tokens used
- 81,671
- Exact commit tested
- ef6560c8e168
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**Binary**: `xleak 0.2.6` — displays .xlsx tables, exports CSV/JSON/text, shows formulas, handles l… **Interactive TUI**: cannot be tested in a non-TTY environment (expected — errors with "requires a … No third-party keys needed; no mocks required. The only gaps were absent tooling (Rust toolchain, o… tokens used 81,671 All systems verified. Here's the summary: **Build**: `cargo build --release` completed successfully (1m 13s). **Code quality**: `cargo fmt --check` clean; `cargo clippy` emits only one pre-existing style warni… **Tests**: 65 unit tests + 39 integration tests — all 104 passed. **Binary**: `xleak 0.2.6` — displays .xlsx tables, exports CSV/JSON/text, shows formulas, handles l… **Interactive TUI**: cannot be tested in a non-TTY environment (expected — errors with "requires a … No third-party keys needed; no mocks required. The only gaps were absent tooling (Rust toolchain, o…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 1.5 minutes, faster than the median of the 126 comparable projects Argusic has measured.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
Of the 127 cli projects Argusic has installed and timed, xleak was the 34th fastest to reach a running state, and 116 of 127 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 1.5 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/xleak)Questions
- Does xleak run?
- Yes. xleak runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test xleak?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ef6560c8e168. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test xleak?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does xleak take to install?
- 1.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does xleak need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing xleak?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does xleak compare with the alternatives?
- Of the 127 cli projects Argusic has installed and timed, xleak was the 34th fastest to reach a running state, and 116 of 127 reached one at all.
- Where is the evidence for xleak?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.