Muesli-HQ/muesli - Open Source PR Review Scorecard

Muesli: agent-native local meeting transcription + dictation for macOS (Granola + WisprFlow alternative)

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

External PR Merge Rate: 63%

Response Time: 8d

First Timer Success: 35%

Frequently Asked Questions

Is Muesli-HQ/muesli welcoming to first-time open-source contributors?

Muesli-HQ/muesli has a recorded first-timer success rate of 35.0%. 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 Muesli-HQ/muesli respond to incoming external pull requests in approximately 191.2 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 61.4 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 61.4 places Muesli-HQ/muesli in the A tier.

What is the external contributor pull request merge rate for Muesli-HQ/muesli?

The external contributor pull request merge rate for Muesli-HQ/muesli is 62.9%, based on public PR activity from non-core contributors.

Are there Good First Issues available in Muesli-HQ/muesli?

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

Muesli-HQ
Muesli-HQ/muesliA•Welcoming1.4k
GitHub
Back to Explorer
Muesli-HQ

Muesli-HQ/muesli

1,385
Active (30d)A•Welcoming(61/100)Swift

Muesli: agent-native local meeting transcription + dictation for macOS (Granola + WisprFlow alternative)

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Community Mentor

Warmth Score
8.6/10
Patience Score
8.7/10
Nitpick Rate
16%

Highly encouraging & supportive maintainers (75% positive review sentiment). Active code reviews with constructive guidance for new contributors in Muesli-HQ/muesli.

Top PR Submission Do's

  • •Add unit tests with >80% coverage for modified code paths
  • •Use conventional commit messages and clean branch names
  • •Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without referencing an existing issue
  • •Do not mix refactoring and feature logic into a single commit
  • •Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
7 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
62.9%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
35.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
26 core
Highly collaborative maintainer core
Diagnostic Health HUD
62.9%
Merge Gauge
35.0%
1st-Timer
Community Vibe36/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

when I transcribe a meeting, I copy the transcript and provide it to my copilot manually, adding persona and skills as I see fit. Unfortunately, using the "copy" button for the transcription does not include the meeting date. It would be really cool to add all the meeting meta data to the copy along the transcript, so that my copilot will have all the information. thanks!

📅 Opened Sep 11, 2026💬 2 comments
Quality: 90/100Contribute

I'm on a large meeting, mostly muted in Teams. Near me, my colleagues are speaking. ==> Muesli catches my colleagues and transcribe them, but they are not part of the meeting. it would be cool if muesly can understand if I'm muted in teams, and ignore my mic completely.

📅 Opened Jul 7, 2026💬 5 comments
Quality: 65/100Contribute

Summary Explore porting microsoft/VibeVoice-ASR to Core ML and adding it to Muesli as another local transcription runtime. Why this is interesting VibeVoice-ASR is a Microsoft Research ASR model with several properties that could map well to Muesli's meeting transcription use case: Long-form ASR: model card says it can process up to 60 minutes of audio in a single pass. Rich transcript output: designed to emit speaker, timestamp, and content structure together. Multilingual/code-switching support: over 50 languages without requiring explicit language selection. Custom hotwords: supports user-provided terms, names, and domain vocabulary. MIT license. Model card details to account for: Hugging Face model: microsoft/VibeVoice-ASR Architecture/library: Transformers / VibeVoice Model size: about 9B parameters Tensor type: BF16 Paper: arXiv 2601.18184 Proposed implementation path Investigate whether VibeVoice-ASR can be converted to Core ML with a practical Apple Silicon runtime profile

📅 Opened May 11, 2026💬 0 comments
Quality: 70/100Contribute

Problem When a meeting is being transcribed, the app currently appears to route dictation and meeting transcription through the same speech-to-text path. In practice this means hotkey dictation is effectively unavailable while a meeting is active. This creates a bad UX for users who want to keep using normal dictation during a meeting, for example to jot down notes, send a message, or capture a private thought without it becoming part of the meeting transcription flow. Desired Outcome Dictation and meeting transcription should be separated so that: meeting transcription can continue uninterrupted while a meeting is active hotkey dictation still works during a meeting dictation output is treated as a separate user action, not merged into the meeting transcript pipeline the UI/state model makes it clear when a meeting is recording versus when ad hoc dictation is running Things To Investigate Which parts of the current codepath are shared between hold-to-talk dictation and meeting tran

📅 Opened Mar 20, 2026💬 1 comment
Quality: 70/100Contribute

Problem Qwen3 ASR is integrated and working in Muesli, but the autoregressive decoder is significantly slower than our CTC-based Parakeet model: Model Latency Architecture Parakeet TDT v3 ~0.13s CTC (parallel) Qwen3 ASR (int8) ~2-3s Autoregressive (sequential) The bottleneck is the CoreML decoder: it generates one token at a time, each requiring a full CoreML inference call. A 10-word transcription = ~15 sequential decoder calls. Proposed Optimization Re-export the Qwen3 decoder CoreML model with batch-4 token input shape, enabling speculative or batched decoding to reduce CoreML calls by up to 4x. Current decoder input shape hidden_states: [1, 1, 1024] (single token) position_cos: [1, 1, 128] position_sin: [1, 1, 128] mask: [1, 1, 1, cache_len] Target decoder input shape hidden_states: [1, 4, 1024] (4 tokens per call) position_cos: [1, 4, 128] position_sin: [1, 4, 128] mask: [1, 1, 4, cache_len] What's Needed PyTorch → CoreML re-export using

📅 Opened Mar 17, 2026💬 5 comments
Quality: 70/100Contribute
Looking for more Swift beginner tasks?Explore Swift 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 Muesli-HQ/muesli

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

Frequently Asked Questions - Contributing to Muesli-HQ/muesli

01

Is Muesli-HQ/muesli welcoming to first-time open-source contributors?

Muesli-HQ/muesli has a recorded first-timer success rate of 35.0%. 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 ~7 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 61.4 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 61.4 places Muesli-HQ/muesli in the Welcoming tier.

04

What is the external contributor pull request merge rate for Muesli-HQ/muesli?

The external pull request merge rate is 62.9%. 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 Muesli-HQ/muesli?

Yes, Muesli-HQ/muesli 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 Muesli-HQ/muesli 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.