Skip to content

active 2024-05-302026-04-15 (UTC)

Partial coverage15,755 / 19,543 hourly files (81%) · 2 absent upstream · 3,787 failed, retryable2024-05-192026-08-11 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
29
Pushes
0
Pull requests
0
Issues
15
Stars
2
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 686 days from 2024-05-30 to 2026-04-15. Pushes: 0 total, peak 0 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 15 total, peak 2 in a day. Comments: 12 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

ContributorContributionsPushesPRsComments
marijnh200011
stuffaboutpete2001
drgrice11000
lie-yan1000
unconed1000
wherewhere1000
vectronic1000

Recent activity

Latest issues, pull requests and releases

  • Issue comment#9marijnh2026-04-15 06:50
    Generating lezer grammar from tree-sitter grammar?
  • Issue comment#54marijnh2026-04-15 06:50
    Getting the term names for static type checking
  • Issue#67marijnh2026-03-27 08:27
    How to parse async-ly
  • Issue comment#67marijnh2026-03-27 08:27
    How to parse async-ly
  • Issue#67wherewhere2026-03-27 08:13
    How to parse async-ly
  • Issue#65vectronic2025-12-09 08:59
    Change in parse result nesting when adding a single character to a comment
  • Issue#64marijnh2025-11-28 13:56
    Parsing fails with extra newline characters
  • Issue#64marijnh2025-11-19 14:40
    Parsing fails with extra newline characters
  • Issue#64marijnh2025-11-18 07:31
    Parsing fails with extra newline characters
  • Issue comment#64marijnh2025-11-18 07:31
    Parsing fails with extra newline characters
  • Issue#63marijnh2025-09-02 20:31
    Can Lezer generate TextMate syntax tokenizers?
  • Issue comment#62marijnh2025-08-10 08:11
    abnormal code in the `common` library
  • Issue#62lie-yan2025-08-10 02:15
    abnormal code in the `common` library
  • Issue comment#61marijnh2024-12-22 18:39
    Is there a way to tell the parser not to attempt a certain recovery path?
  • Issue#61marijnh2024-12-22 18:39
    Is there a way to tell the parser not to attempt a certain recovery path?
  • Issue#61stuffaboutpete2024-12-22 11:41
    Is there a way to tell the parser not to attempt a certain recovery path?
  • Issue#58unconed2024-08-07 20:34
    Error nodes - Regression in 1.3.13+
  • Issue comment#58marijnh2024-08-07 20:08
    Error nodes - Regression in 1.3.13+
  • Issue comment#55marijnh2024-07-27 09:28
    Regression in 1.4.1
  • Issue#55marijnh2024-07-27 09:27
    Regression in 1.4.1
  • Issue comment#57marijnh2024-07-25 06:34
    Javascript keyword `eval` issue
  • Issue comment#56stuffaboutpete2024-07-24 22:47
    Is there no way to identify which missing token(s) triggered an error node?
  • Issue#57drgrice12024-07-24 22:09
    Javascript keyword `eval` issue
  • Issue comment#56marijnh2024-07-24 20:19
    Is there no way to identify which missing token(s) triggered an error node?
  • Issue#56marijnh2024-07-24 20:19
    Is there no way to identify which missing token(s) triggered an error node?

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.