A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 70%
Response Time: 14h
First Timer Success: 80%
amruthpillai/reactive-resume has a recorded first-timer success rate of 80.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in amruthpillai/reactive-resume respond to incoming external pull requests in approximately 13.7 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 63.1 places amruthpillai/reactive-resume in the A tier.
The external contributor pull request merge rate for amruthpillai/reactive-resume is 69.6%, based on public PR activity from non-core contributors.
amruthpillai/reactive-resume does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
Active maintainer team in amruthpillai/reactive-resume welcoming community pull requests and bug fixes.
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/amruthpillai/reactive-resume?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 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~9 hours (87% approval). Large PRs (>500 lines) take ~66 hours (31% approval). Keep your diff compact for rapid review.
Existing issue I searched the existing issues and could not find a matching proposal. Product variant Self-hosted Area API & integrations Problem I have some monitoring software that wants to be able to query the applications I run to check what version they're running and compare it to the "latest" published version. Right now there is no API endpoint that I can call (or that has published information about) that tells me what version of Reactive Resume is currently running. Desired outcome I'm flexible to the actual specifics about how this endpoint is created. The endpoint can be JSON, it can return other information (name of software, etc). This endpoint can authenticated or allow anonymous requests. There is already a /api/health endpoint. If you want to stick a "version": "x.y.z" in there, that's fine with me. Or you could create a new endpoint (maybe GET /api/about that returns { "service": "reactive-resume", "version": "x.y.z" }). Side note, /api/health isn't documented in t
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 amruthpillai/reactive-resume, 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 amruthpillai/reactive-resume acknowledge new external contributions in approximately 13 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 69.6% were successfully merged into the primary branch.
amruthpillai/reactive-resume has a recorded first-timer success rate of 80.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~13 hours. 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 63.1 places amruthpillai/reactive-resume in the Welcoming tier.
The external pull request merge rate is 69.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
amruthpillai/reactive-resume does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for amruthpillai/reactive-resume 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.