# Bytecode Alliance Welcome to the Bytecode Alliance This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## An Update on WAMR and the Bytecode Alliance DevFeed: [An Update on WAMR and the Bytecode Alliance]() Original publisher: [Read original article]() Author: The Bytecode Alliance Published: 2026-07-21T00:00:00Z Content type: news Language: en Sources: [Bytecode Alliance]() Topics: [WebAssembly](), [Development]() Tags: [community](), [development](), [news](), [project](), [update](), [webassembly]() ### AI overview The WebAssembly Micro Runtime (WAMR) will continue development independently of the Bytecode Alliance after the organizations concluded that the project has distinct goals and direction. ### Source excerpt We're writing to share some news about the future of the Bytecode Alliance and the WebAssembly Micro Runtime (WAMR). ## GC and Exceptions in Wasmtime DevFeed: [GC and Exceptions in Wasmtime]() Original publisher: [Read original article]() Author: Nick Fitzgerald Published: 2026-07-20T00:00:00Z Content type: release Language: en Sources: [Bytecode Alliance]() Topics: [WebAssembly](), [wasm](), [Exception](), [toolchains]() Tags: [compilation](), [exceptions](), [release](), [toolchains](), [wasm](), [webassembly]() ### AI overview Wasmtime 47 enables the Wasm GC and exceptions proposals by default. The article explains how Wasm GC supports languages with object-and-reference data models by letting the runtime manage types and lifetimes, while the exceptions proposal provides more efficient exception handling for WebAssembly compilation targets. ### Source excerpt The Wasm GC and exceptions proposals are both enabled by default in today's Wasmtime 47 release! We are excited to help bring more languages to WebAssembly and everywhere that Wasmtime runs. Getting to this point involved large Wasmtime changes and represents the culmination of years of engineering effort. ## WASI 0.3 Launched DevFeed: [WASI 0.3 Launched]() Original publisher: [Read original article]() Author: \["Bailey Hayes", "Yosh Wuyts"\] Published: 2026-06-11T00:00:00Z Content type: release Language: en Sources: [Bytecode Alliance]() Topics: [WebAssembly](), [toolchain]() Tags: [async](), [component](), [components](), [native](), [support](), [toolchain](), [wasi](), [webassembly]() ### AI overview WASI 0.3.0 has been ratified as a stable specification. It rebases WASI on the WebAssembly Component Model's native async primitives, making most changes from WASI 0.2 mechanical and simplifying interface signatures. Runtime and toolchain support is beginning to land. ### Source excerpt WASI 0.3 is official, and async is now native to WebAssembly Components. The WASI Subgroup voted to ratify WASI 0.3.0, rebasing WASI onto the WebAssembly Component Model's async primitives. The 0.3.0 specification is now stable, and runtime and toolchain support is landing now. ## The Road to Component Model 1.0 DevFeed: [The Road to Component Model 1.0]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-06-08T00:00:00Z Content type: article Language: en Sources: [Bytecode Alliance]() Topics: [WebAssembly](), [wasm](), [browser]() Tags: [apis](), [architecture](), [async](), [binaries](), [browser](), [compatibility](), [interfaces](), [polyfill](), [production](), [wasi](), [wasm](), [webassembly]() ### AI overview This article explains the path toward a stable, formally specified WebAssembly Component Model 1.0. It reviews how the Component Model and WASI relate, describes the Component Model as a foundational layer with WASI providing system-resource interfaces, and notes that both are already used in production while their specifications continue to evolve. ### Source excerpt WASI P3 is almost here, bringing native async support to the WebAssembly System Interface (WASI) and Component Model. In this post, we're looking to the next big milestone: a stable, formally specified Component Model 1.0. At February's Bytecode Alliance Plumbers Summit, Luke Wagner and Alex Crichton gave a preview of what the path to a stable 1.0 actually looks like. At Wasm I/O 2026 in Barcelona in March, Luke expanded on that vision. So let's take a look at where the Component Model is heading. ## Endive and the Next Chapter of WebAssembly on the JVM DevFeed: [Endive and the Next Chapter of WebAssembly on the JVM]() Original publisher: [Read original article]() Author: Andrea Peruffo Published: 2026-05-26T00:00:00Z Content type: release Language: en Sources: [Bytecode Alliance]() Topics: [WebAssembly](), [Java](), [Compiler](), [Open Source]() Tags: [announcement](), [compiler](), [fork](), [java](), [jvm](), [open-source](), [webassembly]() ### AI overview Bytecode Alliance announces Endive, a fork of Chicory and a hosted project for running WebAssembly on the JVM. The project aims to let Java developers embed, package, test, and deploy Wasm modules through familiar Java workflows, while integrating the experimental Redline compiler for native machine-code compilation. ### Source excerpt Announcement: Endive begins In September 2023, a small group of contributors set out to answer a simple question: can WebAssembly run on the JVM with zero native dependencies? The project they built, Chicory, proved it could. Within two years it was powering JRuby's Prism parser, a pure-Java SQLite driver, an embedded PostgreSQL, a pure-Java QuickJs runtime, TrinoDB Python UDFs, and many more. What started as an experiment became infrastructure. ## How Wasm components enable pluggable tooling through interposition DevFeed: [How Wasm components enable pluggable tooling through interposition]() Original publisher: [Read original article]() Author: Elizabeth Gilbert Published: 2026-05-14T00:00:00Z Content type: article Language: en Sources: [Bytecode Alliance]() Topics: [wasm](), [Architecture & Design](), [Tooling]() Tags: [architecture](), [modularity](), [services](), [tooling](), [wasm](), [wasm-components]() ### AI overview The article explains how WebAssembly components can support pluggable HTTP middleware through component composition, service chaining, and interposition. It describes in-process communication between components whose imports and exports agree, including fan-in service topologies and chains of handlers for cross-cutting request and response processing. ### Source excerpt And how the splicer framework makes it tractable at any interface edge. ## Wasmtime's April 9, 2026 Security Advisories DevFeed: [Wasmtime's April 9, 2026 Security Advisories]() Original publisher: [Read original article]() Author: The Wasmtime Project Maintainers Published: 2026-04-09T00:00:00Z Content type: news Language: en Sources: [Bytecode Alliance]() Topics: [Security](), [Vulnerabilities](), [releases](), [Open Source](), [Rust](), [WebAssembly](), [Machine Learning, Security Attacks](), [Mozilla]() Tags: [2026](), [attacks](), [audit](), [fuzzing](), [llm](), [mozilla](), [open-source](), [release](), [releases](), [rust](), [security](), [vulnerabilities](), [webassembly]() ### AI overview The Wasmtime team released versions 43.0.1, 42.0.2, 36.0.7, and 24.0.7 with fixes for 12 security advisories, including two rated Critical. The team says 11 advisories were found using new LLM-based tools and recommends that users upgrade. ### Source excerpt A new world for security-critical projects ## Five ways of looking at Jco, Part 1 DevFeed: [Five ways of looking at Jco, Part 1]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-03-19T00:00:00Z Content type: article Language: en Sources: [Bytecode Alliance]() Topics: [JavaScript](), [wasm](), [WebAssembly](), [Rust]() Tags: [blog](), [javascript](), [js](), [presentation](), [technical](), [wasm](), [webassembly]() ### AI overview This first article in a series explains Jco as a layered architecture for the JavaScript and WebAssembly ecosystem. It introduces the projects involved in building JavaScript WebAssembly components, including StarlingMonkey, componentize-js, Wizer, and Jco's CLI and transpilation capabilities. ### Source excerpt Jco (@bytecodealliance/jco on NPM)is a "multi-tool for the JS WebAssembly ecosystem." At the 2026 Bytecode Alliance Plumbers Summit, Technical Steering Committee member Bailey Hayes put it another way: Jco is "like five projects in one." It's certainly a project with many facets--five big ones, arguably! Recognizing what those facets are, and how they fit together, is the key to understanding why Jco matters beyond the JavaScript ecosystem. In this blog series, we'll draw on Victor Adossi's Plumbers Summit presentation to take an in-depth look at Jco from five different perspectives, in order to better grasp how you can use (and contribute to!) Jco today. There's a lot to unpack here, so in this first post, we'll try to get to grips with Jco as a layered architecture that brings together many pieces of the Wasm and JS ecosystem. ## Our Next Plumbers Summit event - February 25 & 26, 2026 DevFeed: [Our Next Plumbers Summit event - February 25 & 26, 2026]() Original publisher: [Read original article]() Author: David Bryant Published: 2026-02-11T00:00:00Z Content type: news Language: en Sources: [Bytecode Alliance]() Topics: [WebAssembly](), [wasm](), [Maintainers](), [Go Language](), [JavaScript]() Tags: [2026](), [c-plus-plus](), [c-sharp](), [community](), [event](), [go](), [javascript](), [maintainers](), [remote](), [rust](), [summit](), [wasi](), [webassembly]() ### AI overview The Bytecode Alliance announces its next online Plumbers Summit, scheduled for February 25-26, 2026. The event will cover WebAssembly plans, hosted-project developments, Wasm tooling, and collaboration among maintainers, platform developers, and users. ### Source excerpt The Bytecode Alliance is pleased to invite you to the next installment in our ongoing Plumbers Summits event series, each designed to bring our members and community together to collectively contribute to the strategic planning for the upcoming year. Our next event will be held Wednesday and Thursday, February 25 and 26, 2026. This will be an all online event, supporting full remote participation for anyone anywhere, with sessions recorded so they can be watched anytime afterward via our YouTube channel ## 10 Years of Wasm: A Retrospective DevFeed: [10 Years of Wasm: A Retrospective]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-01-22T00:00:00Z Content type: article Language: en Sources: [Bytecode Alliance]() Topics: [wasm](), [WebAssembly](), [Web](), [browser](), [JavaScript]() Tags: [browsers](), [javascript](), [retrospective](), [wasm](), [web](), [webassembly]() ### AI overview A retrospective on WebAssembly's origins, standardization, and adoption over its first ten years. It covers the project's 2015 beginnings, the W3C's 2019 recognition of Wasm as the "fourth language of the web," and its use in web applications, streaming video, game engines, embedded devices, and cloud serverless functions. ### Source excerpt In April of 2015, Luke Wagner made the first commits to a new repository called WebAssembly/design, adding a high-level design document for a "binary format to serve as a web compilation target."