ip to location database by ASN, GeoFeed, Whois, iptoasn.com, db-ip lite, GeoLite2
C-Rank Grade: D (Risky) - 9/100
External PR Merge Rate: -
Response Time: 7d
First Timer Success: -
sapics/ip-location-db has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in sapics/ip-location-db respond to incoming external pull requests in approximately 172.4 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 9.2 places sapics/ip-location-db in the D tier.
The external contributor pull request merge rate for sapics/ip-location-db is 0.0%, based on public PR activity from non-core contributors.
sapics/ip-location-db currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
ip to location database by ASN, GeoFeed, Whois, iptoasn.com, db-ip lite, GeoLite2
Active JavaScript repository in sapics/ip-location-db with ongoing community development and issue triage.
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/sapics/ip-location-db?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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~112 hours (81% approval). Large PRs (>500 lines) take ~827 hours (29% approval). Keep your diff compact for rapid review.
I found this project when looking for alternatives to MaxMind's MMDBs for geoblocking in a reverse proxy. Commonly they seem to use a geoipupdate Docker image to periodically download MMDBs from MaxMind, but these require license credentials with them to use (even for the free version), and I would prefer not to have to deal with that, so I'm looking for a drop-in replacement for these databases instead. So I found this as one of the main alternatives for the databases themselves besides the commercially-backed options, but the MMDBs here are in a different format than what the libraries expect. Based on #34, it looks like the decision was made to produce them with a more flattened structure compared to MaxMind's schema? Although I've seen other MMDB sources with a similar structure, so maybe it's also related to legacy GeoLite format I don't know. But unfortunately it means anything expecting the current GeoLite2 schema format doesn't work properly with these files. Is there any chanc
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 sapics/ip-location-db, 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 sapics/ip-location-db acknowledge new external contributions in approximately 7 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
sapics/ip-location-db has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~7 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 9.2 places sapics/ip-location-db in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, sapics/ip-location-db 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 sapics/ip-location-db 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.