WebAssembly/WASI
WebAssembly System Interface
Build with Backblaze B2
SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.
Loading star history...
Where it stands
Rank, growth pace and release cadence relative to everything GStars tracks.
2 releases in the last 90 days, the latest 20 days ago, with 99 contributors on GitHub.
Gained 45% fewer stars in the last 90 days than in the 90 days before.
Use Cases & Benefits
- Defines a modular system interface for WebAssembly to enable standardized interaction with operating system features.
- Provides a stable, extensible API set that supports multiple source languages and enhances portability across environments.
- Use for building secure, portable WebAssembly applications that require OS-level capabilities like file and network access.
- Use for developing cloud-native applications that leverage WebAssembly for sandboxed execution with system interface support.
- Use for creating new WebAssembly APIs by contributing to or extending the WASI modular API proposals.
Should you depend on it?
License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.
License
Other
GitHub could not identify this license; read the LICENSE file before depending on it.
Community files
- README: present
- Contributing guide: present
- Code of conduct: present
Watch-outs
- License not identified by GitHub; read the LICENSE file before depending on it.
General guidance from repository metadata, not legal advice. How we score
From the README
The WebAssembly System Interface (WASI) is a set of APIs for WASI being developed for eventual standardization by the WASI Subgroup, which is a subgroup of the WebAssembly Community Group.
WASI started with launching what is now called Preview 1, an API using the witx IDL, and it is now widely used. Its major influences are POSIX and CloudABI.
WASI Preview 2 is now stable, and is a modular collection of APIs defined with the Wit IDL, and it incorporates many of the lessons learned from Preview 1, including adding support for a wider range of source languages, modularity, a more expressive type system, virtualizability, and more.
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.
If you would like to create a new proposal, get started with our Contributing guide.
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.
Daily snapshots
Stars gained per day, and how forks and open issues moved, from GStars' daily snapshots
Forks
336+10
Open issues
241-16
Compared with peers in Networking
Fastest-growing repositories GStars tracks in this cohort for the week of Nov 1, by 7-day star growth
| Repository | Stars | +7d | Health | Last release |
|---|---|---|---|---|
| superdesigndev/treg | 7.2K | +656 | 45 | — |
| MHSanaei/3x-ui | 49.4K | +522 | 53 | 134 days ago |
| netbirdio/netbird | 30.7K | +399 | 65 | 7 days ago |
| tailscale/tailscale | 38.7K | +378 | 65 | 3 days ago |
| caddyserver/caddy | 78.8K | +267 | 60 | 1 day ago |
| WebAssembly/WASI | 5.8K | — | 64 | 20 days ago |
| Category median | 38.7K | +399 | 60 | — |
Discover Repositories
Search across tracked repositories by name or description