:globe_with_meridians: :electric_plug: The MetaMask browser extension enables browsing Ethereum blockchain enabled websites
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 66%
Response Time: 1d
First Timer Success: 57%
MetaMask/metamask-extension has a recorded first-timer success rate of 57.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in MetaMask/metamask-extension respond to incoming external pull requests in approximately 24.4 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 67.0 places MetaMask/metamask-extension in the A tier.
The external contributor pull request merge rate for MetaMask/metamask-extension is 65.6%, based on public PR activity from non-core contributors.
MetaMask/metamask-extension currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
:globe_with_meridians: :electric_plug: The MetaMask browser extension enables browsing Ethereum blockchain enabled websites
Highly welcoming maintainers in MetaMask/metamask-extension. Prompt code reviews with positive guidance for new contributors.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/MetaMask/metamask-extension?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (82% approval). Large PRs (>500 lines) take ~117 hours (30% approval). Keep your diff compact for rapid review.
Goal Migrate deprecated extension UI component usages to MMDS components from @metamask/design-system-react, in small easy-to-review PRs. This is an evergreen tracker. Do not try to complete every deprecated usage in one PR. Visual Evidence Is Required Before/after visual assets are the key output of this automation. Every PR must include visual evidence for the changed UI so reviewers can confirm there was no regression without manually rebuilding the branch. Required: A before screenshot from current main. An after screenshot from the PR branch. A short note identifying the route, Storybook story, state setup, or mm flow used to capture the screenshots. Screenshots must show the migrated component in context, not only a cropped DOM fragment or isolated code diff. Preferred: Use the MetaMask visual-testing skill or mm flow. Repo guidance lives in test/e2e/playwright/llm-workflow/. Use the same viewport, state, account, network, and route for before and after screenshots. Include an
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to MetaMask/metamask-extension, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of MetaMask/metamask-extension acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 65.6% were successfully merged into the primary branch.
MetaMask/metamask-extension has a recorded first-timer success rate of 57.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 67.0 places MetaMask/metamask-extension in the Welcoming tier.
The external pull request merge rate is 65.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, MetaMask/metamask-extension currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for MetaMask/metamask-extension are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.