LinkedIn vs Perk

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

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

On code quality (the state of repositories, tests, releases and polish), LinkedIn is ahead of Perk. On community (issue response, PR reviews and discussion health), LinkedIn is ahead of Perk. On reach (how visible the ecosystem is beyond its own repos), LinkedIn is clearly ahead of Perk. On momentum (release cadence and how fast the ecosystem moves), Perk is ahead of LinkedIn.

LinkedIn carries 77,785 GitHub stars across 137 public repos, with 28 repositories active in the last 90 days and 52 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 LinkedIn's footprint is roughly 2287.8x larger, which usually shows up in downstream signals like inbound issues and third party integrations.

LinkedIn is the stronger read for anyone weighting reach. 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.