ColossalAI vs zju-icicles

ColossalAI and zju-icicles share 7 technologies: seaborn, matplotlib, scikit-learn, torch, timm, torchvision, and pillow. ColossalAI is written in Python and zju-icicles in HTML.

Read it as markdown

What they share and what sets them apart

Side by side

SizeLines written by people and agents, without generated ones; code files, without tests.
ColossalAI317,403 lines written974 code files
zju-icicles41,446 lines written122 code files
Who writes itA commit counts as AI's when it carries its signature: a Co-Authored-By line, its author name or the merge of its branch.
ColossalAI0.3% of its commits signed by AIWith Codex and Claude Code
zju-icicles0% of its commits signed by AI
ActivityFrom GitHub and its history, on the day SeeRepo read it.
ColossalAILast push November 6, 20263,887 commits41,430 stars
zju-iciclesLast push September 7, 20261,136 commits41,363 stars
TestsThe files that test the code, and the share of code files a test imports.
ColossalAI505 test files1.1% of its code files have a test that imports them
zju-icicles0 test files

Frequently asked questions

Which is bigger, ColossalAI or zju-icicles?
ColossalAI, with 317,403 lines written; zju-icicles has 41,446.

The proof: hpcaitech/ColossalAI's code at commit da8f5c2

Which has more GitHub stars, ColossalAI or zju-icicles?
ColossalAI, with 41,430 stars; zju-icicles has 41,363.

The proof: hpcaitech/ColossalAI on GitHub

Which has more tests, ColossalAI or zju-icicles?
ColossalAI, with 505 test files.

The proof: hpcaitech/ColossalAI's code at commit da8f5c2

Which was updated more recently, ColossalAI or zju-icicles?
ColossalAI: its last push was on November 6, 2026, and zju-icicles's on September 7, 2026.

The proof: hpcaitech/ColossalAI's commits on GitHub

Which has more commits signed by AI, ColossalAI or zju-icicles?
ColossalAI: an AI signed 0.3% of its commits, with Codex and Claude Code.

See inside your code, today.

Paste your repo and see it drawn, part by part: a medium one in under a minute.

Free, no account.

Or look inside SeeRepo's own →