active 2024-09-06 → 2024-09-08 (UTC)
Partial coverage19,067 / 24,543 hourly files (78%) · 2 absent upstream · 5,473 failed, retryable2023-10-25 → 2026-08-12 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
10
Pushes
1
Pull requests
0
Issues
0
Stars
1
Forks
0
Activity over time
Daily event counts in the loaded window
Line chart, 3 days from 2024-09-06 to 2024-09-08. Pushes: 1 total, peak 1 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 0 total, peak 0 in a day. Comments: 7 total, peak 3 in a day. Stars: 1 total, peak 1 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
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 comment#11ArvellonB2024-09-08 00:27Combine the keyring pass backend and a n-year long gpg's cache expiry time is a potential vulnerability
- Issue comment#11ArvellonB2024-09-07 23:35Combine the keyring pass backend and a n-year long gpg's cache expiry time is a potential vulnerability
- Issue comment#11ArvellonB2024-09-07 23:33Combine the keyring pass backend and a n-year long gpg's cache expiry time is a potential vulnerability
- Issue comment#11taariq2024-09-07 16:53Combine the keyring pass backend and a n-year long gpg's cache expiry time is a potential vulnerability
- Issue comment#10ArvellonB2024-09-06 18:04Please build a native aarch64 docker image
- Issue comment#11ArvellonB2024-09-06 17:53Combine the keyring pass backend and a n-year long gpg's cache expiry time is a potential vulnerability
- Issue comment#11alessio2024-09-06 16:46Combine the keyring pass backend and a n-year long gpg's cache expiry time is a potential vulnerability
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 1 stars here means stars gained during the window, not the repo's star count.