tc39/ecma262

Status, process, and documents for ECMA-262

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 43 minutes ago
Added to GitGenius on September 3rd, 2026
Created on April 9th, 2014
Open Issues & Pull Requests: 477 (+0)
GitHub issues: Enabled
Number of forks: 1,433
Total Stargazers: 15,687 (+0)
Total Subscribers: 932 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.9 hours
Mean response time: 94.7 days
90th percentile: 117.5 days
Tracked items: 193

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 28% of open issues come from outside the core team — the tracker reads mainly as internal planning. Only 9% of issues opened in the past year have been closed. Three people close 69% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 72
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 587 days
Stale 30+ days: 64
Stale 90+ days: 55

Recent activity

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

Top labels

  • invalid (26)
  • editorial change (16)
  • establishes editorial conventions (15)
  • spec bug (10)
  • question (9)
  • good first issue (8)
  • web reality (5)
  • unicode (4)

Detailed Description

ECMA-262 is the official specification repository for the ECMAScript language standard.

The repository maintains the authoritative source document for ECMAScript, the standardized specification that defines the JavaScript language. The specification is written in a source format that is processed to generate a human-readable version accessible online. Developers and standards committee members can explore the specification's evolution through its version history using searchable tools. The repository serves as the central coordination point for the TC39 standards committee's work on the language.

This repository is essential for anyone involved in JavaScript language development, including engine implementers, tool authors, and those proposing new language features. It functions as both the living specification document and the process hub for standardization. The TC39 process for language proposals is documented here, with proposals tracked across multiple stages from initial ideas through finished features. Contributors interested in proposing new language features should consult the contribution guidelines provided in the repository.

Development of the specification follows a structured workflow. Contributors clone the repository and use npm commands to build the specification locally or set up continuous builds during development. The build system generates output in a designated directory, with cleanup tools available for resetting the build environment. The project maintains active community engagement through dedicated discussion forums and chat channels for ECMAScript-related questions and collaboration.