willjasen/tailmox - Open Source PR Review Scorecard

cluster proxmox over tailscale

C-Rank Grade: B (Solid) - 60/100

External PR Merge Rate: 83%

Response Time: <1h

First Timer Success: 100%

Frequently Asked Questions

Is willjasen/tailmox welcoming to first-time open-source contributors?

willjasen/tailmox has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in willjasen/tailmox respond to incoming external pull requests in approximately 0.7 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 60.4 C-Rank™ score (B Tier) represent?

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 60.4 places willjasen/tailmox in the B tier.

What is the external contributor pull request merge rate for willjasen/tailmox?

The external contributor pull request merge rate for willjasen/tailmox is 83.3%, based on public PR activity from non-core contributors.

Are there Good First Issues available in willjasen/tailmox?

willjasen/tailmox currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

willjasen
willjasen/tailmoxB•Solid230
GitHub
Back to Explorer
willjasen

willjasen/tailmox

230
Active (30d)B•Solid(60/100)Low Sample (<20 PRs)Capped at B (Bus Factor: 0)Shell

cluster proxmox over tailscale

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
9.5/10
Patience Score
9.2/10
Nitpick Rate
20%

Highly welcoming maintainers in willjasen/tailmox. Prompt code reviews with positive guidance for new contributors.

What Contributors Actually Say

Discussions in willjasen/tailmox focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • •1) Keep PR scope strictly aligned with the linked issue.
  • •2) Ensure local linters pass before opening a review.
  • •3) Maintain full test coverage for modified logic.

Top PR Submission Do's

  • •Add or update tests for changed behavior before requesting review
  • •Link the issue and include reproduction context in the PR
  • •Run the repository formatter and linter locally

Top PR Friction Pitfalls (Don'ts)

  • •Do not leave requested test coverage unresolved
  • •Do not open context-free PRs
  • •Do not submit formatting-only noise with feature changes
Response Velocity
<1 hour
⚡ Fast reviewer response

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
83.3%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
100.0%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
CRITICAL BUS FACTOR
Single maintainer
No active GitHub maintainers found (may review internally on Gerrit or internal tools)
Diagnostic Health HUD
83.3%
Merge Gauge
100.0%
1st-Timer
Community Vibe93/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for willjasen/tailmox
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/willjasen/tailmox)](https://getmerged.abhishekco.de/willjasen/tailmox?utm_source=github&utm_medium=badge)

Active Good First Issues (1)

View on GitHub

Hi, While trying to use the script, after Tailscale starts and it prints the IP & MagicDNS name the script appears to hang until interrupted, I have left it for about 30mins and nothing is happening. This occurs both with & without the --staging flag. * I am using a fresh Tailscale account/Tailnet, and a fresh install of Proxmox - However, it is a "pre-configured" base from Ionos on one of their machines, so I don't know if something they have done may be affecting it. If I use Ctrl+C to interrupt, the script then prints Tailscale serve is now running. & Tailscale service started for tailmox. But the Service shows no hosts in the Tailscale Admin Console. *Initially I had also tried to run the script on three internal Nodes which are already clustered, and these hung in the same place as well.

📅 Opened Sep 17, 2026💬 9 comments
Quality: 90/100Contribute
Looking for more Shell beginner tasks?Explore Shell GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for willjasen/tailmox

When evaluating whether to contribute to willjasen/tailmox, 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 willjasen/tailmox acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.3% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to willjasen/tailmox

01

Is willjasen/tailmox welcoming to first-time open-source contributors?

willjasen/tailmox has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~<1 hour. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 60.4 C-Rank™ score represent?

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 60.4 places willjasen/tailmox in the Solid tier.

04

What is the external contributor pull request merge rate for willjasen/tailmox?

The external pull request merge rate is 83.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in willjasen/tailmox?

Yes, willjasen/tailmox currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for willjasen/tailmox 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.