The power of Raycast. The speed of Alfred. Privacy by design.
C-Rank Grade: S (Elite) - 72/100
External PR Merge Rate: 93%
Response Time: -
First Timer Success: 67%
Xoshbin/asyar has a recorded first-timer success rate of 66.7%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Xoshbin/asyar 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.
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 71.5 places Xoshbin/asyar in the S tier.
The external contributor pull request merge rate for Xoshbin/asyar is 92.9%, based on public PR activity from non-core contributors.
Xoshbin/asyar currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in Xoshbin/asyar. Prompt code reviews with positive guidance for new contributors.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/Xoshbin/asyar?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (42% approval). Keep your diff compact for rapid review.
Is your feature request related to a problem? Inspired by raycast, have the option to view the extension store web page directly Proposed Solution / Alternatives Considered No response
Is your feature request related to a problem? Currently the settings window, when not having the show in dock toggle toggled is not shown as an "app" where you can cycle through. Makes it kinda hard to focus back to window when switched to other app Proposed Solution / Alternatives Considered No response
Asyar Version v.0.1.1-51 Platform / OS macOS Description cant drag onboarding window. im not sure if its intended, but on dual monitor setup its kinda annoying. You are not allowed to resize or move window Steps to Reproduce Logs or Additional Context
#842 added a macOS-only System Settings built-in (search “sound”, “displays”, ... and open the pane directly). We’d like the same on Windows and Linux. Where to start: asyar-launcher/src/built-in-features/system-settings/panes.ts (settingsPanesFor) and the Rust open_settings_pane command (one cfg(target_os) arm per platform). Windows: map the existing pane ids to ms-settings: pages. Linux: detect the desktop environment (start with GNOME and KDE) and map ids to the matching panel or module, with a graceful fallback. Checklist: per-platform targets for the shared ids, locale strings for any new panes (all 4 locales), tests for the lookup and the Rust allowlist, a note in docs/guide/features/system-settings.md. Please say which platform you’re taking, so two people don’t start the same one.
Problem Agent threads have a pinned state in the backend, but users have no way to pin or unpin a thread. The ⌘K action panel in the agent chat view only offers "New thread" and "Delete thread". What already exists DB column threads.is_pinned and set_thread_pinned in asyar-launcher/src-tauri/crates/asyar-storage/src/agents.rs Tauri command agents_thread_set_pinned TS wrappers agentsThreadSetPinned (src/lib/ipc/agentCommands.ts) and agentService.setThreadPinned(id, pinned) (src/built-in-features/agents/agentService.svelte.ts) Pinned threads already sort first (ORDER BY is_pinned DESC, updated_at DESC) and are skipped by retention pruning Thread.isPinned in src/built-in-features/agents/types.ts Nothing outside tests calls setThreadPinned, so the feature is unreachable today. This is frontend-only work. Proposal Add a Pin / Unpin action to the chat-view actions in src/built-in-features/agents/index.ts, next to ACTION_NEW_THREAD and ACTION_DELETE_THREAD in registerChatViewActions(). A
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to Xoshbin/asyar, 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 Xoshbin/asyar acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 92.9% were successfully merged into the primary branch.
Xoshbin/asyar has a recorded first-timer success rate of 66.7%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
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 71.5 places Xoshbin/asyar in the Elite tier.
The external pull request merge rate is 92.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Xoshbin/asyar currently has 6 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for Xoshbin/asyar 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.