wazero/wazero

wazero: the zero dependency WebAssembly runtime for Go developers

View on GitHub ↗Jump to charts ↓Open shareable report →

wazero/wazero has 6k+ stars and 350+ forks on GitHub, is written in Go, and was last pushed on Sep 28, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 4 hours ago
Type:Library / SDKCategory(s):Runtimes & WebAssemblyLanguages & Runtimes
Added to GitGenius on July 23rd, 2025
Created on May 4th, 2020
Open Issues & Pull Requests: 52 (+0)
GitHub issues: Enabled
Number of forks: 363
Total Stargazers: 6,421 (+3)
Total Subscribers: 42 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.8 hours
Mean response time: 67.5 days
90th percentile: 320.4 days
Tracked items: 136

Maintainer activity

2 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

How this project is maintained

About 17% of issues opened in the past year have never received a reply. 97% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 57% of issues opened in the past year have been closed. Three people close 88% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 33
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 280 days
Stale 30+ days: 26
Stale 90+ days: 21

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 1
Events in 7 days: 5

Top labels

  • bug (91)
  • enhancement (69)
  • question (15)
  • help wanted (8)
  • tech debt (5)
  • good first issue (3)
  • documentation (1)
  • duplicate (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Wazero is a WebAssembly (Wasm) runtime designed for embedding within Go applications, prioritizing security, portability, and performance. Developed by Tetra Technologies, it aims to provide a robust and efficient way to execute Wasm modules directly within Go without relying on external processes or virtual machines. Unlike some other Wasm runtimes, Wazero is specifically tailored for server-side applications and focuses on minimizing overhead and maximizing control for the host Go application.

At its core, Wazero leverages the WebAssembly System Interface (WASI) to provide a standardized interface between the Wasm module and the host environment. This allows Wasm modules to interact with system resources like files, networking, and clocks in a secure and portable manner. Wazero’s implementation of WASI is carefully designed to be configurable, allowing developers to precisely control which capabilities are exposed to the Wasm module, significantly enhancing security. It doesn’t aim for full WASI compatibility initially, instead focusing on a subset relevant to server-side use cases, and expanding based on demand.

A key feature of Wazero is its compiled nature. It's written entirely in Go and compiles directly into native machine code, avoiding the performance penalties associated with interpreters or just-in-time (JIT) compilation in many scenarios. This results in faster startup times and more predictable performance, crucial for latency-sensitive applications. Furthermore, Wazero’s architecture is designed to be lightweight and minimize memory footprint, making it suitable for resource-constrained environments. It avoids the need for a separate VM process, reducing overhead and simplifying deployment.

The repository provides a comprehensive API for interacting with Wasm modules. This includes functionalities for loading Wasm bytecode from various sources (files, byte arrays, etc.), instantiating modules, exporting functions, and calling those functions from Go code. Wazero also supports passing data between Go and Wasm modules efficiently, using Go slices and structs that can be directly mapped to Wasm memory. Error handling is robust, providing detailed information about any issues encountered during module loading or execution.

Beyond the core runtime, the repository includes several examples and tools demonstrating Wazero’s capabilities. These examples cover common use cases such as image processing, data compression, and running serverless functions. The repository also contains extensive documentation, including API references, tutorials, and guides on security best practices. A significant component is the `wazero/sys` package, which provides a platform-agnostic interface for interacting with the underlying operating system, enhancing portability. The project is actively maintained and welcomes contributions from the community, with a clear roadmap for future development focusing on WASI compatibility, performance optimizations, and expanded tooling.