|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Wasm3||6,105||9 days ago||1||March 03, 2021||62||mit||C|
|🚀 A fast WebAssembly interpreter and the most universal WASM runtime|
|Wasm Micro Runtime||3,801||a day ago||149||apache-2.0||C|
|WebAssembly Micro Runtime (WAMR)|
|Squirreljme||170||2 days ago||63||gpl-3.0||Java|
|SquirrelJME is a Java ME 8 Virtual Machine for embedded and Internet of Things devices. It has the ultimate goal of being 99.9% compatible with the Java ME standard.|
|Azure IoT connected factory preconfigured solution|
|Embedos||99||3 years ago||1||gpl-2.0|
|EmbedOS - Embedded security testing virtual machine|
|Deeplang||72||3 months ago||12||bsd-3-clause|
|DeepLang is a new language for IoT device programming.|
|Greengo||68||3 years ago||5||April 30, 2019||5||mit||Python|
|Simple YAML-based deployment framework for AWS Greengrass.|
|Warduino||60||5 days ago||58||mpl-2.0||Shell|
|A dynamic WebAssembly VM for embedded systems|
|A cross browser, electron-less helper, for IoT projects and standalone applications.|
|Czl||31||4 years ago||2||C|
A fast WebAssembly interpreter and the most universal WASM runtime.
Based on CoreMark 1.0 and independent benchmarks. Your mileage may vary.
Here's a small getting started guide. Click here to start:
Please follow the installation instructions.
Wasm3 can also be used as a library for:
Arduino, PlatformIO, Particle QuickJS
wasm3 passes the WebAssembly spec testsuite and is able to run many
Minimum useful system requirements: ~64Kb for code and ~10Kb RAM
wasm3 runs on a wide range of architectures (
ARC32, ...) and platforms:
|Webassembly Core Proposals||Extra|
|Import/Export of Mutable Globals||Structured execution tracing|
|Non-trapping float-to-int conversions||Big-Endian systems support|
|Sign-extension operators||Wasm and WASI self-hosting|
|Bulk memory operations (partial support)||Linear memory limit (< 64KiB)|
|Tail call optimization|
Why use a "slow interpreter" versus a "fast JIT"?
In many situations, speed is not the main concern. Runtime executable size, memory usage, startup latency can be improved with the interpreter approach. Portability and security are much easier to achieve and maintain. Additionally, development impedance is much lower. A simple library like Wasm3 is easy to compile and integrate into an existing project. (Wasm3 builds in a just few seconds). Finally, on some platforms (i.e. iOS and WebAssembly itself) you can't generate executable code pages in runtime, so JIT is unavailable.
Why would you want to run WASM on embedded devices?
Wasm3 started as a research project and remains so by many means. Evaluating the engine in different environments is part of the research. Given that we have
... running on MCUs,
WebAssembly is actually a promising alternative. It provides toolchain decoupling as well as a completely sandboxed, well-defined, predictable environment. Among practical use cases we can list
plugin systems, running
smart contracts, etc.
Build and Development instructions
Testing & Fuzzing
Awesome WebAssembly Tools
This project is released under The MIT License (MIT)