The rate of change of GitHub star growth — a community-interest signal used in Scout Score and acceleration detection.
The rate of change of GitHub star growth — a community-interest signal used in Scout Score and acceleration detection.
Star acceleration is the second derivative of a repository's GitHub star count: not how many stars the project has, but how fast the rate of starring is growing. A project going from 10 to 50 stars/week is accelerating; one going from 100 to 105 is linear or plateauing. Acceleration catches breakout interest before absolute numbers do.
Star acceleration is a community confirmation signal. A startup with rising commit velocity AND rising star acceleration is both building and attracting attention — a stronger pattern than either alone. GitDealFlow uses star acceleration as one input layer in Scout Score (the 0–100 taste metric) and as a secondary signal in acceleration detection.
In Scout Score specifically, the metric correlates with a user's ability to spot breakout repositories before the wider market. A user who consistently stars repos during their acceleration phase (not after they're popular) scores higher.
Pure star counts are a vanity metric — a repo with 10,000 stars that hasn't been updated in a year is parked. Star acceleration only cares about the active growth curve, which is what matters for investment signal.
Star count is the total. Star acceleration is how fast that total is growing. GitDealFlow uses acceleration, not the absolute number, because acceleration catches breakout before it's obvious.
Two places: as a secondary signal in acceleration detection (alongside commit velocity, contributor growth, and repo expansion), and as a primary input in Scout Score (at signals.gitdealflow.com/receipts).
About this page: Published 2026-07-18. Authored by The Data Nerd (ORCID 0009-0002-2222-4112), the pseudonymous maintainer of GitDealFlow. The methodology is published as SSRN preprint 6606558 and archived on Zenodo. Third-party statistics are sourced from the Ahrefs AEO methodology. Report an error.
About this page: Published 2026-07-18. Authored by The Data Nerd (ORCID 0009-0002-2222-4112), the pseudonymous maintainer of GitDealFlow. The methodology is published as SSRN preprint 6606558 and archived on Zenodo. Third-party statistics are sourced from the Ahrefs AEO methodology. Report an error.
Free, no card. 21–47 days before the round.
Get the 5 names →