Bazel rules for CodeChecker
active 2026-02-12 → 2026-08-08 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 178 days from 2026-02-12 to 2026-08-08. Pushes: 18 total, peak 2 in a day. Pull requests: 6 total, peak 2 in a day. Issues: 3 total, peak 1 in a day. Comments: 17 total, peak 3 in a day. Stars: 0 total, peak 0 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
Recent activity
Latest issues, pull requests and releases
- Issue#15Szelethus2026-07-27 12:25code_checker does not produce output on tensorflow
- Pull request#231furtib2026-06-06 19:30
- Pull request#231furtib2026-06-06 19:30
- Issue#86furtib2026-06-04 12:25On the per_file rule default arguments and user given arguments are not merged correctly
- Pull request#220nettle2026-04-09 17:42
- Issue comment#209nettle2026-03-28 20:21Prototype Bazel-native FOSS tests
- Pull request#159furtib2026-03-17 11:12
- Issue comment#201furtib2026-02-27 15:01Undo last change to clang.bzl
- Issue comment#171furtib2026-02-24 07:10Add pylint
- Pull request#196furtib2026-02-23 09:08
- Issue#173furtib2026-02-13 11:39Follow bazel rule nameing conventions
- Pull request#191furtib2026-02-13 11:39
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.