Skip to content

Scrape and parse search engine results using SerpApi.

active 2024-08-112026-05-18 (UTC)

Partial coverage14,612 / 17,731 hourly files (82%) · 2 absent upstream · 3,119 failed, retryable2024-08-022026-08-11 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
73
Pushes
12
Pull requests
2
Issues
8
Stars
19
Forks
3

Activity over time

Daily event counts in the loaded window

Line chart, 646 days from 2024-08-11 to 2026-05-18. Pushes: 12 total, peak 5 in a day. Pull requests: 2 total, peak 1 in a day. Issues: 8 total, peak 2 in a day. Comments: 20 total, peak 4 in a day. Stars: 19 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
zyc901212902
Ovi6004
hilmanski5004
marm1232001
Yokai10001000
juncas2205-debug1001
Yasaman-k1000
schaferyan1001
andreamr781000
kenrogers1010

Recent activity

Latest issues, pull requests and releases

  • Pull request#36kenrogers2026-03-28 21:09
  • Issue comment#34juncas2205-debug2026-03-15 11:04
    Timeout issues
  • Issue comment#35hilmanski2025-12-09 21:40
    Google Maps engine intermittently returns place_results_state: "Fully empty" for valid place_id
  • Issue comment#35hilmanski2025-12-09 07:50
    Google Maps engine intermittently returns place_results_state: "Fully empty" for valid place_id
  • Issue comment#32schaferyan2025-07-31 18:07
    Remove or Clarify "Using a Proxy" Section from the Readme
  • Issue comment#31zyc90122025-07-25 23:35
    Release 2.2.0 is broken due to missing files
  • Issue#31zyc90122025-07-25 23:35
    Release 2.2.0 is broken due to missing files
  • Issue comment#31PhatStraw2025-07-25 00:06
    Release 2.2.0 is broken due to missing files
  • Issue comment#31lh152025-07-24 17:45
    Release 2.2.0 is broken due to missing files
  • Issue comment#31Luluno012025-07-24 17:35
    Release 2.2.0 is broken due to missing files
  • Issue comment#31hilmanski2025-07-24 08:49
    Release 2.2.0 is broken due to missing files
  • Issue comment#31Mramzan9872025-07-24 07:45
    Release 2.2.0 is broken due to missing files
  • Issue#31Luluno012025-07-24 04:37
    Release 2.2.0 is broken due to missing files
  • Issue#27zyc90122025-07-24 01:47
    Feature Request: Support HTTPS_PROXY / HTTP_PROXY / NO_PROXY environment variables for proxying
  • Pull request#29zyc90122025-07-24 01:47
  • Issue comment#30marm1232025-04-06 21:28
    Profiles are not returned in knowledge_graph response when doing searches.
  • Issue#30marm1232025-04-06 21:28
    Profiles are not returned in knowledge_graph response when doing searches.
  • Issue#30Yokai10002025-04-05 14:36
    Profiles are not returned in knowledge_graph response when doing searches.
  • Issue comment#27zyc90122025-04-02 01:03
    Feature Request: Support HTTPS_PROXY / HTTP_PROXY / NO_PROXY environment variables for proxying
  • Issue comment#25hilmanski2025-03-21 05:15
    Uncaught (in promise) TypeError: import_querystring.default.stringify is not a function
  • Issue#25hilmanski2025-03-21 05:15
    Uncaught (in promise) TypeError: import_querystring.default.stringify is not a function
  • Issue#25andreamr782025-03-21 04:23
    Uncaught (in promise) TypeError: import_querystring.default.stringify is not a function
  • Issue comment#21hilmanski2025-03-04 02:49
    (Frontend Issue) Unhandled Runtime Error TypeError: Failed to fetch on React and Next JS
  • Issue#24Yasaman-k2024-11-03 11:59
    Module not found: Error: Can't resolve 'https'

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