logo

emscripten-core/emscripten

Emscripten: An LLVM-to-WebAssembly Compiler

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

emscripten-core/emscripten has 27k+ stars and 3.5k+ forks on GitHub, is written in C++, and was last pushed on Oct 15, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 5 hours ago
Type:FrameworkCategory(s):Runtimes & WebAssemblyProgramming Languages & CompilersLanguages & Runtimes
Added to GitGenius on September 2nd, 2026
Created on February 12th, 2011
Open Issues & Pull Requests: 2,517 (-3)
GitHub issues: Enabled
Number of forks: 3,569
Total Stargazers: 27,713 (+2)
Total Subscribers: 573 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.3 hours
Mean response time: 25.3 days
90th percentile: 7.7 days
Tracked items: 1,325

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Maintainer activity

9 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

Around half of the issues opened in the past year never receive a reply. 73% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "embind" is answered fastest, typically in about 12 hours, while "flaky test" waits about 2 months. 62% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 4% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 573
New in 7 days: 12
Closed in 7 days: 7
Avg open age: 643 days
Stale 30+ days: 518
Stale 90+ days: 472

Recent activity

Opened in 7 days: 12
Closed in 7 days: 5
Comments in 7 days: 21
Events in 7 days: 38

Top labels

  • webgpu (42)
  • embind (40)
  • help wanted (27)
  • good first bug (19)
  • flaky test (18)
  • wontfix (18)
  • wasmfs (12)
  • deprecation (6)

Most active issues this week

Sign in to see which issues are moving.
Sign in
Explore full issue details

Detailed Description

Emscripten is an LLVM-to-WebAssembly compiler that transforms C and C++ code into WebAssembly modules executable in browsers, Node.js, and standalone wasm runtimes.

The tool solves the problem of running native C and C++ applications on the Web by compiling through LLVM and Binaryen to produce WebAssembly output. It provides Web support for established portable APIs such as OpenGL and SDL2, enabling complex graphical applications originally written for desktop platforms to run in browser environments with minimal modification. The compiler works by accepting C and C++ source code and producing both a WebAssembly module and accompanying JavaScript loader code, which can then be executed directly in web browsers or JavaScript runtimes.

Adoption suits projects that have existing C or C++ codebases and need to run them on the Web without rewriting in JavaScript. It is particularly valuable for graphical applications, game engines, and computationally intensive software that benefit from WebAssembly's performance characteristics. The tool can integrate with other LLVM-based compilers, such as Rust's wasm32-unknown-emscripten target. Installation is available through the official Emscripten SDK for ease of setup, or through manual Git checkout for developers who prefer direct repository access.

The project maintains active continuous integration through CircleCI and Chromium builder infrastructure. Development follows a structured contribution process documented in the repository's contributing guidelines and developer documentation. The tool is distributed under dual licensing with both MIT and University of Illinois/NCSA Open Source licenses, providing flexibility for different project requirements.