Google Workspace vs Perk

Google Workspace (Developer samples for Google Workspace APIs) and Perk (We're fixing business travel.) both appear on the Smoower Developer Ecosystem Index.

Google Workspace (rank #165) holds a modest lead over Perk (rank #372) on the overall Smoower ecosystem score (51 vs 42). The gap of 9 points reflects composite signals across code, docs, community and reach.

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

Google Workspace carries 48,567 GitHub stars across 57 public repos, with 18 repositories active in the last 90 days and 37 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 Google Workspace's footprint is roughly 1428.4x larger, which usually shows up in downstream signals like inbound issues and third party integrations.

Google Workspace is the stronger read for anyone weighting code quality. Perk makes more sense for teams already using its adjacent tools. The table below breaks the scores down pillar by pillar; the linked profiles cover the underlying repos, docs and community signals in full.