mdn/browser-compat-data

Browser compatibility data for Web technologies as displayed on MDN

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 36 minutes ago
Added to GitGenius on September 11th, 2026
Created on March 29th, 2016
Open Issues & Pull Requests: 395 (+0)
GitHub issues: Enabled
Number of forks: 2,628
Total Stargazers: 5,747 (+0)
Total Subscribers: 282 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.8 days
Mean response time: 178.0 days
90th percentile: 769.0 days
Tracked items: 1,221

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 91% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "spam" is answered fastest, typically in about 2 hours, while "browser:multiple" waits about 8 weeks. 23% of tracked open issues have had no activity in three months. Only 9% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 330
New in 7 days: 22
Closed in 7 days: 20
Avg open age: 790 days
Stale 30+ days: 292
Stale 90+ days: 89

Recent activity

Opened in 7 days: 20
Closed in 7 days: 18
Comments in 7 days: 17
Events in 7 days: 96

Top labels

  • spam (771)
  • data:api (445)
  • needs triage (314)
  • data:css (287)
  • invalid (185)
  • p3 (156)
  • data:html (115)
  • browser:multiple (87)

Detailed Description

browser-compat-data is a machine-readable dataset that documents browser and JavaScript runtime compatibility for Web technologies including APIs, CSS properties, HTML elements, and HTTP features.

The project solves the problem of scattered, inconsistent compatibility information by providing a single authoritative source that developers can query programmatically. It structures compatibility data in a standardized JSON format with over 15,000 features, each describing which browsers and runtimes support that feature and under what conditions. The data powers MDN Web Docs, CanIUse, Visual Studio Code, WebStorm, and other tools that help developers write cross-browser compatible code.

Developers should adopt this dataset if they build tools, documentation sites, or applications that need to display or reason about browser support. It suits any project that wants to avoid maintaining its own compatibility matrix. The package is available as a Node module with TypeScript type definitions, can be imported via CDN for browser and Deno environments, or accessed as raw JSON for other languages. The schema is formally defined and documented, making it straightforward to integrate into existing systems.

The project receives almost all of its issue reports from outside users rather than the core team, demonstrating substantial real-world adoption. Maintainers typically respond to new issues and pull requests within a few days.