Qonto vs SlackAPI

Qonto and SlackAPI (https://docs.slack.dev/tools) both appear on the Smoower Developer Ecosystem Index.

SlackAPI (rank #47) holds a modest lead over Qonto (rank #338) on the overall Smoower ecosystem score (61 vs 43). The gap of 18 points reflects composite signals across code, docs, community and reach.

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

Qonto carries 501 GitHub stars across 75 public repos, with 11 repositories active in the last 90 days and 5 external contributors on record. SlackAPI shows 17,894 stars across 37 public repos, 19 active in the last 90 days and 39 external contributors. The star gap on its own does not decide the comparison, but SlackAPI's footprint is roughly 35.7x larger, which usually shows up in downstream signals like inbound issues and third party integrations.

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