One command deploys a censorship-resistant VLESS+Reality proxy server. Perfectly configured out-of-the-box. Relay nodes supported.
C-Rank Grade: C (Moderate) - 33/100
External PR Merge Rate: 100%
Response Time: 3d
First Timer Success: -
getmeridian/meridian has a recorded first-timer success rate of 0.0%. Repositories ranked C typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in getmeridian/meridian respond to incoming external pull requests in approximately 72.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 33.4 places getmeridian/meridian in the C tier.
The external contributor pull request merge rate for getmeridian/meridian is 100.0%, based on public PR activity from non-core contributors.
getmeridian/meridian currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in getmeridian/meridian. Reviews community pull requests with focus on project quality.
Discussions in getmeridian/meridian 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/getmeridian/meridian?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~47 hours (96% approval). Large PRs (>500 lines) take ~346 hours (45% approval). Keep your diff compact for rapid review.
WebRTC leaks are client-side — the browser discovers local IPs via OS APIs, bypassing the proxy entirely. Server-side fixes don't help; traffic never reaches Xray. Users who assume Meridian hides their IP may be wrong in a specific category of leak. Proposed: amber warning box on the connection page, similar to the existing clock-sync warning, with: Link to browserleaks.com/webrtc Per-app guidance (v2rayNG "Global" mode, Hiddify "route all connections", etc.) Browser extension recommendations Needs design/scope details: translation strings, placement on the page, whether to gate behind a "learn more" disclosure. Refs: #28
meridian client add currently accepts one name at a time. Remnawave API calls are fast and already parallel-friendly in this codebase (ThreadPoolExecutor is used for apply). Proposed: accept a variadic NAMES... argument, run adds in parallel, print a summary table at the end. Same --server / --yes flags. Good-first-issue. Design details to resolve Partial-success semantics — collect exceptions per-name, print a summary table (name → status / error), exit non-zero if ANY name failed. (All-or-nothing rollback would mean one duplicate name rolls back all the fresh ones — not operator-friendly.) Output format — for 1 name, print as client add does today; for N, render a table with columns NAME | UUID | STATUS. Concurrency cap — reuse the reconciler executor's ThreadPoolExecutor pattern from reconciler/executor.py with max_workers=8 to avoid hammering the panel. Refs: #28
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 getmeridian/meridian, 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 getmeridian/meridian acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
getmeridian/meridian has a recorded first-timer success rate of 0.0%. Repositories ranked Moderate typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 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 33.4 places getmeridian/meridian in the Moderate tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, getmeridian/meridian 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 getmeridian/meridian 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.