Amplitude vs Perk

Amplitude and Perk (We're fixing business travel.) both appear on the Smoower Developer Ecosystem Index.

Amplitude (rank #93) holds a modest lead over Perk (rank #372) on the overall Smoower ecosystem score (56 vs 42). The gap of 14 points reflects composite signals across code, docs, community and reach.

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

Amplitude carries 3,167 GitHub stars across 151 public repos, with 39 repositories active in the last 90 days and 23 external contributors on record. Perk shows 34 stars across 25 public repos, 5 active in the last 90 days and 6 external contributors. The star gap on its own does not decide the comparison, but Amplitude's footprint is roughly 93.1x larger, which usually shows up in downstream signals like inbound issues and third party integrations.

Amplitude is the stronger read for anyone weighting code quality. Perk 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.