Mission control for your AI agents
C-Rank Grade: B (Solid) - 51/100
External PR Merge Rate: 17%
Response Time: 5h
First Timer Success: -
RizRiyz/luvus has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in RizRiyz/luvus respond to incoming external pull requests in approximately 5.1 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 50.8 places RizRiyz/luvus in the B tier.
The external contributor pull request merge rate for RizRiyz/luvus is 16.7%, based on public PR activity from non-core contributors.
RizRiyz/luvus does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Strict review standards in RizRiyz/luvus. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in RizRiyz/luvus 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/RizRiyz/luvus?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 Tuesday - Thursday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (21% approval). Large PRs (>500 lines) take ~24 hours (15% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Rust.
Rusty wrapper for the Unified Extensible Firmware Interface (UEFI). This crate makes it easy to develop Rust software that leverages safe, convenient, and performant abstractions for UEFI functionality.
Safe Rust bindings to POSIX-ish APIs
A slightly quackers Docker TUI based on k9s 🦆
Description Running: luvus skill enable claude fails with: Error: this Luvus build has no skill verification key; release builds must set LUVUS_SKILL_PUBLIC_KEY_B64 The same issue should potentially affect: luvus skill enable codex luvus skill enable opencode Steps to reproduce Install Luvus using the official prebuilt release, for example via the installer or Homebrew. Run: luvus skill enable claude The command fails immediately with: Error: this Luvus build has no skill verification key; release builds must set LUVUS_SKILL_PUBLIC_KEY_B64 Expected behavior The official release binary should contain the production skill verification public key, allowing Luvus to verify the signed skill manifest and install the requested skill. For example: luvus skill enable claude should download, verify, and install the Claude skill normally. Actual behavior The release binary appears to have been built without LUVUS_SKILL_PUBLIC_KEY_B64, so verification_key() fails before the skill manifest can be f
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 RizRiyz/luvus, 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 RizRiyz/luvus acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 16.7% were successfully merged into the primary branch.
RizRiyz/luvus has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 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 50.8 places RizRiyz/luvus in the Solid tier.
The external pull request merge rate is 16.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
RizRiyz/luvus 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 RizRiyz/luvus 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.