Paddle vs Perk

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

Paddle and Perk sit at essentially the same overall ecosystem score (42), which is unusual and worth reading through the pillars below.

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

Paddle carries 997 GitHub stars across 54 public repos, with 22 repositories active in the last 90 days and 6 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 Paddle's footprint is roughly 29.3x larger, which usually shows up in downstream signals like inbound issues and third party integrations.

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