MoganLab/mogan - Open Source PR Review Scorecard

Mogan STEM Suite (based on GNU TeXmacs): Enjoy exploring science and technology!

C-Rank Grade: S (Elite) - 76/100

External PR Merge Rate: 79%

Response Time: 20h

First Timer Success: 88%

Frequently Asked Questions

Is MoganLab/mogan welcoming to first-time open-source contributors?

MoganLab/mogan has a recorded first-timer success rate of 87.5%. Repositories ranked S 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 MoganLab/mogan respond to incoming external pull requests in approximately 20.3 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 76.2 C-Rank™ score (S 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 76.2 places MoganLab/mogan in the S tier.

What is the external contributor pull request merge rate for MoganLab/mogan?

The external contributor pull request merge rate for MoganLab/mogan is 79.3%, based on public PR activity from non-core contributors.

Are there Good First Issues available in MoganLab/mogan?

MoganLab/mogan currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

MoganLab
MoganLab/moganS•Elite571
GitHub
Back to Explorer
MoganLab

MoganLab/mogan

571
Active (30d)S•Elite(76/100)SCScheme

Mogan STEM Suite (based on GNU TeXmacs): Enjoy exploring science and technology!

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
20%

Active maintainer team in MoganLab/mogan welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • •Ensure code complies with repository style conventions
  • •Keep PRs focused and well-documented

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
Response Velocity
20 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
79.3%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
9 core
Highly collaborative maintainer core
Diagnostic Health HUD
79.3%
Merge Gauge
87.5%
1st-Timer
Community Vibe73/100

Embed C-Rank Badge

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

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

Active Good First Issues (3)

View on GitHub

如下图所示,第二行公式的右括号大小没有匹配第一行 使用 \align 环境做测试

📅 Opened Mar 5, 2026💬 3 comments
Quality: 15/100Contribute
📅 Opened Feb 5, 2026💬 3 comments
Quality: 10/100Contribute

On macOS, MoganSTEM splits Ghostscript argv at spaces even when attempting to escape paths, breaking PS/EPS rendering when the user’s full name contains spaces. Reproducible with official dmg 2026.1.1. and dmg 2026.1.2.

📅 Opened Jan 27, 2026💬 2 comments
Quality: 15/100Contribute
Looking for more Scheme beginner tasks?Explore Scheme 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 MoganLab/mogan

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

Frequently Asked Questions - Contributing to MoganLab/mogan

01

Is MoganLab/mogan welcoming to first-time open-source contributors?

MoganLab/mogan has a recorded first-timer success rate of 87.5%. Repositories ranked Elite 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 ~20 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 76.2 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 76.2 places MoganLab/mogan in the Elite tier.

04

What is the external contributor pull request merge rate for MoganLab/mogan?

The external pull request merge rate is 79.3%. 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 MoganLab/mogan?

Yes, MoganLab/mogan currently has 3 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 MoganLab/mogan 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.