WebAssembly/design

WebAssembly Design Documents

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 10 minutes ago
Added to GitGenius on November 14th, 2024
Created on April 29th, 2015
Open Issues & Pull Requests: 185 (+0)
Number of forks: 710
Total Stargazers: 11,613 (+0)
Total Subscribers: 727 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 81.3 days
Mean response time: 1026.7 days
90th percentile: 2847.3 days
Tracked items: 96

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 82% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 2% of issues opened in the past year have been closed. Three people close 77% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 165
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 1,901 days
Stale 30+ days: 163
Stale 90+ days: 161

Recent activity

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

Top labels

  • binary format (51)
  • JS embedding (34)
  • control flow (26)
  • documentation (22)
  • linear memory (22)
  • clarification (16)
  • imports/exports (16)
  • integer (13)

Most active issues this week

Detailed Description

The webassembly/design repository serves as the central hub for WebAssembly design documentation and community governance.

The repository's primary purpose is to document and discuss the architectural and design decisions underlying WebAssembly, a binary instruction format and execution environment designed for portability across platforms. The design documents address fundamental aspects of the specification including high-level goals, portability semantics, security models, and nondeterminism considerations. The README identifies several documents as relatively current, including WebAssembly High-Level Goals, a Portability guide explaining what portability means in the Wasm context, Design Rationale, the Security model documentation, and a document on Nondeterminism in WebAssembly. The repository acknowledges that some design documents have become outdated and notes ongoing efforts to update them.

GitGenius activity analysis reveals this is an active standardization effort with substantial community engagement. These labels reflect core concerns in making WebAssembly practical for real-world deployment and integration with existing web platforms.

The contributor ecosystem shows concentrated expertise among key maintainers. These connections reflect WebAssembly's role as a cross-platform execution target relevant to multiple programming language communities and development environments.

The repository's classification across multiple domains reflects WebAssembly's multifaceted nature: it functions simultaneously as a specification, a binary format, a bytecode standard, an execution engine architecture, and a platform for achieving portability and performance. The emphasis on standardization, language design, web development, and execution environment concerns demonstrates that the design repository addresses both the technical specification aspects and the broader ecosystem considerations necessary for WebAssembly adoption.

The repository enforces community standards through a Code of Ethics and Professional Conduct, establishing expectations for respectful participation in design discussions. By hosting both the issue tracker for early-stage proposals and a general discussion forum, the repository creates structured pathways for community members to propose features, discuss technical challenges, and reach consensus on design decisions. This dual-track approach allows phase 0 proposals to receive focused technical review while maintaining space for broader architectural questions and community input.