Skip to content

tomayac/local-reverse-geocoder

View on GitHub ↗Related repositories →

Local reverse geocoder for Node.js based on GeoNames data

active 2023-08-262026-06-13 (UTC)

Complete coverage26,491 / 26,491 hourly files (100%) · 2 absent upstream2023-08-152026-08-22 (UTC)
Events
90
Pushes
4
Pull requests
6
Issues
12
Stars
38
Forks
10

Activity over time

Daily event counts in the loaded window

Line chart, 1023 days from 2023-08-26 to 2026-06-13. Pushes: 4 total, peak 2 in a day. Pull requests: 6 total, peak 2 in a day. Issues: 12 total, peak 3 in a day. Comments: 18 total, peak 4 in a day. Stars: 38 total, peak 2 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
tomayac19428
junglebells3002
eligrifel3001
nhumble-sa3021
YanWittmann3002
shivamsaxenadev2001
devanjith2020
chad-vanet2001
yjwong1001
riccardoratta1001
TomerPapaya1000

Recent activity

Latest issues, pull requests and releases

  • Issue comment#88tomayac2025-02-10 18:35
    UnhandledPromiseRejectionWarning: Not supported - Cannot initialize container
  • Issue#88tomayac2025-02-10 18:35
    UnhandledPromiseRejectionWarning: Not supported - Cannot initialize container
  • Issue comment#88YanWittmann2025-02-10 18:02
    UnhandledPromiseRejectionWarning: Not supported - Cannot initialize container
  • Issue comment#88tomayac2025-02-10 07:34
    UnhandledPromiseRejectionWarning: Not supported - Cannot initialize container
  • Issue comment#88YanWittmann2025-02-09 13:01
    UnhandledPromiseRejectionWarning: Not supported - Cannot initialize container
  • Issue#88YanWittmann2025-02-09 12:53
    UnhandledPromiseRejectionWarning: Not supported - Cannot initialize container
  • Issue comment#87chad-vanet2024-08-19 11:48
    CSV_RECORD_INCONSISTENT_FIELDS_LENGTH
  • Issue#87tomayac2024-08-19 11:14
    CSV_RECORD_INCONSISTENT_FIELDS_LENGTH
  • Issue#87chad-vanet2024-08-19 11:10
    CSV_RECORD_INCONSISTENT_FIELDS_LENGTH
  • Issue comment#86riccardoratta2024-08-07 12:52
    admin1Code, admin2Code are returned as string instead of object in API response
  • Issue comment#86shivamsaxenadev2024-07-25 10:38
    admin1Code, admin2Code are returned as string instead of object in API response
  • Issue comment#86tomayac2024-07-22 12:50
    admin1Code, admin2Code are returned as string instead of object in API response
  • Issue#86shivamsaxenadev2024-07-19 06:09
    admin1Code, admin2Code are returned as string instead of object in API response
  • Issue comment#85nhumble-sa2024-01-16 22:21
    ECT-1803 Security Updates
  • Pull request#85nhumble-sa2024-01-16 22:21
  • Pull request#85nhumble-sa2024-01-16 22:20
  • Issue comment#84eligrifel2024-01-08 17:04
    when chossing specific country result are wrong
  • Issue comment#84tomayac2024-01-08 17:00
    when chossing specific country result are wrong
  • Issue#84tomayac2024-01-08 17:00
    when chossing specific country result are wrong
  • Pull request#80tomayac2024-01-08 17:00
  • Issue#82tomayac2024-01-08 16:58
    Types mismatch
  • Issue comment#83tomayac2024-01-08 16:51
    citiesFileOverride ignored when choosing specific country
  • Issue#83tomayac2024-01-08 16:51
    citiesFileOverride ignored when choosing specific country
  • Issue comment#84tomayac2024-01-08 12:03
    when chossing specific country result are wrong
  • Issue#84eligrifel2024-01-01 17:12
    when chossing specific country result are wrong

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 38 stars here means stars gained during the window, not the repo's star count.