Terminal UI for WireGuard and OpenVPN with multi-tunnel control, real-time telemetry, and leak guarding.
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 52%
Response Time: -
First Timer Success: -
Harry-kp/vortix has a recorded first-timer success rate of 0.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Harry-kp/vortix 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 56.6 places Harry-kp/vortix in the A tier.
The external contributor pull request merge rate for Harry-kp/vortix is 51.9%, based on public PR activity from non-core contributors.
Harry-kp/vortix currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Rust project in Harry-kp/vortix welcoming community pull requests and bug fixes.
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/Harry-kp/vortix?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 Monday - Wednesday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (65% approval). Large PRs (>500 lines) take ~115 hours (23% approval). Keep your diff compact for rapid review.
Vortix is in homebrew-core (Formula/v/vortix.rb), but the formula only runs cargo install, so brew install vortix gives no tab completion. Homebrew has a helper for exactly this, and vortix completions <shell> runs without root. To do Open a PR to Homebrew/homebrew-core that adds, at the end of def install: generate_completions_from_executable(bin/"vortix", "completions") Follow their contributing guide and PR template, and run brew audit --strict vortix and brew test vortix. Once it merges, open a small PR here changing the note in docs/usage.md ("Diagnostics") so it says Homebrew installs completions. Check: after brew install --build-from-source vortix, vortix <Tab> completes subcommands in zsh, bash and fish.
The project fixes lints instead of allowing them (see CLAUDE.md, "Lints"). These nine #[allow] lines are stale: with each one removed, cargo clippy -p vortix --all-targets -- -D warnings still passes. crates/vortix/src/ui/dashboard/logs.rs:11: too_many_lines crates/vortix/src/ui/dashboard/connection_details.rs:26: similar_names crates/vortix/src/cli/status.rs:218: too_many_lines crates/vortix/src/cli/status.rs:498: cast_possible_wrap crates/vortix/src/app/state.rs:386: struct_field_names crates/vortix/src/cli/profiles.rs:33: too_many_lines crates/vortix/src/app/update.rs:628: too_many_lines, together with its comment crates/vortix/src/config/profiles.rs:50: too_many_lines, together with its comment crates/vortix/src/control/scanner.rs:369: too_many_lines Line numbers are from main when this issue was filed. Search for the attribute if they have moved. To do: delete those lines. Change nothing else. Check: scripts/ci-local.sh --quick passes. It also runs clippy for the Linux target, s
vortix list shows when each profile was last used. format_elapsed in crates/vortix/src/cli/profiles.rs always uses the plural, so a profile used 90 minutes ago reads 1 hours ago, and one used yesterday reads 1 days ago. To do Use 1 hour ago and 1 day ago for one, and keep the plural for two or more (2 hours ago). min already reads correctly for both. Extend test_format_elapsed in the same file with 3600, 7199, 86400 and 172799 seconds. Check: cargo test -p vortix format_elapsed passes. No root or VPN is needed.
`vortix completions ` prints a completion script for bash, zsh, fish, elvish and powershell, but `docs/usage.md` only shows the command, not where to put the output. To do Under Diagnostics in `docs/usage.md`, add one line per shell with the usual install location, e.g. `vortix completions fish > ~/.config/fish/completions/vortix.fish`, and the equivalents for bash and zsh. Mention that Homebrew and the `.deb`/`.rpm` packages don't install completions yet, if that's still true. Check: try each command in its shell. `cargo xtask check-docs` must pass.
`.github/workflows/linux-packages.yml` builds `.deb`/`.rpm` for amd64 and arm64, but only the amd64 ones are installed on clean Ubuntu, Debian and Fedora images. The arm64 packages ship untested. To do Add a job on the `ubuntu-24.04-arm` runner that downloads the built packages and runs the same install check against the `_arm64.deb` and `.aarch64.rpm` files: `wg-quick` and `openvpn` installed, `/usr/bin/vortix`, and the right `--version`. Keep a single copy of the check. Sharing it (for example through a matrix) is better than a second copy. Check: the workflow runs on PRs that touch it, so the PR itself shows it working.
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 Harry-kp/vortix, 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 Harry-kp/vortix acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 51.9% were successfully merged into the primary branch.
Harry-kp/vortix has a recorded first-timer success rate of 0.0%. Repositories ranked Welcoming 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 56.6 places Harry-kp/vortix in the Welcoming tier.
The external pull request merge rate is 51.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Harry-kp/vortix 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 Harry-kp/vortix 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.