OpenMOSS/MOSS-TTS-Nano - Open Source PR Review Scorecard

A 100M-parameter multilingual TTS model for real-time CPU inference, voice cloning, and 48 kHz stereo generation

C-Rank Grade: C (Moderate) - 37/100

External PR Merge Rate: 40%

Response Time: 17h

First Timer Success: -

Frequently Asked Questions

Is OpenMOSS/MOSS-TTS-Nano welcoming to first-time open-source contributors?

OpenMOSS/MOSS-TTS-Nano has a recorded first-timer success rate of 0.0%. Repositories ranked C 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 OpenMOSS/MOSS-TTS-Nano respond to incoming external pull requests in approximately 17.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 37.2 C-Rank™ score (C 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 37.2 places OpenMOSS/MOSS-TTS-Nano in the C tier.

What is the external contributor pull request merge rate for OpenMOSS/MOSS-TTS-Nano?

The external contributor pull request merge rate for OpenMOSS/MOSS-TTS-Nano is 40.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in OpenMOSS/MOSS-TTS-Nano?

OpenMOSS/MOSS-TTS-Nano currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

OpenMOSS
OpenMOSS/MOSS-TTS-NanoC•Moderate4.5k
GitHub
Back to Explorer
OpenMOSS

OpenMOSS/MOSS-TTS-Nano

4,459
InactiveC•Moderate(37/100)Low Sample (<20 PRs)Python

A 100M-parameter multilingual TTS model for real-time CPU inference, voice cloning, and 48 kHz stereo generation

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

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

Collaborative maintainer environment in OpenMOSS/MOSS-TTS-Nano. Reviews community pull requests with focus on project quality.

What Contributors Actually Say

Discussions in OpenMOSS/MOSS-TTS-Nano focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • •1) Keep PR scope strictly aligned with the linked issue.
  • •2) Ensure local linters pass before opening a review.
  • •3) Maintain full test coverage for modified logic.

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
16 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
40.0%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
0.0%
No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
40.0%
Merge Gauge
0.0%
1st-Timer
Community Vibe33/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

Hi 朋友们大家好~ MOSS-TTS 2.0 即将到来,为了更好地优化模型能力和产品体验,我们想收集大家在使用 TTS 过程中的反馈与建议。 希望大家能够花 2–3 分钟填写问卷,欢迎各种意义上的需求说明,包括许愿! MOSS-TTS 2.0 需求收集表 非常感谢大家一直以来的支持! Hi friends, MOSS-TTS 2.0 is coming soon. To better improve the model’s capabilities and product experience, we’d like to collect your feedback and suggestions from using TTS. We’d really appreciate it if you could spend 2–3 minutes filling out this survey. All kinds of requests and ideas are welcome — wishlists included! MOSS-TTS 2.0 Request Collection Form Thank you so much for your continued support!

📅 Opened Apr 29, 2026💬 0 comments
Quality: 70/100Contribute
Looking for more Python beginner tasks?Explore Python 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 OpenMOSS/MOSS-TTS-Nano

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

Frequently Asked Questions - Contributing to OpenMOSS/MOSS-TTS-Nano

01

Is OpenMOSS/MOSS-TTS-Nano welcoming to first-time open-source contributors?

OpenMOSS/MOSS-TTS-Nano has a recorded first-timer success rate of 0.0%. Repositories ranked Moderate 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 ~16 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 37.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 37.2 places OpenMOSS/MOSS-TTS-Nano in the Moderate tier.

04

What is the external contributor pull request merge rate for OpenMOSS/MOSS-TTS-Nano?

The external pull request merge rate is 40.0%. 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 OpenMOSS/MOSS-TTS-Nano?

Yes, OpenMOSS/MOSS-TTS-Nano currently has 1 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 OpenMOSS/MOSS-TTS-Nano 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.