Skip to content

NodeJs CLI tools to search keywords in find across all your project

active 2023-09-072026-04-08 (UTC)

Complete coverage26,586 / 26,586 hourly files (100%) · 2 absent upstream2023-08-152026-08-26 (UTC)
Events
62
Pushes
6
Pull requests
5
Issues
6
Stars
23
Forks
5

Activity over time

Daily event counts in the loaded window

Line chart, 945 days from 2023-09-07 to 2026-04-08. Pushes: 6 total, peak 2 in a day. Pull requests: 5 total, peak 1 in a day. Issues: 6 total, peak 2 in a day. Comments: 13 total, peak 6 in a day. Stars: 23 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
ldbglobe13612
bytehead7006
nis2674004
rcasia2020
syoma7551000
ilyesAj1010
fliespl1000
hilenko1001
johndoe-foobar1000
datawookie1010

Recent activity

Latest issues, pull requests and releases

  • Issue#9syoma7552026-03-14 13:39
    Any option to search in branches?
  • Issue#8johndoe-foobar2025-03-31 13:40
    CLI-style interface
  • Issue#6ldbglobe2025-02-14 13:38
    Possibility to search group recursively?
  • Issue#5ldbglobe2025-02-14 13:38
    Always runs into HTTPError: Response code 401
  • Issue comment#4hilenko2025-01-22 09:13
    fix: Add installation step
  • Pull request#7rcasia2024-09-27 01:31
  • Pull request#7rcasia2024-08-16 17:59
  • Issue#6fliespl2024-08-10 20:06
    Possibility to search group recursively?
  • Issue comment#5bytehead2024-07-30 13:51
    Always runs into HTTPError: Response code 401
  • Issue comment#5nis2672024-07-30 13:49
    Always runs into HTTPError: Response code 401
  • Issue comment#5bytehead2024-07-30 13:43
    Always runs into HTTPError: Response code 401
  • Issue comment#5bytehead2024-07-30 13:41
    Always runs into HTTPError: Response code 401
  • Issue comment#5nis2672024-07-30 13:39
    Always runs into HTTPError: Response code 401
  • Issue comment#5nis2672024-07-30 13:27
    Always runs into HTTPError: Response code 401
  • Issue comment#5ldbglobe2024-07-29 14:55
    Always runs into HTTPError: Response code 401
  • Issue comment#5bytehead2024-07-29 11:47
    Always runs into HTTPError: Response code 401
  • Issue comment#5bytehead2024-07-29 11:38
    Always runs into HTTPError: Response code 401
  • Issue comment#5ldbglobe2024-07-29 11:22
    Always runs into HTTPError: Response code 401
  • Issue comment#5bytehead2024-07-29 09:08
    Always runs into HTTPError: Response code 401
  • Issue comment#5nis2672024-07-25 15:01
    Always runs into HTTPError: Response code 401
  • Issue#5bytehead2024-07-03 11:25
    Always runs into HTTPError: Response code 401
  • Pull request#4datawookie2024-03-25 12:46
  • Pull request#3ldbglobe2024-03-15 08:12
  • Pull request#3ilyesAj2024-03-07 15:48

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