Fast featureful friendly wifi terminal UI. 🛜✨
C-Rank Grade: D (Risky) - 24/100
External PR Merge Rate: -
Response Time: <1h
First Timer Success: -
shazow/wifitui has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in shazow/wifitui 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 23.8 places shazow/wifitui in the D tier.
The external contributor pull request merge rate for shazow/wifitui is 0.0%, based on public PR activity from non-core contributors.
shazow/wifitui currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in shazow/wifitui. Reviews community pull requests with focus on project quality.
Discussions in shazow/wifitui 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/shazow/wifitui?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Monday - Friday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (81% approval). Large PRs (>500 lines) take ~0 hours (29% approval). Keep your diff compact for rapid review.
#189 refactors the darwin backend to link against CoreWLAN with cgo to get better functionality. Need someone to validate that everything still works. It's merged into main now, something along these lines would be helpful (paste output and feedback): # Get the latest wifitui build from main (or build yourself using `go build` or `make`) $ nix shell github:shazow/wifitui # Run some commands and make sure output makes sense $ wifitui --version v0.13.0-49-g2026438 $ wifitui list ... # Mess with the TUI: Join a network, maybe forget an old network $ wifitui
Right now wifitui just picks the first wifi device it finds, which is probably fine for 99% of users, but would be nice to have a way to specify a device if there are multiple. Something along the lines of adding a global wifitui --device=[auto|wlan0|...] flag to the main command. Would be useful to also add a way to list devices, but not sure it's worth a whole subcommand for it. Would it be too overloaded/confusing to have a wifitui --device=list?
Would be cool to have a wifitui module for waybar, ironbar, etc. At least a recipe or helper script to facilitate opening wifitui easily? Not sure what the best approach is here, haven't made statusbar modules before, is it better to go super native vs not? Suggestions welcome! MVP: Wifi icon indicator, click to open wifitui in a terminal? Better: Right click to present a list of available connections and clicking any of them switches to that connection
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 shazow/wifitui, 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 shazow/wifitui acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
shazow/wifitui has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 23.8 places shazow/wifitui in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, shazow/wifitui currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for shazow/wifitui 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.