All 22 Dependencies
Every package Wasmer depends on, ranked by repo health score.
Wasmer is a WebAssembly runtime written in Rust that lets you execute WASM modules as fast, sandboxed "containers" instead of full operating-system containers. It ships as both a standalone CLI (`wasmer run`) and an embeddable library with official SDKs for Rust, C/C++, Python, Go, PHP, Ruby, JavaScript, C#, Swift, and more, so the same compiled `.wasm` binary can run identically on Linux, macOS, Windows, or inside a browser tab.
At its core, Wasmer offers three interchangeable compiler backends — Singlepass for near-instant compilation during development, Cranelift as the balanced default, and LLVM for maximum runtime performance — all built behind a shared `Compiler` trait so callers can pick the right trade-off per workload. On top of that sits WASIX, Wasmer's own extension of the WebAssembly System Interface that adds POSIX-style threads, sockets, and process primitives, making it possible to run unmodified networked, multi-threaded C, Rust, or Python programs as WebAssembly rather than only simple, single-threaded command-line tools.
The project doubles as a package ecosystem: `wasmer.toml` manifests and the wasmer.io registry let developers publish and `wasmer run` WASM packages the way `docker run` pulls container images, and `create-exe`/`create-obj` can cross-compile a module into a standalone native executable with no runtime dependency at all. A companion `lib/backend-api` crate talks to Wasmer's hosted registry and "Wasmer Edge" platform for deploying WASM workloads to the edge, but that hosted product is a separate commercial layer — everything in this repository, including every compiler backend and syscall layer, is MIT licensed with no gating.
With over 20,000 GitHub stars, weekly-cadence releases, and a workspace of roughly 35 crates spanning VM internals, compilers, CLI, native bindings, and CI tooling, Wasmer is one of the most mature general-purpose WebAssembly runtimes in the ecosystem.
