https://github.com/WebAssembly/WASI Skip to content Toggle navigation Sign up * Product + Actions Automate any workflow + Packages Host and manage packages + Security Find and fix vulnerabilities + Codespaces Instant dev environments + Copilot Write better code with AI + Code review Manage code changes + Issues Plan and track work + Discussions Collaborate outside of code Explore + All features + Documentation + GitHub Skills + Blog * Solutions For + Enterprise + Teams + Startups + Education By Solution + CI/CD & Automation + DevOps + DevSecOps Resources + Customer Stories + White papers, Ebooks, Webinars + Partners * Open Source + GitHub Sponsors Fund open source developers + The ReadME Project GitHub community articles Repositories + Topics + Trending + Collections * Pricing Search or jump to... Search code, repositories, users, issues, pull requests... Search [ ] Clear Search syntax tips Provide feedback We read every piece of feedback, and take your input very seriously. [ ] [ ] Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly Name [ ] Query [ ] To see all available qualifiers, see our documentation. Cancel Create saved search Sign in Sign up You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. {{ message }} WebAssembly / WASI Public * Notifications * Fork 229 * Star 4k WebAssembly System Interface License View license 4k stars 229 forks Activity Star Notifications * Code * Issues 72 * Pull requests 6 * Discussions * Actions * Projects 0 * Security * Insights More * Code * Issues * Pull requests * Discussions * Actions * Projects * Security * Insights WebAssembly/WASI This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository. main Switch branches/tags [ ] Branches Tags Could not load branches Nothing to show {{ refName }} default View all branches Could not load tags Nothing to show {{ refName }} default View all tags Name already in use A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch? Cancel Create 19 branches 1 tag Code * Local * Codespaces * Clone HTTPS GitHub CLI [https://github.com/W] Use Git or checkout with SVN using the web URL. [gh repo clone WebAss] Work fast with our official CLI. Learn more about the CLI. * Open with GitHub Desktop * Download ZIP Sign In Required Please sign in to use Codespaces. Launching GitHub Desktop If nothing happens, download GitHub Desktop and try again. Launching GitHub Desktop If nothing happens, download GitHub Desktop and try again. Launching Xcode If nothing happens, download Xcode and try again. Launching Visual Studio Code Your codespace will open once ready. There was a problem preparing your codespace, please try again. Latest commit @yamt yamt Document that an out-of-bounds pointer shall trap (#536) ... 4712d49 Jul 28, 2023 Document that an out-of-bounds pointer shall trap (#536) discussion: #505 4712d49 Git stats * 374 commits Files Permalink Failed to load latest commit information. Type Name Latest commit message Commit time docs Add a "Wit in WASI" document. (#517) February 27, 2023 08:50 legacy Document that an out-of-bounds pointer shall trap (#536) July 28, 2023 10:00 Charter.md Improve spelling (#295) July 6, 2020 08:41 Contributing.md Add a "Wit in WASI" document. (#517) February 27, 2023 08:50 LICENSE.md add LICENSE.md, following the W3C CLA Deed, in markdown. (#543) June 23, 2023 14:11 Proposals.md Remove WASI-Data as a proposal (#535) July 10, 2023 12:21 README.md Fix hyperlink (#527) July 10, 2023 12:15 WASI.png Add a simple README and Contributing.md. April 2, 2019 15:56 View code [ ] WebAssembly System Interface Important Note: WASI is in transition Find the APIs Propose a new API WASI High Level Goals WASI Design Principles Capability-based security Interposition Compatibility Portability README.md DOI WebAssembly System Interface WASI The WebAssembly System Interface is not a monolithic standard system interface, but is instead a modular collection of standardized APIs. None of the APIs are required to be implemented to have a compliant runtime. Instead, host environments can choose which APIs make sense for their use cases. --------------------------------------------------------------------- Important Note: WASI is in transition WASI is transitioning away from the witx format and its early experimental ABI. We are transitioning to Interface Types using the wit format and the canonical ABI. All new API proposals should use the new format and the new repo structure that is shown in the proposal template. See the Wit in WASI document for more information about using Wit for WASI proposals. --------------------------------------------------------------------- Find the APIs Development of each API happens in its own repo, which you can access from the proposals list. This repo is for general discussion, as well as documenting how we work and high-level goals. Propose a new API If you would like to create a new proposal, get started with our Contributing guide. WASI High Level Goals (In the spirit of WebAssembly's High-Level Goals.) 1. Define a set of portable, modular, runtime-independent, and WebAssembly-native APIs which can be used by WebAssembly code to interact with the outside world. These APIs preserve the essential sandboxed nature of WebAssembly through a Capability-based API design. 2. Specify and implement incrementally. Start with a Minimum Viable Product (MVP), then adding additional features, prioritized by feedback and experience. 3. Supplement API designs with documentation and tests, and, when feasible, reference implementations which can be shared between wasm engines. 4. Make a great platform: + Work with WebAssembly tool and library authors to help them provide WASI support for their users. + When being WebAssembly-native means the platform isn't directly compatible with existing applications written for other platforms, design to enable compatibility to be provided by tools and libraries. + Allow the overall API to evolve over time; to make changes to API modules that have been standardized, build implementations of them using libraries on top of new API modules to provide compatibility. WASI Design Principles Capability-based security WASI is designed with capability-based security principles, using the facilities provided by the Wasm component model. All access to external resources is provided by capabilities. There are two kinds of capabilities: * Handles, defined in the component-model type system, dynamically identify and provide access to resources. They are unforgeable, meaning there's no way for an instance to acquire access to a handle other than to have another instance explicitly pass one to it. * Link-time capabilities, which are functions which require no handle arguments, are used sparingly, in situations where it's not necessary to identify more than one instance of a resource at runtime. Link-time capabilities are interposable, so they are still refusable in a capability-based security sense. WASI has no ambient authorities, meaning that there are no global namespaces at runtime, and no global functions at link time. Note that this is a different sense of "capability" than Linux capabilities or the withdrawn POSIX capabilities, which are per-process rather than per-resource. Interposition Interposition in the context of WASI interfaces is the ability for a Webassembly instance to implement a given WASI interface, and for a consumer WebAssembly instance to be able to use this implementation transparently. This can be used to adapt or attenuate the functionality of a WASI API without changing the code using it. Component model interfaces always support link-time interposition. While WASI APIs are often implemented in hosts, they can also be implemented in Wasm, which may itself be a wrapper around the host. This may be used to implement attenuation, providing filtered access to the underlying host-provided functionality. Interposition is sometimes referred to as "virtualization", however we use "interposition" here because the word "virtualization" has several related meanings. Compatibility Compatibility with existing applications and libraries, as well as existing host platforms, is important, but will sometimes be in conflict with overall API cleanliness, safety, performance, or portability. Where practical, WASI seeks to keep the WASI API itself free of compatibility concerns, and provides compatibility through libraries, such as WASI libc, and tools. This way, applications which don't require compatibility for compatibility's sake aren't burdened by it. Portability Portability is important to WASI, however the meaning of portability will be specific to each API. WASI's modular nature means that engines don't need to implement every API in WASI, so we don't need to exclude APIs just because some host environments can't implement them. We prefer APIs which can run across a wide variety of engines when feasible, but we'll ultimately decide whether something is "portable enough" on an API-by-API basis. About WebAssembly System Interface Resources Readme License View license Code of conduct Code of conduct Activity Stars 4k stars Watchers 197 watching Forks 229 forks Report repository Releases 1 tags Packages 0 No packages published Contributors 53 * @sunfishcode * @pchickey * @linclark * @alexcrichton * @abrown * @sbc100 * @cjihrig * @igrep * @peterhuene * @cratelyn * @joshtriplett + 42 contributors Languages * Rust 64.5% * HTML 35.4% * Shell 0.1% Footer (c) 2023 GitHub, Inc. Footer navigation * Terms * Privacy * Security * Status * Docs * Contact GitHub * Pricing * API * Training * Blog * About You can't perform that action at this time.