Official examples and tools from the JACK project
active 2024-12-21 → 2026-03-21 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 456 days from 2024-12-21 to 2026-03-21. Pushes: 0 total, peak 0 in a day. Pull requests: 1 total, peak 1 in a day. Issues: 5 total, peak 2 in a day. Comments: 5 total, peak 4 in a day. Stars: 5 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
Recent activity
Latest issues, pull requests and releases
- Issue#96jpka-2025-05-03 11:18[minor] capture_client.c: -Wshadow warning
- Issue comment#93riban-bw2025-02-01 12:26zalsa internal client crashes if alsa device has disappeared
- Issue comment#94farshield2025-02-01 10:57zalsa_in/zalsa_out plugins select wrong default resampling quality
- Pull request#95farshield2025-02-01 10:55
- Issue#94farshield2025-02-01 10:41zalsa_in/zalsa_out plugins select wrong default resampling quality
- Issue comment#93farshield2025-02-01 10:35zalsa internal client crashes if alsa device has disappeared
- Issue comment#91farshield2025-02-01 10:31zalsa plugin not working with Loopback ALSA device
- Issue#91farshield2025-02-01 10:31zalsa plugin not working with Loopback ALSA device
- Issue comment#93riban-bw2025-01-09 08:34zalsa internal client crashes if alsa device has disappeared
- Issue#93riban-bw2025-01-09 08:27zalsa internal client crashes if alsa device has disappeared
- Issue#92riban-bw2025-01-09 07:01Feature: Ability for zalsa to auto detect quantity of channels
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 5 stars here means stars gained during the window, not the repo's star count.