Virtual Input over IP Emulator - VIIPER is a tool to create virtual input devices using USBIP. (Linux/Windows)
C-Rank Grade: B (Solid) - 52/100
External PR Merge Rate: 44%
Response Time: 13h
First Timer Success: 50%
Alia5/VIIPER has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Alia5/VIIPER respond to incoming external pull requests in approximately 13.5 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 51.6 places Alia5/VIIPER in the B tier.
The external contributor pull request merge rate for Alia5/VIIPER is 44.4%, based on public PR activity from non-core contributors.
Alia5/VIIPER currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in Alia5/VIIPER. Reviews community pull requests with focus on project quality.
Discussions in Alia5/VIIPER 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/Alia5/VIIPER?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 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 19:00 to 23:00 UTC (19:00 - 23:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~9 hours (56% approval). Large PRs (>500 lines) take ~65 hours (20% approval). Keep your diff compact for rapid review.
Is your feature request related to a problem? Please describe The current way (usage of password file) for connecting remote clients is clunky and not user friendly. Describe the solution you'd like A pairing API. This API would be available under pair. Upon receiving the server would keep the connection alive and keep track of the pairing request, similar to how device-streams work. A pairing request must be approved within N seconds. A new command will be added to list and approve pairing requests. The approve and list commands talk to another new endpoint pairings with paramters list or approve. These APIs are only callable from localhost. At a later stage a gui for this can be figured out (See also #6 (comment)) Upon approval a random password is generated, stored in an sqlite.db and sent ro the client. The pairing connection closes.
For networked scenarios, VIIPER should provide service discovery via zeroconf or similar
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 Alia5/VIIPER, 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 Alia5/VIIPER acknowledge new external contributions in approximately 13 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 44.4% were successfully merged into the primary branch.
Alia5/VIIPER has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~13 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 51.6 places Alia5/VIIPER in the Solid tier.
The external pull request merge rate is 44.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Alia5/VIIPER currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for Alia5/VIIPER 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.