Activity
Stars and mentions · Last 30 days, Oct 5 – Nov 3
Top repositories
koalaman’s repositories ranked by pull request authors, as on trending.
Contributes to
Repositories outside koalaman’s account where koalaman opened or reviewed pull requests in the past 365 days.
Who noticed koalaman
Everyone who starred or forked koalaman’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 koalaman owns. Select an award to embed its badge.
No awards yet
Repositories earn awards by reaching the top three in a completed trending day or week.
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
That Bash script runs, but is it safe from common mistakes? 🐚 ShellCheck flags risky patterns and suggests fixes. Use it in your editor or CI. ✅ koalaman/shellcheck #Bash #浇朋友 #蓝朋友 #互关 #fo
Shell 脚本能跑，不代表没坑。🐚 ShellCheck 会指出常见语法与潜在逻辑问题，还能接入编辑器和 CI。写 Bash 前先检查。✅ koalaman/shellcheck #Bash #浇朋友 #蓝朋友 #互关 #fo
AI attempts to licensewash another big project The latest victim (that I'm aware of) is shellcheck (a gplv3 project) by shuck (a MIT project). Look, I'm not a lawyer and I don't know if it's even necessary to have clean-room separation in a case like this. But the project apparently thought it was a good idea to say "shuck is not a port of ShellCheck. It is a clean-room reimplementation." There is even a CLEAN_ROOM.md stating "prohibited inputs" include the shellcheck source code, shellcheck documentation, shellcheck output, and more. The wrinkle, of course, is that it was written in six months with agents whose models were almost certainly trained extensively on all of those supposedly "prohibited inputs". How does one defend calling this a clean-room implementation with impossibly prohibited inputs? Maybe there will be an answer.