pshenok/server-survival - Open Source PR Review Scorecard

Tower defense game that teaches cloud architecture. Build infrastructure, survive traffic, learn scaling.

C-Rank Grade: A (Welcoming) - 63/100

External PR Merge Rate: 84%

Response Time: 3d

First Timer Success: 100%

Frequently Asked Questions

Is pshenok/server-survival welcoming to first-time open-source contributors?

pshenok/server-survival 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.

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

Maintainers in pshenok/server-survival respond to incoming external pull requests in approximately 70.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 62.7 C-Rank™ score (A 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 62.7 places pshenok/server-survival in the A tier.

What is the external contributor pull request merge rate for pshenok/server-survival?

The external contributor pull request merge rate for pshenok/server-survival is 83.5%, based on public PR activity from non-core contributors.

Are there Good First Issues available in pshenok/server-survival?

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

pshenok
pshenok/server-survivalA•Welcoming6.4k
GitHub
Back to Explorer
pshenok

pshenok/server-survival

6,433
Active (30d)A•Welcoming(63/100)JavaScript

Tower defense game that teaches cloud architecture. Build infrastructure, survive traffic, learn scaling.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
8.3/10
Patience Score
8.4/10
Nitpick Rate
40%

Highly welcoming maintainers in pshenok/server-survival. Prompt code reviews with positive guidance for new contributors.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
2 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
83.5%
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
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
83.5%
Merge Gauge
100.0%
1st-Timer
Community Vibe63/100

Embed C-Rank Badge

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

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

Active Good First Issues (2)

View on GitHub

On a keyboard, Q/E orbit the camera and T switches between the isometric and top-down views. A phone has no keyboard, and there is no touch equivalent for either, as the README now says under "On a phone or tablet". Everything else on a phone works since #289, #282 and #307: tap, drag, two-finger pan and pinch zoom, and the HUD tabs. This is a good first contribution: both behaviours already exist, and they only need a touch entry point. Where things are orbitCamera(deltaRadians) in src/input/handlers.js rotates the isometric view. Q/E call it from animate() in game.js. toggleView() in the same file flips isometric ↔ top-down. T calls it. The touch handlers are in src/input/handlers.js, at container.addEventListener("touchmove", ...). Two fingers already pan, using touchMidpoint, and pinch, using touchDistance. The phone HUD tab strip is #hudTabs in index.html. Its last button, #btn-reset-view, is the touch stand-in for R, wired in src/ui/hud-tabs.js. Two possible approaches (eithe

📅 Opened Oct 8, 2026💬 2 comments
Quality: 90/100Contribute

Found by the native reviewer during #240 (out of its scope — pre-existing): traffic_inference in it.js says "INFERENZA", while the six chapter-5 description keys (gpu_/infgw_) and the campaign narrative all use "INFERENCE" (Latin, per the file's traffic-type convention). One concept, two renderings — the HUD chip and the service cards disagree. Some it.js achievement descriptions cite campaign level titles in English while others cite them in Italian (compare the wave-1 block around lines 657-663 with the wave-2 block around 717-721). Since #240 the level titles render in Italian ("Ciao, GPU", "Batch o Dissanguamento", "La Deadline"), so the English citations now point at titles the player never sees. Fix direction: align traffic_inference to INFERENCE, and make all achievement citations use the Italian titles as they appear in the level_*_title keys. Both are it.js-only string edits; the parity suite guards the rest.

📅 Opened Aug 5, 2026💬 1 comment
Quality: 80/100Contribute
Looking for more JavaScript beginner tasks?Explore JavaScript 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 pshenok/server-survival

When evaluating whether to contribute to pshenok/server-survival, 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 pshenok/server-survival acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.5% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to pshenok/server-survival

01

Is pshenok/server-survival welcoming to first-time open-source contributors?

pshenok/server-survival 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.

02

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

The initial maintainer response time averages ~2 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 62.7 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 62.7 places pshenok/server-survival in the Welcoming tier.

04

What is the external contributor pull request merge rate for pshenok/server-survival?

The external pull request merge rate is 83.5%. 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 pshenok/server-survival?

Yes, pshenok/server-survival 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 pshenok/server-survival 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.