Skip to content

UT based automated fuzz driver generation

active 2023-08-172025-08-07 (UTC)

Partial coverage20,516 / 26,272 hourly files (78%) · 2 absent upstream · 5,753 failed, retryable2023-08-152026-08-13 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
102
Pushes
13
Pull requests
7
Issues
8
Stars
34
Forks
9

Activity over time

Daily event counts in the loaded window

Line chart, 722 days from 2023-08-17 to 2025-08-07. Pushes: 13 total, peak 4 in a day. Pull requests: 7 total, peak 3 in a day. Issues: 8 total, peak 2 in a day. Comments: 14 total, peak 3 in a day. Stars: 34 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
yuweol22856
sole28012
kj26486510
musangk5001
vsecv3001
AxelHowe2001
YancyLii2002
DUT-ShiLongYu2001

Recent activity

Latest issues, pull requests and releases

  • Pull request#34yuweol2024-12-31 06:53
  • Pull request#34yuweol2024-12-31 05:45
  • Issue comment#33DUT-ShiLongYu2024-10-28 06:31
    Can UTopia be applied to C++ projects that do not use a testing framework?
  • Issue#33DUT-ShiLongYu2024-10-23 01:40
    Can UTopia be applied to C++ projects that do not use a testing framework?
  • Pull request#32kj26482024-07-25 07:45
  • Issue comment#31AxelHowe2024-05-31 07:16
    How UTopia generate code coverage?
  • Issue#31AxelHowe2024-05-31 05:53
    How UTopia generate code coverage?
  • Issue#30yuweol2024-05-24 00:39
    Support LLVM 17
  • Issue comment#29yuweol2024-05-13 00:08
    Experimental reproduction
  • Issue comment#29YancyLii2024-05-10 10:44
    Experimental reproduction
  • Issue comment#29YancyLii2024-05-10 10:43
    Experimental reproduction
  • Issue comment#29yuweol2024-05-10 06:18
    Experimental reproduction
  • Issue comment#29yuweol2024-05-09 06:16
    Experimental reproduction
  • Pull request#28yuweol2024-05-02 06:52
  • Issue comment#27vsecv2024-04-02 06:58
    How to create a test case to recreate a collision
  • Issue#27vsecv2024-04-02 06:04
    How to create a test case to recreate a collision
  • Issue comment#26yuweol2024-03-25 00:52
    Where can I find a built fuzz driver?
  • Issue#26yuweol2024-03-25 00:52
    Where can I find a built fuzz driver?
  • Issue#25vsecv2024-03-21 07:55
    helper : autofuzz_base error
  • Issue comment#23sole22024-03-20 02:55
    How to test the generated driver? The code coverage I received differs significantly from that in the paper
  • Issue#23sole22024-03-20 02:55
    How to test the generated driver? The code coverage I received differs significantly from that in the paper
  • Issue comment#21sole22024-03-20 02:55
    Running the code "make -s jstest"(a part of "make -j16 check" of "make node") gives many errors.
  • Issue#21sole22024-03-20 02:55
    Running the code "make -s jstest"(a part of "make -j16 check" of "make node") gives many errors.
  • Pull request#22sole22024-03-20 02:51
  • Pull request#24yuweol2024-03-20 02:29

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