mengxi-ream/read-frog - Open Source PR Review Scorecard

🐸 Read Frog - Language Learning & Translate | 🐸 陪读蛙 - 语言学习与翻译

C-Rank Grade: A (Welcoming) - 68/100

External PR Merge Rate: 73%

Response Time: -

First Timer Success: 54%

Frequently Asked Questions

Is mengxi-ream/read-frog welcoming to first-time open-source contributors?

mengxi-ream/read-frog has a recorded first-timer success rate of 54.2%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in mengxi-ream/read-frog respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 67.8 C-Rank™ score (A Tier) represent?

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.8 places mengxi-ream/read-frog in the A tier.

What is the external contributor pull request merge rate for mengxi-ream/read-frog?

The external contributor pull request merge rate for mengxi-ream/read-frog is 73.1%, based on public PR activity from non-core contributors.

Are there Good First Issues available in mengxi-ream/read-frog?

mengxi-ream/read-frog currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

mengxi-ream
mengxi-ream/read-frogA•Welcoming10.0k
GitHub
Back to Explorer
mengxi-ream

mengxi-ream/read-frog

10,046
Active (30d)A•Welcoming(68/100)TypeScript

🐸 Read Frog - Language Learning & Translate | 🐸 陪读蛙 - 语言学习与翻译

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.9/10
Patience Score
8.4/10
Nitpick Rate
20%

Highly welcoming maintainers in mengxi-ream/read-frog. Prompt code reviews with positive guidance for new contributors.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
-
No reviewer activity recorded

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
73.1%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
54.2%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
18 core
Highly collaborative maintainer core
Diagnostic Health HUD
73.1%
Merge Gauge
54.2%
1st-Timer
Community Vibe45/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for mengxi-ream/read-frog
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/mengxi-ream/read-frog)](https://getmerged.abhishekco.de/mengxi-ream/read-frog?utm_source=github&utm_medium=badge)

Active Good First Issues (4)

View on GitHub

Before you report I have searched existing issues to avoid duplicates I have confirmed this on the latest extension version Current vs. Expected behavior When Read Frog page translation is enabled on the Shopify Admin embedded app Omega Facebook Pixel, the app iframe is translated, but the injected translation styling breaks the page layout. Current behavior observed from the screenshots: Translated Chinese text is inserted as separate green text blocks instead of staying visually attached to the source UI. On the onboarding page, several translations are concatenated into a long green paragraph below the setup cards and form instead of being placed beside the related labels/descriptions. On the order report/dashboard page, guidance and status text translations are collected into a long green paragraph near the bottom of the iframe, spanning across the content area. Inline controls such as tab labels and buttons receive appended translations, which makes spacing and alignment look

📅 Opened Jun 25, 2026💬 1 comment
Quality: 80/100Contribute

Before you report I have searched existing issues to avoid duplicates I have tried with the latest available version (or can reproduce on latest) Current vs. Expected behavior 部分网站 鼠标悬停翻译功能 和 选择工具栏功能(选中内容未弹出工具栏) 失效 To Reproduce 例一:部分内容 鼠标悬停翻译功能 失效,网址:标题部分失效 例二:所有内容 鼠标悬停翻译功能 和 选择工具栏功能 均失效,网址:全部失效 Which area(s) are affected? (Select all that apply) Website Extension version (if applicable) 1.35.0 Provide environment information - 系统:windows10 - 浏览器: chrome - 扩展版本: 1.35.0 Additional context No response

📅 Opened Jun 23, 2026💬 2 comments
Quality: 80/100Contribute

Summary On Mobalytics PoE 2 guide pages, page translation can translate chrome/header/sidebar content into Chinese, but the main guide body remains untranslated. The affected content is inside Mobalytics' Lexical rich-text guide body. The current evidence points to the site runtime removing externally inserted DOM nodes inside the guide paragraphs after Read Frog inserts or attempts to insert translated wrappers. Reported page: https://mobalytics.gg/poe-2/guides/campaign-martial-weapon-crafting#54b21eea-823f-4edc-844c-980710e995ea-act-4-3 Example untranslated paragraph: In The Red Vale, Rusted Arms and Refined Arms can drop weapons. While each Arm individually is random, the full set of Arms collectively guarantees at least one of every weapon type (wands and staves are excluded). Because of this, if you open all of them, you’ll always find at least one weapon suitable for your class. Always click them whenever you see them. Environment Tested Browser: Microsoft Edge 148.0.3967.54

📅 Opened May 14, 2026💬 3 comments
Quality: 80/100Contribute

Before you report I have searched existing issues to avoid duplicates I have tried with the latest available version (or can reproduce on latest) Current vs. Expected behavior I'm currently testing the translation capabilities of Read Frog and I noticed an issue on websites with complex layouts. While the extension successfully translates the main body content (articles, headlines, main or tags), it completely skips the header/navigation menus and the footer sections. Steps to Reproduce Go to a complex website like https://edition.cnn.com/ or https://science.nasa.gov/. Activate Read Frog to translate the page into Italian (or any other target language). Check the top navigation bar and scroll down to the bottom footer. Expected Behavior The entire page should be translated, including the top navigation menus (, ) and the bottom link sections (). Actual Behavior The main editorial content is translated correctly, but the header and the large footer sections remain in the original

📅 Opened May 10, 2026💬 1 comment
Quality: 70/100Contribute
Looking for more TypeScript beginner tasks?Explore TypeScript GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for mengxi-ream/read-frog

When evaluating whether to contribute to mengxi-ream/read-frog, 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 mengxi-ream/read-frog acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 73.1% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to mengxi-ream/read-frog

01

Is mengxi-ream/read-frog welcoming to first-time open-source contributors?

mengxi-ream/read-frog has a recorded first-timer success rate of 54.2%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 67.8 C-Rank™ score represent?

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.8 places mengxi-ream/read-frog in the Welcoming tier.

04

What is the external contributor pull request merge rate for mengxi-ream/read-frog?

The external pull request merge rate is 73.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in mengxi-ream/read-frog?

Yes, mengxi-ream/read-frog currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for mengxi-ream/read-frog 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.