360Learning vs Clio

360Learning (Learning Engagement Platform) and Clio both appear on the Smoower Developer Ecosystem Index.

360Learning and Clio sit at essentially the same overall ecosystem score (33), which is unusual and worth reading through the pillars below.

On code quality (the state of repositories, tests, releases and polish), Clio is ahead of 360Learning. On education (docs, guides and learning material for developers), Clio is clearly ahead of 360Learning. On community (issue response, PR reviews and discussion health), 360Learning is slightly ahead of Clio. On reach (how visible the ecosystem is beyond its own repos), 360Learning is ahead of Clio. On momentum (release cadence and how fast the ecosystem moves), Clio is clearly ahead of 360Learning.

360Learning carries 120 GitHub stars across 10 public repos, with 2 repositories active in the last 90 days and 1 external contributors on record. Clio shows 518 stars across 19 public repos, 4 active in the last 90 days and 3 external contributors. The star gap on its own does not decide the comparison, but Clio's footprint is roughly 4.3x larger, which usually shows up in downstream signals like inbound issues and third party integrations.

360Learning is the stronger read for anyone weighting reach. Clio looks better where education is the deciding factor. The table below breaks the scores down pillar by pillar; the linked profiles cover the underlying repos, docs and community signals in full.