Activity
Stars and mentions · Last 30 days, Oct 5 – Nov 3
Top repositories
hatchet-dev’s repositories ranked by new stars, as on trending.
Contributes to
Repositories outside hatchet-dev’s account where hatchet-dev opened or reviewed pull requests in the past 365 days.
Who noticed hatchet-dev
Everyone who starred or forked hatchet-dev’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.
Achievements
Awards earned by the repositories hatchet-dev owns. Select an award to embed its badge.
- Gold
- 11st place finishes
- Silver
- 02nd place finishes
- Bronze
- 03rd place finishes
- Awarded repositories
- 1Owned by hatchet-dev now
Repositories
Ordered by gold, then silver, then bronze.
- hatchetBest: 1st by stars, 756 stars100
Every award
Top-three finishes of these repositories in completed trending days and weeks, newest first.
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
@abelanger5 @crimebucket Thank you for the side by side. It shows that Claude did find the fix, but then packed 625 more lines of irrelevant stuff around it - the coherence argument on display hatchet#4734
@crimebucket wait, you want screenshots of the entire diff? it'd literally just be pages of code which no one here would have context on. but we're open source, you can evaluate them yourself: - hatchet#4733 - hatchet#4734
@crimebucket @abelanger5 i went to read the PRs, and tbh I don't know what you expected. it's the same Claude as always hatchet#4733 and hatchet#4734 tldr: the PR had the same human fix, but with a janky, imperative if/else scheduler on top. oh, Claude.