sozercan/kaset - Open Source PR Review Scorecard

📼 The missing YouTube and YouTube Music macOS app

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

External PR Merge Rate: 64%

Response Time: 18h

First Timer Success: 45%

Frequently Asked Questions

Is sozercan/kaset welcoming to first-time open-source contributors?

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

What does the 60.9 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 60.9 places sozercan/kaset in the A tier.

What is the external contributor pull request merge rate for sozercan/kaset?

The external contributor pull request merge rate for sozercan/kaset is 63.7%, based on public PR activity from non-core contributors.

Are there Good First Issues available in sozercan/kaset?

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

sozercan
sozercan/kasetA•Welcoming2.4k
GitHub
Back to Explorer
sozercan

sozercan/kaset

2,404
Active (30d)A•Welcoming(61/100)Swift

📼 The missing YouTube and YouTube Music macOS app

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

High-Friction Gatekeeper

Warmth Score
6.2/10
Patience Score
6.9/10
Nitpick Rate
49%

Rigorous architecture standards (75% critical review signals). Ensure PRs strictly follow guidelines before requesting review in sozercan/kaset.

Top PR Submission Do's

  • •Add unit tests with >80% coverage for modified code paths
  • •Run repository linter and code formatters locally before pushing
  • •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
18 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
63.7%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
45.5%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
36 core
Highly collaborative maintainer core
Diagnostic Health HUD
63.7%
Merge Gauge
45.5%
1st-Timer
Community Vibe55/100

Embed C-Rank Badge

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

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

Active Good First Issues (2)

View on GitHub

Is there an existing feature request for this? I have searched the existing issues Problem or Motivation the context menus aren't the same on every page, and sometimes do not exist song context menu on the home page song context menu on the album page no context menu for the singles in the artist page likewise, the "new releases" section of the sidebar (below moods and genres) does not have any context menus whatsoever for any items Proposed Solution make the context menus a shared view, and reuse it on every pages Alternatives Considered No response Feature Area UI / Visual How important is this feature to you? Would improve my experience Mockups or Examples No response Additional Context No response

📅 Opened Sep 25, 2026💬 0 comments
Quality: 50/100Contribute

Is there an existing issue for this? I have searched the existing issues Bug Description When Google account session expired on macOS like the picture bellow, I can't close the app. Kaset Version: 0.14.0 (24) macOS Version: 26.3 (25D125) Expected Behavior I need to close the app. Steps to Reproduce Login google account, keep app open, wait for session expire, the app can't close macOS Version macOS 26 (Tahoe) Kaset Version 0.14.0 (24) Affected Area Other Screenshots or Logs No response Additional Context No response

📅 Opened Sep 14, 2026💬 2 comments
Quality: 90/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 sozercan/kaset

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

Frequently Asked Questions - Contributing to sozercan/kaset

01

Is sozercan/kaset welcoming to first-time open-source contributors?

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

03

What does the 60.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 60.9 places sozercan/kaset in the Welcoming tier.

04

What is the external contributor pull request merge rate for sozercan/kaset?

The external pull request merge rate is 63.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 sozercan/kaset?

sozercan/kaset 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 sozercan/kaset 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.