You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
Pat Hickey e3b4954610
Sync wasi-cli with wit definitions in standards repo (#6806)
1 year ago
.github Remove the implementation of wasi-crypto (#6816) 1 year ago
benches Change preview2 builder methods to use `&mut self` (#6770) 1 year ago
ci Remove the implementation of wasi-crypto (#6816) 1 year ago
cranelift Add support for vector in DataValueExt::int() (#6844) 1 year ago
crates Sync wasi-cli with wit definitions in standards repo (#6806) 1 year ago
docs Minor documentation updates to docs/WASI-tutorial.md (#6839) 1 year ago
examples fixed typo in examples/memory.rs (#5576) 2 years ago
fuzz Fuzzing: Check that Wasm compilation is deterministic (#6704) 1 year ago
scripts Remove the implementation of wasi-crypto (#6816) 1 year ago
src Remove the implementation of wasi-crypto (#6816) 1 year ago
supply-chain Remove the implementation of wasi-crypto (#6816) 1 year ago
tests Add an API to detect precompiled modules/components (#6832) 1 year ago
winch winch: Simplify the MacroAssembler and Assembler interfaces (#6841) 1 year ago
.gitattributes `generated-code.rs` is not itself generated code (#5571) 2 years ago
.gitignore Add cmake compatibility to c-api (#4369) 2 years ago
.gitmodules Remove the implementation of wasi-crypto (#6816) 1 year ago
CODEOWNERS Use GitHub teams as code owners (#6114) 2 years ago
CODE_OF_CONDUCT.md Rename the `master` branch to `main` (#1924) 4 years ago
CONTRIBUTING.md Merge the CONTRIBUTING.md files 5 years ago
Cargo.lock Sync wasi-cli with wit definitions in standards repo (#6806) 1 year ago
Cargo.toml Sync wasi-cli with wit definitions in standards repo (#6806) 1 year ago
LICENSE Adjust whitespace to match the upstream exception text. 6 years ago
ORG_CODE_OF_CONDUCT.md Make it a Bytecode Alliance project (#549) 5 years ago
README.md Add links to cranelift.dev site. (#6336) 2 years ago
RELEASES.md Update RELEASES.md (#6838) 1 year ago
SECURITY.md Refer to BA security policy (#2912) 4 years ago
build.rs Wasmtime: Add support for Wasm tail calls (#6774) 1 year ago
clippy.toml Merge clippy configs 5 years ago
deny.toml Dependency gardening for Wasmtime (#6731) 1 year ago

README.md

wasmtime

A standalone runtime for WebAssembly

A Bytecode Alliance project

build status zulip chat supported rustc stable Documentation Status

Guide | Contributing | Website | Chat

Installation

The Wasmtime CLI can be installed on Linux and macOS (locally) with a small install script:

curl https://wasmtime.dev/install.sh -sSf | bash

Windows or otherwise interested users can download installers and binaries directly from the GitHub Releases page.

Example

If you've got the Rust compiler installed then you can take some Rust source code:

fn main() {
    println!("Hello, world!");
}

and compile/run it with:

$ rustup target add wasm32-wasi
$ rustc hello.rs --target wasm32-wasi
$ wasmtime hello.wasm
Hello, world!

(Note: make sure you installed Rust using the rustup method in the official instructions above, and do not have a copy of the Rust toolchain installed on your system in some other way as well (e.g. the system package manager). Otherwise, the rustup target add... command may not install the target for the correct copy of Rust.)

Features

  • Fast. Wasmtime is built on the optimizing Cranelift code generator to quickly generate high-quality machine code either at runtime or ahead-of-time. Wasmtime is optimized for efficient instantiation, low-overhead calls between the embedder and wasm, and scalability of concurrent instances.

  • Secure. Wasmtime's development is strongly focused on correctness and security. Building on top of Rust's runtime safety guarantees, each Wasmtime feature goes through careful review and consideration via an RFC process. Once features are designed and implemented, they undergo 24/7 fuzzing donated by Google's OSS Fuzz. As features stabilize they become part of a release, and when things go wrong we have a well-defined security policy in place to quickly mitigate and patch any issues. We follow best practices for defense-in-depth and integrate protections and mitigations for issues like Spectre. Finally, we're working to push the state-of-the-art by collaborating with academic researchers to formally verify critical parts of Wasmtime and Cranelift.

  • Configurable. Wasmtime uses sensible defaults, but can also be configured to provide more fine-grained control over things like CPU and memory consumption. Whether you want to run Wasmtime in a tiny environment or on massive servers with many concurrent instances, we've got you covered.

  • WASI. Wasmtime supports a rich set of APIs for interacting with the host environment through the WASI standard.

  • Standards Compliant. Wasmtime passes the official WebAssembly test suite, implements the official C API of wasm, and implements future proposals to WebAssembly as well. Wasmtime developers are intimately engaged with the WebAssembly standards process all along the way too.

Language Support

You can use Wasmtime from a variety of different languages through embeddings of the implementation.

Languages supported by the Bytecode Alliance:

Languages supported by the community:

Documentation

📚 Read the Wasmtime guide here! 📚

The wasmtime guide is the best starting point to learn about what Wasmtime can do for you or help answer your questions about Wasmtime. If you're curious in contributing to Wasmtime, it can also help you do that!


It's Wasmtime.