Maps and turn-by-turn navigation for Android without Google Play Services: the best of open map data, with Google lookups by choice. Runs on degoogled phones and can avoid Flock cameras
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 71%
Response Time: -
First Timer Success: 50%
PimpinPumpkin/Vela has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in PimpinPumpkin/Vela respond to incoming external pull requests in approximately 0.0 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 64.3 places PimpinPumpkin/Vela in the A tier.
The external contributor pull request merge rate for PimpinPumpkin/Vela is 70.6%, based on public PR activity from non-core contributors.
PimpinPumpkin/Vela currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in PimpinPumpkin/Vela. Prompt code reviews with positive guidance for new contributors.
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/PimpinPumpkin/Vela?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 19:00 to 23:00 UTC (19:00 - 23:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (88% approval). Large PRs (>500 lines) take ~115 hours (32% approval). Keep your diff compact for rapid review.
What you want Would be interesting to investigate if their API can be used for traffic info (traffic-aware routing). They have quite good traffic data but lack other things that Google Maps has like the extensive POI info or streetview. Why? The app would be just a bit more degoogled. Why it matters No response Keyless reality check No response
EDIT October 3rd, 2026 Here's where every install method stands right now. Find your phone's column: How you install Vela Stock Android, or a ROM with Google apps GrapheneOS (sandboxed Play) Rooted, any ROM Plain install + Android Auto "Unknown sources" ❌ ❌ ❌ KingInstaller, "Google installer" method (no root) ✅ ❌ (GrapheneOS has no Google installer) ✅ KingInstaller, Shizuku method ✅ on an aftermarket head unit, not tested in a car ❌ not tested AAEnabler (no root) ✅ ❌ not tested PlayInstaller by @alltechdev (ARS18), installs as Play using root needs root needs root ✅ adb install -i com.android.vending ❌ ❌ ❌ Gearslip by @Seb3thehacker, an Android Auto replacement on the phone (no Google software, no root) ✅ cars before ~2020 ✅ cars before ~2020 ✅ cars before ~2020 Stock: you need a Google account signed in to the Play Store. GrapheneOS: still investigating. No install method has passed a real car's check yet (Gearslip sidesteps the
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 PimpinPumpkin/Vela, 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 PimpinPumpkin/Vela acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.6% were successfully merged into the primary branch.
PimpinPumpkin/Vela has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 64.3 places PimpinPumpkin/Vela in the Welcoming tier.
The external pull request merge rate is 70.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, PimpinPumpkin/Vela currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for PimpinPumpkin/Vela 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.