microsoft/monaco-editor

A browser based code editor

Owned by Microsoft

View on GitHub ↗Jump to charts ↓

microsoft/monaco-editor has 46k+ stars and 4k+ forks on GitHub, is written in JavaScript, and was last pushed on Oct 13, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 20 minutes ago
Added to GitGenius on August 31st, 2026
Created on June 7th, 2016
Open Issues & Pull Requests: 885 (+1)
GitHub issues: Enabled
Number of forks: 4,155
Total Stargazers: 46,873 (+0)
Total Subscribers: 544 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.7 days
Mean response time: 80.7 days
90th percentile: 240.6 days
Tracked items: 450

Maintainer activity

20 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 is counted.

How this project is maintained

Roughly one issue in four opened in the past year never receives a reply. 97% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "typescript" is answered fastest, typically in about 3 days, while "confirmed" waits about 4 months. 57% of tracked open issues have had no activity in three months. Only 26% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 434
New in 7 days: 5
Closed in 7 days: 0
Avg open age: 761 days
Stale 30+ days: 398
Stale 90+ days: 356

Recent activity

Opened in 7 days: 4
Closed in 7 days: 0
Comments in 7 days: 8
Events in 7 days: 19

Top labels

  • feature-request (130)
  • bug (122)
  • accessibility (23)
  • editor-core (21)
  • help wanted (21)
  • verified (21)
  • confirmed (18)
  • typescript (18)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Monaco Editor is a browser-based code editor that brings the fully featured editing capabilities of VS Code to web applications.

The editor solves the problem of embedding a production-grade code editor in web applications without requiring users to install desktop software. It centers on a model-view architecture where models represent file content and track edit history, while editors provide the user-facing view attached to the DOM. Providers deliver smart features like code completion and hover information, often mapping to language server protocol capabilities. The tool supports multiple languages through localization via nls script files and offers both ESM and AMD builds, though AMD support is deprecated.

Developers should choose this tool when building web-based IDEs, collaborative editing platforms, or any application requiring sophisticated code editing with language-aware features. The interactive playground provides the best way to explore supported features and test different versions before integration. The project suits scenarios where you need to represent content as a virtual file system with proper URIs, since some smart features like TypeScript import resolution depend on correct model URIs. The tool is particularly valuable for teams already familiar with VS Code, as it shares the same underlying editor.

The project maintains active development with regular updates to keep pace with VS Code's evolution. The codebase demonstrates careful attention to API stability, with the monaco.d.ts file explicitly versioned while other internals are treated as private and subject to change. The team provides comprehensive documentation covering core concepts like models, URIs, editors, providers, and the disposal pattern for resource cleanup. Development activity shows responsiveness to the playground as a primary learning resource and emphasis on backwards compatibility considerations during deprecation cycles.