WAVM: nightly tags with a four year gap, a side channel warning that points at OS processes, and an Ubuntu 18.04 build image
WebAssembly Virtual Machine
At a glance
- What is it?
- A WebAssembly virtual machine for non-browser applications that compiles modules to machine code with LLVM and executes bounds-checked memory at native cost using virtual memory and signal handlers. Its release list is date-stamped nightlies with a four year hole, and its development container is Ubuntu 18.04 with LLVM 6.
- Who is it for?
- WAVM fits a team embedding WebAssembly in a desktop or server process that controls its own toolchain and wants ahead-of-time compilation instead of an interpreter. It does not fit anyone treating it as a sandbox for hostile modules.
- Can I use it commercially?
- Yes. BSD-3-Clause is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Activity is slowing. The repository last received commits 7 months ago.
- What is it written in?
- Mainly C++, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 13, 2026, and from our analysis. They are not legal advice.
Star history
- WAVM/WAVM2,788 ★ · +6
| Repository | 2026-10-04 | 2026-11-13 |
|---|---|---|
| WAVM/WAVM | 2.8k | 2.8k |
6 Stars in the last 40 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The release list is date-stamped nightlies with a four year hole
There are no version numbers in this project's releases, only dates. The newest tag is nightly/2026-04-05, published on the morning of 2026-04-05. Before that, the previous tag is nightly/2022-05-14, published in May 2022, and before that nightly/2022-05-03 from the same month. So the release history is two nightlies twelve days apart in May 2022, then nothing for roughly four years, then a single nightly in April 2026. The default branch is master and its last push is dated 2026-04-05, the same day as that nightly, so the visible release history and the branch agree with each other and both stop there. For anyone who needs to cite or pin a WAVM build, a date is the only identifier on offer, and there is exactly one recent one.
The README tells you to isolate with OS processes, not with the VM
The safety section is the most useful thing in a short README, because it states both what the virtual machine does and what it does not do. WAVM prevents WebAssembly code from accessing state outside of the WebAssembly virtual machine, and prevents it from calling native code that you did not explicitly link with the module. Then a footnote qualifies that. WAVM is vulnerable to some side-channel attacks, such as Spectre variant 2. It may add further mitigations for specific attacks, but it is impractical to guard against all of them. And the instruction to the reader is explicit: you should use another form of isolation, such as OS processes, to protect sensitive data from untrusted WebAssembly code. That is the project's own statement of where the boundary is not, and it is the sentence to quote in any threat model.
Virtual memory reduces explicit bounds-check overhead
WAVM uses LLVM to compile WebAssembly to machine code. The project describes performance as close to native and notes that CPU-specific code generation can sometimes outperform a native build; actual results depend on the workload and comparison.
Its README also describes using virtual memory and signal handlers to avoid explicit bounds checks on the normal memory-access path. Invalid accesses can fault and be converted into WebAssembly traps. This design needs a large virtual address space, but it should not be interpreted as a guarantee of zero overhead in every program: measure on the intended hardware and workload. WAVM also warns that its isolation has side-channel limitations and recommends another isolation layer, such as OS processes, for sensitive data exposed to untrusted code.
The extension list names proposals without revision numbers
The claim is full support for WebAssembly 1.0 plus many proposed extensions, and eleven are listed with links: WASI, 128-bit SIMD, threads, reference types, multiple results and block parameters, bulk memory operations, non-trapping float-to-int conversions, sign-extension instructions, exception handling, the extended name section, and multiple memories. Each of those proposals has been revised more than once since it was written, and the list carries no revision numbers, no dates and no note about which draft an implementation follows. For an embedder this matters more than the headline: the difference between two revisions of the SIMD or threads proposal is not academic, since it changes the binary format a module must be compiled against. The documentation is three files deep from here, at Doc/GettingStarted.md, Doc/Building.md and Doc/CodeOrganization.md, and the portability detail has its own page at Doc/PortabilityMatrix.md.
The runtime needs a 64-bit address space, and the assembler does not
Portability is stated as a matrix rather than a promise. WAVM is written in portable C and C++ with a small amount of architecture-specific assembly and LLVM IR generation code. It is tested on and fully supports x86-64 and AArch64 on Windows, macOS and Linux, with all six platform and architecture combinations tested in CI. Beyond that it is designed to run on any POSIX-compatible system but is not routinely tested on others, which is a narrower claim than the six combinations implies. The one hard limit is stated plainly: the runtime requires a 64-bit virtual address space and so is not portable to 32-bit hosts. The exception is narrow and practical, because the assembler and disassembler do work on 32-bit hosts. So a 32-bit build target can still compile and inspect modules, it just cannot run them.
The development container is Ubuntu 18.04 with LLVM 6
The Dockerfile in the tree is the build recipe a contributor gets, and it starts from ubuntu:18.04. It runs apt-get update, installs software-properties-common, runs apt-get update a second time, and then installs autoconf, automake, build-essential, cmake, libtool, llvm-6.0, make, ninja-build, sudo, unzip and zlib1g-dev. The compiler pin is the informative part: LLVM 6 is what this project expects to be buildable against, and anyone on a current distribution will be compiling against something two major generations newer. The rest of the file copies the whole source tree into /code, configures with
cmake -G Ninja /code -DCMAKE_BUILD_TYPE=RelWithDebInforuns ninja, and leaves the container at a bash shell as its default command, with no user directive, so the build runs as root in the image. Two smaller details: the cleanup line is written as a single apt-get clean autoclean, which passes autoclean along as an argument rather than running it as its own command, and the image never ships a built WAVM as its entry point.
A TextMate grammar and a Chromium reference sit beside the C++ tree
The top level listing explains more about how the project is worked on than the README does. There is a .clang-format and a .clang-tidy for the C++ side, an .editorconfig and a .gitattributes for everything else, and a CMakeLists.txt with a cmake directory beside it. Build, Lib, Include, Programs, Test, Benchmarks and ThirdParty are seven capitalised directories, which tells you the project predates most lowercase conventions and has kept them. Two entries do not belong to a WebAssembly runtime at all: WebAssembly.tmLanguage, a TextMate grammar for the WebAssembly text format, and a file named vs-chromium-project.txt, a reference to the browser project WebAssembly was incubated in. The examples directory ships its test material as .wast files, echo, helloworld, tee and trap, alongside a CMakeLists.txt and an embedder directory, and a THIRD-PARTY.md at the root for the dependency notices that LICENSE.txt alone would not cover.
Editorial conclusion
WAVM fits a team embedding WebAssembly in a desktop or server process that controls its own toolchain and wants ahead-of-time compilation instead of an interpreter. It does not fit anyone treating it as a sandbox for hostile modules. Four things to weigh. The README itself says to use operating system processes to isolate untrusted WebAssembly, and names Spectre variant 2 as an attack the design does not defend against, so the VM boundary is a correctness boundary rather than a trust boundary. The release tags are nightlies carrying dates, with a four year hole between May 2022 and April 2026, so pinning a date is the only reproducibility available. The build image targets Ubuntu 18.04 and LLVM 6, which tells you the floor for the compiler you need. And the feature list names proposals without revision numbers, so verify each extension against the documentation before depending on it.
Frequently asked questions
What is WAVM and what is it for?
A WebAssembly virtual machine designed for non-browser applications, written in portable C and C++, which uses LLVM to compile WebAssembly to machine code with close to native performance. It supports WebAssembly 1.0 plus proposed extensions including WASI, 128-bit SIMD, threads, bulk memory and exception handling.
Is WAVM safe for running untrusted WebAssembly?
The README says WAVM prevents WebAssembly code from accessing state outside the virtual machine or calling native code that was not explicitly linked, but also states that it is vulnerable to some side-channel attacks such as Spectre variant 2, that guarding against all of them is impractical, and that you should use another form of isolation such as OS processes.
Does WAVM run on 32-bit systems?
The runtime requires a 64-bit virtual address space and so is not portable to 32-bit hosts. The assembler and disassembler do work on 32-bit hosts, so modules can still be built and inspected there.
Which platforms does WAVM support and test?
It is tested on and fully supports x86-64 and AArch64 on Windows, macOS and Linux, with all six combinations tested in CI. It is designed to run on any POSIX-compatible system but is not routinely tested on other systems, and there is a portability matrix page in the documentation.
How are WAVM releases tagged?
By nightly tags carrying dates, the newest being nightly/2026-04-05, with the two before it dated 2022-05-14 and 2022-05-03. No versioned releases appear in the list, and a VERSION file sits at the repository root.
What is inside the WAVM development container image?
The Dockerfile starts from ubuntu:18.04, installs build tools including llvm-6.0, cmake, ninja-build and zlib1g-dev, copies the source into /code, configures with cmake -G Ninja using the RelWithDebInfo build type, runs ninja, and ends with a bash shell as the default command.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/wavm-wavm)Star history chart for your README
[](https://hysenlabs.com/projects/wavm-wavm)Was this useful?