Securely connect your devices into a private network. Mesh VPN, socks5 proxy server/client
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 88%
Response Time: 5d
First Timer Success: 100%
anywherelan/awl has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in anywherelan/awl respond to incoming external pull requests in approximately 125.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 59.8 places anywherelan/awl in the A tier.
The external contributor pull request merge rate for anywherelan/awl is 88.5%, based on public PR activity from non-core contributors.
anywherelan/awl currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in anywherelan/awl.
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/anywherelan/awl?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~82 hours (96% approval). Large PRs (>500 lines) take ~603 hours (40% approval). Keep your diff compact for rapid review.
Windows AMD64 version gets detected as Trojan by windows defender, and immediately removed. Also emits trojan like behavior, like disabling windows defender...
Currently, there is no fine-grained control over how private network addresses are handled in the VPN configuration. This proposal suggests adding two new configuration options to provide more flexibility in routing private network traffic. Proposed Solution I suggest adding the following two configuration options: 1. RouteLan Purpose: Indicates whether to route private network addresses to the VPN gateway Effect: When enabled, private network traffic (e.g., RFC 1918 addresses) is tunneled through the VPN connection When to use: For scenarios where users want to access local network resources through the VPN gateway 2. AllowLan Purpose: Indicates whether clients are allowed to route packets containing private network addresses Effect: When enabled, clients can send and receive packets with private network addresses; when disabled, such packets are dropped or rejected When to use: For controlling client permissions and preventing unintended local network access Use Cases Network Is
# awl cli gateway server enable 2026-07-21T06:02:04.882Z FATAL awl/cli Error occurred: status code: 500, error: setup NAT: init iptables: exec: "iptables": executable file not found in $PATH OS Information # nix-shell -p nix-info --run "nix-info -m" - system: `"x86_64-linux"` - host os: `Linux 6.18.37, NixOS, 26.05 (Yarara), 26.05.20260630.95ca1e2` - multi-user?: `yes` - sandbox: `yes` - version: `nix-env (Nix) 2.34.7` - nixpkgs: `/nix/store/bdn0zqq9mqdc9ccwfnamx4lax9163xr1-source`
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 anywherelan/awl, 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 anywherelan/awl acknowledge new external contributions in approximately 5 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 88.5% were successfully merged into the primary branch.
anywherelan/awl has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 days+. 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 59.8 places anywherelan/awl in the Welcoming tier.
The external pull request merge rate is 88.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, anywherelan/awl 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 anywherelan/awl 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.