Stars and mentions
Last 30 days, Oct 4 – Nov 2
Package downloads
Top repositories
Arinerron’s repositories ranked by new forks, as on trending.
Contributes to
Repositories outside Arinerron’s account where Arinerron opened or reviewed pull requests in the past 365 days.
Who noticed Arinerron
Everyone who starred or forked Arinerron’s repositories since the archive began in 2011.
Notable accounts
Ordered by the stars their own repositories have received.
Biggest fans
Accounts that starred the most of these repositories.
Breakout weeks
Each repository’s best week of new stars, with the release published around it.
- Gold
- 01st place finishes
- Silver
- 02nd place finishes
- Bronze
- 03rd place finishes
- Awarded repositories
- 0Owned by Arinerron now
No trending awards yet
None of the repositories Arinerron owns has finished in the top three of a completed trending day or week, by stars, forks or PR authors. See who is trending now.
A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.
Mentions
Show HN: whytime: time(1) that tells you where the wall-clock time went time says a command took 3.8 seconds... whytime tells you where those seconds went: $ sudo whytime -- sh -c 'sleep 0.5; dd … oflag=dsync; curl -s -o /dev/null https://speed.cloudflare.com/…' wall 3.83s 47% blocked on network: speed.cloudflare.com:443 (1 connection) 34% fsync on ~/.cache 13% timer sleep (sleep) 4% on-CPU (curl) 2% other The lines always add up to 100%. When the command waits on a child or another thread, whytime follows whoever woke it up, so a shell waiting on curl is charged to the network wait curl was stuck on. The top line is what you'd have to make faster. It can also draw a flamegraph. Uses eBPF (Linux 5.18+)