Perk vs Typeform

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

Typeform (rank #189) holds a narrow lead over Perk (rank #372) on the overall Smoower ecosystem score (50 vs 42). The gap of 8 points reflects composite signals across code, docs, community and reach.

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

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

Perk is the stronger read for anyone weighting momentum. Typeform looks better where code quality 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.