wasmi

WebAssembly (Wasm) Interpreter - An efficient, lightweight, and deterministic WebAssembly interpreter for embedded systems and plug-in runtimes.

Runssource: GitHubhomepageRustApache-2.0commit 2970aa871cc1

Rust, Apache-2.0 licensed. The project labels itself: cross platform, edge computing, efficient, embedded systems, fast, fuel consumption, game engine and interpreter.

wasmi runs. An Argusic agent installed it in 5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

The wasmi v2.0.0 CLI and libraries build cleanly, all 776 tests across wasmi/wasmi_wast/wasmi_cli pass, and the wasmi CLI executes WASI wasm and the WebAssembly spec-suite scripts.

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.04 (measured)
recorded runs
2
last tested
stars
2,345
forks
382
open issues
42
watchers
39
size
25 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.

Install time
5 minutes
Cold machine to finish
26 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
cargo test -p wasmi exited 0 (56+61+1 passed); cargo test -p wasmi_wast exited 0 (642 passed, 1 ignored); cargo test -p wasmi_cli exited 0 (7+3 passed); ./target/debug/wasmi --version printed 'wasmi 2.0.0'; ./target/debug/wasmi run crates/cli/tests/wats/simple_print.wat printed 'Hello World' and exited 0; ./target/debug/wasmi wast crates/wast/tests/spec/address.wast exited 0; cargo build finished with no error
Model tokens used
128,623
Exact commit tested
2970aa871cc1
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

 succeeded in 23262ms:
BUILD_EXIT=0
   Compiling wasmi_cli v2.0.0 (/work/repo/crates/cli)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 23.23s
wasmi 2.0.0
Everything verified. Final state is confirmed: build green, all three crate test suites green, CLI …
exec
/bin/sh -lc 'cd /work/repo && ./target/debug/wasmi run crates/cli/tests/wats/simple_print.wat' in /…
 succeeded in 0ms:
Hello World
tokens used
128,623

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 5 minutes, faster than the median of the 12 comparable projects Argusic has measured.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 13 cross-platform projects Argusic has installed and timed, wasmi was the 2nd fastest to reach a running state, and 10 of 13 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 5 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

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 Runner2/3Runs100.000.04
Argusic Runner1/3Runs100.000.03

Topics (from GitHub)

cross-platformedge-computingefficientembedded-systemsfastfuel-consumptiongame-engineinterpreterinterpretersplugin-systemruntimeruntimesrust-langrustlangsandboxessmart-contractsvirtual-machinewasmwebassemblywebassembly-runtime

Embed the badge

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

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

Questions

Does wasmi run?
Yes. wasmi runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test wasmi?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2970aa871cc1. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test wasmi?
The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does wasmi take to install?
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 wasmi need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing wasmi?
Nothing did, in the recorded run: zero errors between clone and running.
How does wasmi compare with the alternatives?
Of the 13 cross-platform projects Argusic has installed and timed, wasmi was the 2nd fastest to reach a running state, and 10 of 13 reached one at all.
Where is the evidence for wasmi?
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.

Discussion