excelize-wasm

A WebAssembly build of the Go Excelize library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets

Runssource: GitHubhomepageGoBSD-3-Clausecommit a11a6f1ba5d8

Go, BSD-3-Clause licensed. The project labels itself: ecma 376, excel, excelize, formula, go, golang, javascript and js.

excelize-wasm runs. An Argusic agent installed it in 10 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

npm install succeeds, rollup build produces dist/main.js/dist/main.cjs/dist/index.js, and the module loads and creates valid XLSX spreadsheets with data and charts when paired with the WASM binary from the published npm package.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.15 (measured)
recorded runs
1
last tested
stars
368
forks
45
open issues
8
watchers
11
size
1 MB
created
last push

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.

Time lost to each failure while testing excelize-wasm, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • rollup build failed: crypto is not defined in serialize-javascript (dependency of @rollup/plugin-terser)5 minutes
  • excelize.wasm.gz missing from source repo; requires Go compilation2 minutes
Install time
10 minutes
Cold machine to finish
13 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
node test_create.mjs: created XLSX (6354 bytes), node test_read.mjs: read back Sheet1!B2=100 and Sheet2!A2='Hello world.', node test_chart.mjs: created XLSX with chart (9035 bytes), node test_repo_build.mjs: dist/main.js + published wasm produced valid output (5660 bytes)
Model tokens used
92,076
Exact commit tested
a11a6f1ba5d8
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.

92,076
Now let me produce the final report with all findings.
Here's the complete summary:
**Installation**: The standard `npm install` succeeded (Node v18.19.1 despite engine requirement `>…
**Fix 1 - Build error**: Patched `node_modules/serialize-javascript/index.js` to defer `generateUID…
**Fix 2 - Missing WASM binary**: The source repo doesn't include `excelize.wasm.gz` (it's compiled …
**Verification**: All core features work end-to-end:
- `NewFile` / `NewSheet` / `SetCellValue` / `WriteToBuffer` → produces valid XLSX file (6354 bytes)
- `OpenReader` / `GetCellValue` / `GetRows` → reads back correct values ("Hello world.", 100)
- `AddChart` → creates chart-containing XLSX (9035 bytes)
- 150+ API functions exported; column/row conversion helpers work
- `init()` returns the excelize object successfully

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 10 minutes.
  • 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 BSD-3-Clause, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 10 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.15

Topics (from GitHub)

ecma-376excelexcelizeformulagogolangjavascriptjsmicrosoftnpmofficeooxmlspreadsheettstypescriptvbawasmwebassemblyxlsmxlsx

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/excelize-wasm.svg)](https://argusic.com/subject/excelize-wasm)

Questions

Does excelize-wasm run?
Yes. excelize-wasm runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test excelize-wasm?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit a11a6f1ba5d8. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test excelize-wasm?
The run that produced this verdict cost $0.15: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does excelize-wasm take to install?
10 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 excelize-wasm need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing excelize-wasm?
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.
Where is the evidence for excelize-wasm?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion