swc-project/swc

Rust-based platform for the Web

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

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on January 29th, 2026
Created on December 22nd, 2017
Open Issues & Pull Requests: 396 (+0)
GitHub issues: Enabled
Number of forks: 1,570
Total Stargazers: 34,210 (+1)
Total Subscribers: 180 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.0 hours
Mean response time: 50.2 days
90th percentile: 56.9 days
Tracked items: 1,552

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 7, 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

About 4% of issues opened in the past year have never received a reply. 71% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 24% of tracked open issues have had no activity in three months. 88% of issues opened in the past year have been closed, leaving a working backlog. Three people close 96% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 225
New in 7 days: 7
Closed in 7 days: 7
Avg open age: 699 days
Stale 30+ days: 212
Stale 90+ days: 187

Recent activity

Opened in 7 days: 6
Closed in 7 days: 6
Comments in 7 days: 1
Events in 7 days: 13

Top labels

  • C-bug (1,771)
  • enhancement (247)
  • invalid link (72)
  • Labor0 (32)
  • A: plugin (22)
  • good first issue (20)
  • A: ES minifier (16)
  • invalid (16)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

SWC is a Rust-based compiler for TypeScript and JavaScript designed to accelerate web development. The project's name stands for Speedy Web Compiler, and it functions as a dual-purpose library accessible to both Rust developers and JavaScript users. For Rust users, the primary entry point is the parser module documented in rustdoc, while JavaScript users access SWC through npm packages like @swc/core and can reference the project's website documentation for integration guidance.

The repository is classified across multiple domains including Web Compiler, JavaScript, TypeScript, Bundler, Minifier, Transformer, and Toolchain categories. It covers the full spectrum of ECMAScript and TypeScript compilation needs, with a strong emphasis on performance optimization. The project maintains compatibility with Node v10 and above for usage, though development requires Node v20 or later. For Rust users, the minimum supported Rust version is 1.73.

SWC's development activity shows significant engagement from the open-source community.

GitGenius identifies shared contributors with microsoft/vscode, microsoft/typescript, and denoland/deno, indicating deep integration within the broader TypeScript and JavaScript ecosystem. This cross-project involvement suggests SWC's role as a foundational tool for these major platforms.

The project distributes through multiple channels including npm packages tracked by download metrics and Rust crates available on crates.io, particularly swc_ecma_parser. SWC emphasizes reliability for Rust users through a guarantee that selecting the latest version of each crate will result in a working configuration. The project provides comparison documentation with Babel to help users understand feature parity and migration paths, along with benchmark results demonstrating performance characteristics.

SWC is maintained as a community-driven project by volunteers and accepts contributions through GitHub. Development support is coordinated through Discord and GitHub Discussions, with the project also accepting financial sponsorship through Open Collective to sustain ongoing development efforts.