Client Scripts for using a Crypt Keeper Server
active 2024-02-07 → 2024-06-29 (UTC)
Partial coverage20,507 / 26,263 hourly files (78%) · 2 absent upstream · 5,753 failed, retryable2023-08-15 → 2026-08-13 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
46
Pushes
34
Pull requests
0
Issues
4
Stars
0
Forks
0
Activity over time
Daily event counts in the loaded window
Line chart, 144 days from 2024-02-07 to 2024-06-29. Pushes: 34 total, peak 9 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 4 total, peak 4 in a day. Comments: 2 total, peak 2 in a day. Stars: 0 total, peak 0 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
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| huths0lo | 40 | 34 | 0 | 2 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#2huths0lo2024-02-07 22:56Fix code scanning alert - Use of a broken or weak cryptographic hashing algorithm on sensitive data
- Issue#2huths0lo2024-02-07 22:56Fix code scanning alert - Use of a broken or weak cryptographic hashing algorithm on sensitive data
- Issue#2huths0lo2024-02-07 22:56Fix code scanning alert - Use of a broken or weak cryptographic hashing algorithm on sensitive data
- Issue comment#1huths0lo2024-02-07 22:49Fix code scanning alert - Use of a broken or weak cryptographic hashing algorithm on sensitive data
- Issue#1huths0lo2024-02-07 22:49Fix code scanning alert - Use of a broken or weak cryptographic hashing algorithm on sensitive data
- Issue#1huths0lo2024-02-07 22:49Fix code scanning alert - Use of a broken or weak cryptographic hashing algorithm on sensitive data
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.