y0sif/whisrs - Open Source PR Review Scorecard

Voice for the Linux desktop: dictation, read-aloud, and voice-driven LLM commands. Wayland & X11: Hyprland, Sway, Niri, GNOME, KDE. Cloud or fully offline. Written in Rust.

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

External PR Merge Rate: 89%

Response Time: -

First Timer Success: 89%

Frequently Asked Questions

Is y0sif/whisrs welcoming to first-time open-source contributors?

y0sif/whisrs has a recorded first-timer success rate of 88.9%. 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 y0sif/whisrs 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 68.9 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 68.9 places y0sif/whisrs in the S tier.

What is the external contributor pull request merge rate for y0sif/whisrs?

The external contributor pull request merge rate for y0sif/whisrs is 88.7%, based on public PR activity from non-core contributors.

Are there Good First Issues available in y0sif/whisrs?

y0sif/whisrs does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

y0sif
y0sif/whisrsS•Elite133
GitHub
Back to Explorer
y0sif

y0sif/whisrs

133
Active (30d)S•Elite(69/100)Rust

Voice for the Linux desktop: dictation, read-aloud, and voice-driven LLM commands. Wayland & X11: Hyprland, Sway, Niri, GNOME, KDE. Cloud or fully offline. Written in Rust.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
8.2/10
Patience Score
8.4/10
Nitpick Rate
35%

Highly welcoming maintainers in y0sif/whisrs. 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
88.7%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
11 core
Highly collaborative maintainer core
Diagnostic Health HUD
88.7%
Merge Gauge
88.9%
1st-Timer
Community Vibe62/100

Embed C-Rank Badge

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

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

Active Good First Issues (2)

View on GitHub

WindowTracker::get_focused_window_class() returns None on KDE. DbusTracker (src/window/dbus.rs) is a stub for both GNOME and KDE, so is_terminal is always false on Plasma and terminals there are treated as ordinary targets. Consequences, all of which already work on Hyprland, Niri, Sway and X11: command mode does not clear the prompt line before injecting a multi-line LLM reply is typed into the terminal instead of being refused, so every line break is an Enter selection copy sends Ctrl+C rather than Ctrl+Shift+C, which is SIGINT when a foreground process is running with [input] paste = true, injection sends Ctrl+V rather than Ctrl+Shift+V [input] terminal_classes is accepted, parsed, and never consulted GNOME is tracked separately in #72 and needs a different mechanism. #126 fixed Sway and X11, which leaves KDE as the only platform with a gap and no plan. Approach: the org_kde_plasma_window_management Wayland protocol carries app_id and an active state bit. A one shot query works, n

📅 Opened Aug 19, 2026💬 0 comments
Quality: 90/100Contribute

Some entries in TERMINAL_CLASSES (src/daemon/injection.rs) come from upstream source or packaging rather than an observed hyprctl or xprop capture: waveterm, tabby: source-derived. Wave's app_id is Electron-version dependent (Wave on 40.10.6 and older, waveterm on 41.0 to 41.5, wave on 41.6+), so the current entries may not cover every build. dev.warp.warp: secondary sources only. org.xfce.terminal, org.contourterminal.contour: defensive. The verified strings are xfce4-terminal and contour. Not covered at all: Tilda, Eterm, zutty, havoc, extraterm, lilyterm, wayst, darktile, mrxvt, aterm, wterm. If you run any of these, hyprctl activewindow -j | jq -r .class on Hyprland or Niri, or xprop WM_CLASS on X11, gives the string needed. A miss is not destructive, but it does fall back to plain Ctrl+C, which in a terminal is SIGINT to the foreground process rather than a copy, so the capture fails.

📅 Opened Aug 3, 2026💬 0 comments
Quality: 90/100Contribute
Looking for more Rust beginner tasks?Explore Rust 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 y0sif/whisrs

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

Frequently Asked Questions - Contributing to y0sif/whisrs

01

Is y0sif/whisrs welcoming to first-time open-source contributors?

y0sif/whisrs has a recorded first-timer success rate of 88.9%. 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 ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 68.9 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 68.9 places y0sif/whisrs in the Elite tier.

04

What is the external contributor pull request merge rate for y0sif/whisrs?

The external pull request merge rate is 88.7%. 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 y0sif/whisrs?

y0sif/whisrs does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for y0sif/whisrs 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.