An open source alternative to raycast, in rust!! (retired)
C-Rank Grade: B (Solid) - 49/100
External PR Merge Rate: 75%
Response Time: 3h
First Timer Success: 67%
MystikoLab/rustcast has a recorded first-timer success rate of 66.7%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in MystikoLab/rustcast respond to incoming external pull requests in approximately 2.6 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 48.8 places MystikoLab/rustcast in the B tier.
The external contributor pull request merge rate for MystikoLab/rustcast is 75.0%, based on public PR activity from non-core contributors.
MystikoLab/rustcast does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Collaborative maintainer environment in MystikoLab/rustcast. Reviews community pull requests with focus on project quality.
Discussions in MystikoLab/rustcast focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/MystikoLab/rustcast?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (94% approval). Large PRs (>500 lines) take ~12 hours (34% approval). Keep your diff compact for rapid review.
Describe the bug A clear and concise description of what the bug is. Rustcast has a high CPU and RAM Usage. To Reproduce Steps to reproduce the behavior: NIL - Rustcast's usage is high all the time. Expected behavior A clear and concise description of what you expected to happen. Rustcast is a background app and hence should have low resource and compute usage. Screenshots If applicable, add screenshots to help explain your problem. Which macos version? (please complete the following information): OS: MacOS Tahoe 26.5 Rustcast Version: v0.8.1 This is caused mostly by the Clipboard history which saves every image as raw bytes. Using a database would reduce the weight on the ram, but other optimisations should also take place.
I think hyperkey would be a nice touch to add to rustcast, I think its simply adding a global listener, and then return nill, followed by doing a new CGEventTap which is just a bunch of modifiers. Quoting chatgpt: User holds your chosen key (say Caps Lock or F18). Your app sets hyperDown = true and swallows the physical key event. When user presses K while hyperDown, your app swallows that K event and posts a synthetic K with modifier flags control|option|shift command. Result: other apps receive ⌃⌥⇧⌘K.
Are there any plans to port this over to other Unix-based systems and/or Windows?
This adds support for extensions / plugins in rustcast
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 MystikoLab/rustcast, 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 MystikoLab/rustcast acknowledge new external contributions in approximately 2 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.0% were successfully merged into the primary branch.
MystikoLab/rustcast has a recorded first-timer success rate of 66.7%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 hours. 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 48.8 places MystikoLab/rustcast in the Solid tier.
The external pull request merge rate is 75.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
MystikoLab/rustcast does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for MystikoLab/rustcast 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.