active 2023-09-12 → 2025-12-29 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 840 days from 2023-09-12 to 2025-12-29. Pushes: 99 total, peak 6 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 33 total, peak 3 in a day. Comments: 4 total, peak 2 in a day. Stars: 2 total, peak 1 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
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| robinbourianes-kalisio | 64 | 42 | 0 | 3 |
| claustres | 47 | 39 | 0 | 1 |
| cnouguier | 20 | 14 | 0 | 0 |
| tristan-greffe | 4 | 3 | 0 | 0 |
| scolbert-lisbona-kalisio | 1 | 1 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue#20robinbourianes-kalisio2025-12-10 10:47Update package.json to use node-geocoder on specific commit, otherwise opendatafrance source will stop working
- Issue#18robinbourianes-kalisio2025-05-23 07:07Add an endpoint to request a batch of positions for reverse geocoding
- Issue#16cnouguier2025-04-01 15:46The Kano provider should be able to handle contextual remote services
- Issue#17cnouguier2025-04-01 13:15Allow providing a baseQuery to the find query emitted by the Kano provider
- Issue#16cnouguier2025-03-27 15:29The Kano provider should be able to handle contextual remote services
- Issue#5robinbourianes-kalisio2025-03-27 09:09Distribution healthcheck endpoint is not reachable
- Issue#15robinbourianes-kalisio2025-03-26 16:15MBTiles provider does not filter results properly when multiple layers are in the same dataset
- Issue#11robinbourianes-kalisio2025-01-30 14:01Geokoder provider does not yet support limit query parameter
- Issue#14robinbourianes-kalisio2025-01-30 14:01`limit` query parameter should represent the max number of results we get from a query
- Issue#14robinbourianes-kalisio2025-01-29 11:08`limit` query parameter should represent the max number of results we get from a query
- Issue#13robinbourianes-kalisio2025-01-17 18:55MBTiles provider assumes that all layers have the same max zoom level
- Issue#13robinbourianes-kalisio2025-01-17 18:54MBTiles provider assumes that all layers have the same max zoom level
- Issue#12robinbourianes-kalisio2025-01-16 12:08MBTiles provider throws an error and fails to probe remaining datasets when searching for an out of bound tile.
- Issue#12robinbourianes-kalisio2025-01-16 12:05MBTiles provider throws an error and fails to probe remaining datasets when searching for an out of bound tile.
- Issue#11robinbourianes-kalisio2025-01-10 08:06Geokoder provider does not yet support limit query parameter
- Issue#10robinbourianes-kalisio2025-01-09 15:31Kano provider may expose duplicated sources
- Issue#10robinbourianes-kalisio2025-01-09 14:52Kano provider may expose duplicated sources
- Issue#9robinbourianes-kalisio2024-12-18 13:08Add ability to limit forward geocoding results to a bounding box
- Issue comment#9robinbourianes-kalisio2024-12-18 13:06Add ability to limit forward geocoding results to a bounding box
- Issue#9robinbourianes-kalisio2024-12-18 13:05Add ability to limit forward geocoding results to a bounding box
- Issue#3robinbourianes-kalisio2024-09-10 14:32Provide a geokoder provider
- Issue comment#8robinbourianes-kalisio2024-07-23 09:32Upgrade to NodeJS v20
- Issue#8robinbourianes-kalisio2024-07-23 09:32Upgrade to NodeJS v20
- Issue comment#8robinbourianes-kalisio2024-07-23 09:23Upgrade to NodeJS v20
- Issue#8robinbourianes-kalisio2024-07-23 09:22Upgrade to NodeJS v20
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 2 stars here means stars gained during the window, not the repo's star count.