[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-6492":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":25,"hasPages":23,"topics":26,"createdAt":10,"pushedAt":10,"updatedAt":41,"readmeContent":42,"aiSummary":43,"trendingCount":16,"starSnapshotCount":16,"syncStatus":17,"lastSyncTime":44,"discoverSource":45},6492,"wasm-micro-runtime","bytecodealliance\u002Fwasm-micro-runtime","bytecodealliance","WebAssembly Micro Runtime (WAMR)","",null,"C",5978,814,103,535,0,2,15,63,13,39.73,"Apache License 2.0",false,"main",true,[27,28,29,30,31,32,33,34,35,36,37,38,39,40],"aot","assembly-script","embedded","interpreter","iot","jit","pthread","runtime","sgx","wasi-nn","wasi-threads","wasm","wasm-socket","webassembly","2026-06-12 02:01:25","# WebAssembly Micro Runtime\n\n\n**A [Bytecode Alliance][BA] project**\n\n[BA]: https:\u002F\u002Fbytecodealliance.org\u002F\n\n**[Guide](https:\u002F\u002Fwamr.gitbook.io\u002F)**  **[Website](https:\u002F\u002Fbytecodealliance.github.io\u002Fwamr.dev)**  **[Chat](https:\u002F\u002Fbytecodealliance.zulipchat.com\u002F#narrow\u002Fstream\u002F290350-wamr)**\n\n[Build WAMR](.\u002Fdoc\u002Fbuild_wamr.md) | [Build AOT Compiler](.\u002Fwamr-compiler\u002FREADME.md) | [Embed WAMR](.\u002Fdoc\u002Fembed_wamr.md) | [Export Native API](.\u002Fdoc\u002Fexport_native_api.md) | [Build Wasm Apps](.\u002Fdoc\u002Fbuild_wasm_app.md) | [Samples](.\u002Fsamples\u002FREADME.md)\n\nWebAssembly Micro Runtime (WAMR) is a lightweight standalone WebAssembly (Wasm) runtime with small footprint, high performance and highly configurable features for applications cross from embedded, IoT, edge to Trusted Execution Environment (TEE), smart contract, cloud native and so on. It includes a few parts as below:\n- [**VMcore**](.\u002Fcore\u002Fiwasm\u002F): A set of runtime libraries for loading and running Wasm modules. It supports rich running modes including interpreter, Ahead-of-Time compilation(AoT) and Just-in-Time compilation (JIT). WAMR supports two JIT tiers - Fast JIT, LLVM JIT, and dynamic tier-up from Fast JIT to LLVM JIT.\n- [**iwasm**](.\u002Fproduct-mini\u002F): The executable binary built with WAMR VMcore which supports WASI and command line interface.\n- [**wamrc**](.\u002Fwamr-compiler\u002F): The AOT compiler to compile Wasm file into AOT file\n- Useful components and tools for building real solutions with WAMR vmcore:\n  - [App-framework](https:\u002F\u002Fgithub.com\u002Fbytecodealliance\u002Fwamr-app-framework\u002Fblob\u002Fmain\u002Fapp-framework\u002FREADME.md): A framework for supporting APIs for the Wasm applications\n  - [App-manager](https:\u002F\u002Fgithub.com\u002Fbytecodealliance\u002Fwamr-app-framework\u002Fblob\u002Fmain\u002Fapp-mgr\u002FREADME.md): A framework for dynamical loading the Wasm module remotely\n  - [WAMR-IDE](.\u002Ftest-tools\u002Fwamr-ide): An experimental VSCode extension for developping WebAssembly applications with C\u002FC++\n\n\n### Key features\n- Full compliant to the W3C Wasm MVP\n- Small runtime binary size (core vmlib on cortex-m4f with tail-call\u002Fbulk memory\u002Fshared memory support, text size from bloaty)\n  * ~58.9K for fast interpreter\n  * ~56.3K for classic interpreter\n  * ~29.4K for aot runtime\n  * ~21.4K for libc-wasi library\n  * ~3.7K for libc-builtin library\n- Near to native speed by AOT and JIT\n- Self-implemented AOT module loader to enable AOT working on Linux, Windows, MacOS, Android, SGX and MCU systems\n- Choices of Wasm application libc support: the built-in libc subset for the embedded environment or [WASI](https:\u002F\u002Fgithub.com\u002FWebAssembly\u002FWASI) for the standard libc\n- [The simple C APIs to embed WAMR into host environment](.\u002Fdoc\u002Fembed_wamr.md), see [how to integrate WAMR](.\u002Fdoc\u002Fembed_wamr.md) and the [API list](.\u002Fcore\u002Fiwasm\u002Finclude\u002Fwasm_export.h)\n- [The mechanism to export native APIs to Wasm applications](.\u002Fdoc\u002Fexport_native_api.md), see [how to register native APIs](.\u002Fdoc\u002Fexport_native_api.md)\n- [Multiple modules as dependencies](.\u002Fdoc\u002Fmulti_module.md), ref to [document](.\u002Fdoc\u002Fmulti_module.md) and [sample](samples\u002Fmulti-module)\n- [Multi-thread, pthread APIs and thread management](.\u002Fdoc\u002Fpthread_library.md), ref to [document](.\u002Fdoc\u002Fpthread_library.md) and [sample](samples\u002Fmulti-thread)\n- [wasi-threads](.\u002Fdoc\u002Fpthread_impls.md#wasi-threads-new), ref to [document](.\u002Fdoc\u002Fpthread_impls.md#wasi-threads-new) and [sample](samples\u002Fwasi-threads)\n- [Linux SGX (Intel Software Guard Extension) support](.\u002Fdoc\u002Flinux_sgx.md), ref to [document](.\u002Fdoc\u002Flinux_sgx.md)\n- [Source debugging support](.\u002Fdoc\u002Fsource_debugging.md), ref to [document](.\u002Fdoc\u002Fsource_debugging.md)\n- [XIP (Execution In Place) support](.\u002Fdoc\u002Fxip.md), ref to [document](.\u002Fdoc\u002Fxip.md)\n- [Berkeley\u002FPosix Socket support](.\u002Fdoc\u002Fsocket_api.md), ref to [document](.\u002Fdoc\u002Fsocket_api.md) and [sample](.\u002Fsamples\u002Fsocket-api)\n- [Multi-tier JIT](.\u002Fproduct-mini#linux) and [Running mode control](https:\u002F\u002Fbytecodealliance.github.io\u002Fwamr.dev\u002Fblog\u002Fintroduction-to-wamr-running-modes\u002F)\n- Language bindings: [Go](.\u002Flanguage-bindings\u002Fgo\u002FREADME.md), [Python](.\u002Flanguage-bindings\u002Fpython\u002FREADME.md), [Rust](.\u002Flanguage-bindings\u002Frust\u002FREADME.md)\n\n### Wasm post-MVP features\n- [wasm-c-api](https:\u002F\u002Fgithub.com\u002FWebAssembly\u002Fwasm-c-api), ref to [document](doc\u002Fwasm_c_api.md) and [sample](samples\u002Fwasm-c-api)\n- [128-bit SIMD](https:\u002F\u002Fgithub.com\u002FWebAssembly\u002Fsimd), ref to [samples\u002Fworkload](samples\u002Fworkload)\n- [Reference Types](https:\u002F\u002Fgithub.com\u002FWebAssembly\u002Freference-types), ref to [document](doc\u002Fref_types.md) and [sample](samples\u002Fref-types)\n- [Bulk memory operations](https:\u002F\u002Fgithub.com\u002FWebAssembly\u002Fbulk-memory-operations), [Shared memory](https:\u002F\u002Fgithub.com\u002FWebAssembly\u002Fthreads\u002Fblob\u002Fmain\u002Fproposals\u002Fthreads\u002FOverview.md#shared-linear-memory), [Memory64](https:\u002F\u002Fgithub.com\u002FWebAssembly\u002Fmemory64)\n- [Tail-call](https:\u002F\u002Fgithub.com\u002FWebAssembly\u002Ftail-call), [Garbage Collection](https:\u002F\u002Fgithub.com\u002FWebAssembly\u002Fgc), [Exception Handling](https:\u002F\u002Fgithub.com\u002FWebAssembly\u002Fexception-handling), [Branch Hinting](https:\u002F\u002Fgithub.com\u002FWebAssembly\u002Fbranch-hinting)\n- [Extended Constant Expressions](https:\u002F\u002Fgithub.com\u002FWebAssembly\u002Fextended-const)\n\n### Supported architectures and platforms\nThe WAMR VMcore supports the following architectures:\n- X86-64, X86-32\n- ARM, THUMB (ARMV7 Cortex-M7 and Cortex-A15 are tested)\n- AArch64 (Cortex-A57 and Cortex-A53 are tested)\n- RISCV64, RISCV32 (RISC-V LP64 and RISC-V LP64D are tested)\n- XTENSA, MIPS, ARC\n\nThe following platforms are supported, click each link below for how to build iwasm on that platform. Refer to [WAMR porting guide](.\u002Fdoc\u002Fport_wamr.md) for how to port WAMR to a new platform.\n- [Linux](.\u002Fproduct-mini\u002FREADME.md#linux),  [Linux SGX (Intel Software Guard Extension)](.\u002Fdoc\u002Flinux_sgx.md),  [MacOS](.\u002Fproduct-mini\u002FREADME.md#macos),  [Android](.\u002Fproduct-mini\u002FREADME.md#android), [Windows](.\u002Fproduct-mini\u002FREADME.md#windows), [Windows (MinGW, MSVC)](.\u002Fproduct-mini\u002FREADME.md#mingw)\n- [Zephyr](.\u002Fproduct-mini\u002FREADME.md#zephyr),  [AliOS-Things](.\u002Fproduct-mini\u002FREADME.md#alios-things),  [VxWorks](.\u002Fproduct-mini\u002FREADME.md#vxworks), [NuttX](.\u002Fproduct-mini\u002FREADME.md#nuttx), [RT-Thread](.\u002Fproduct-mini\u002FREADME.md#RT-Thread), [ESP-IDF(FreeRTOS)](.\u002Fproduct-mini\u002FREADME.md#esp-idf)\n\n\n## Getting started\n- [Build VM core](.\u002Fdoc\u002Fbuild_wamr.md) and [Build wamrc AOT compiler](.\u002Fwamr-compiler\u002FREADME.md)\n- [Build iwasm (mini product)](.\u002Fproduct-mini\u002FREADME.md): [Linux](.\u002Fproduct-mini\u002FREADME.md#linux), [SGX](.\u002Fdoc\u002Flinux_sgx.md), [MacOS](.\u002Fproduct-mini\u002FREADME.md#macos) and [Windows](.\u002Fproduct-mini\u002FREADME.md#windows)\n- [Embed into C\u002FC++](.\u002Fdoc\u002Fembed_wamr.md), [Embed into Python](.\u002Flanguage-bindings\u002Fpython), [Embed into Go](.\u002Flanguage-bindings\u002Fgo), [Embed in Rust](.\u002Flanguage-bindings\u002Frust)\n- [Register native APIs for Wasm applications](.\u002Fdoc\u002Fexport_native_api.md)\n- [Build wamrc AOT compiler](.\u002Fwamr-compiler\u002FREADME.md)\n- [Build Wasm applications](.\u002Fdoc\u002Fbuild_wasm_app.md)\n- [Port WAMR to a new platform](.\u002Fdoc\u002Fport_wamr.md)\n- [VS Code development container](.\u002Fdoc\u002Fdevcontainer.md)\n- [Samples](.\u002Fsamples) and [Benchmarks](.\u002Ftests\u002Fbenchmarks)\n- [End-user APIs documentation](https:\u002F\u002Fbytecodealliance.github.io\u002Fwamr.dev\u002Fapis\u002F)\n\n\n### Performance and memory\n- [Blog: The WAMR memory model](https:\u002F\u002Fbytecodealliance.github.io\u002Fwamr.dev\u002Fblog\u002Fthe-wamr-memory-model\u002F)\n- [Blog: Understand WAMR heaps](https:\u002F\u002Fbytecodealliance.github.io\u002Fwamr.dev\u002Fblog\u002Funderstand-the-wamr-heaps\u002F) and [stacks](https:\u002F\u002Fbytecodealliance.github.io\u002Fwamr.dev\u002Fblog\u002Funderstand-the-wamr-stacks\u002F)\n- [Blog: Introduction to WAMR running modes](https:\u002F\u002Fbytecodealliance.github.io\u002Fwamr.dev\u002Fblog\u002Fintroduction-to-wamr-running-modes\u002F)\n- [Memory usage tuning](.\u002Fdoc\u002Fmemory_tune.md): the memory model and how to tune the memory usage\n- [Memory usage profiling](.\u002Fdoc\u002Fbuild_wamr.md#enable-memory-profiling-experiment): how to profile the memory usage\n- [Performance tuning](.\u002Fdoc\u002Fperf_tune.md): how to tune the performance\n- [Benchmarks](.\u002Ftests\u002Fbenchmarks): checkout these links for how to run the benchmarks: [PolyBench](.\u002Ftests\u002Fbenchmarks\u002Fpolybench), [CoreMark](.\u002Ftests\u002Fbenchmarks\u002Fcoremark), [Sightglass](.\u002Ftests\u002Fbenchmarks\u002Fsightglass), [JetStream2](.\u002Ftests\u002Fbenchmarks\u002Fjetstream)\n- [Performance and footprint data](https:\u002F\u002Fgithub.com\u002Fbytecodealliance\u002Fwasm-micro-runtime\u002Fwiki\u002FPerformance): the performance and footprint data\n\n\nProject Technical Steering Committee\n====================================\nThe [WAMR PTSC Charter](.\u002FTSC_Charter.md) governs the operations of the project TSC.\nThe current TSC members:\n- [dongsheng28849455](https:\u002F\u002Fgithub.com\u002Fdongsheng28849455) - **Dongsheng Yan**, \u003Cdongsheng.yan@sony.com>\n- [loganek](https:\u002F\u002Fgithub.com\u002Floganek) - **Marcin Kolny**, \u003Cmkolny@amazon.co.uk>\n- [lum1n0us](https:\u002F\u002Fgithub.com\u002Flum1n0us) - **Liang He**， \u003Cliang.he@intel.com>\n- [no1wudi](https:\u002F\u002Fgithub.com\u002Fno1wudi) **Qi Huang**, \u003Chuangqi3@xiaomi.com>\n- [qinxk-inter](https:\u002F\u002Fgithub.com\u002Fqinxk-inter) - **Xiaokang Qin**， \u003Cxiaokang.qxk@antgroup.com>\n- [ttrenner ](https:\u002F\u002Fgithub.com\u002Fttrenner) - **Trenner, Thomas**， \u003Ctrenner.thomas@siemens.com>\n- [wei-tang](https:\u002F\u002Fgithub.com\u002Fwei-tang) - **Wei Tang**， \u003Ctangwei.tang@antgroup.com>\n- [wenyongh](https:\u002F\u002Fgithub.com\u002Fwenyongh) - **Wenyong Huang**， \u003Cwenyong.huang@intel.com>\n- [woodsmc](https:\u002F\u002Fgithub.com\u002Fwoodsmc) - **Woods, Chris**， \u003Cchris.woods@siemens.com>\n- [xujuntwt95329](https:\u002F\u002Fgithub.com\u002Fxujuntwt95329) - **Jun Xu**， \u003CJun1.Xu@intel.com>\n- [xwang98](https:\u002F\u002Fgithub.com\u002Fxwang98) - **Xin Wang**， \u003Cxin.wang@intel.com> (chair)\n- [yamt](https:\u002F\u002Fgithub.com\u002Fyamt) - **Takashi Yamamoto**, \u003Cyamamoto@midokura.com>\n\n\nLicense\n=======\nWAMR uses the same license as LLVM: the `Apache 2.0 license` with the LLVM\nexception. See the LICENSE file for details. This license allows you to freely\nuse, modify, distribute and sell your own products based on WAMR.\nAny contributions you make will be under the same license.\n\n# More resources\n- [Who use WAMR?](https:\u002F\u002Fgithub.com\u002Fbytecodealliance\u002Fwasm-micro-runtime\u002Fwiki)\n- [WAMR Blogs](https:\u002F\u002Fbytecodealliance.github.io\u002Fwamr.dev\u002Fblog\u002F)\n- [Community news and events](https:\u002F\u002Fbytecodealliance.github.io\u002Fwamr.dev\u002Fevents\u002F)\n- [WAMR TSC meetings](https:\u002F\u002Fgithub.com\u002Fbytecodealliance\u002Fwasm-micro-runtime\u002Fwiki\u002FTSC-meeting-notes)\n","WebAssembly Micro Runtime (WAMR) 是一个轻量级的独立 WebAssembly 运行时，旨在为从嵌入式、物联网到可信执行环境等多种应用场景提供高性能和高度可配置的支持。其核心功能包括支持多种运行模式（解释器、AOT 编译和 JIT 编译），其中 JIT 支持快速 JIT 和 LLVM JIT 两种级别，并能动态升级。WAMR 提供了完整的 W3C Wasm MVP 兼容性，以及极小的二进制文件大小，例如 AOT 运行时仅约 29.4K。此外，它还支持通过简单的 C API 将 WAMR 集成到宿主环境中，并允许向 Wasm 应用程序导出本地 API。适用于需要在资源受限设备上高效运行 WebAssembly 代码的各种场景，如嵌入式系统、IoT 设备、边缘计算及云原生应用等。","2026-06-11 03:07:17","top_language"]