Star History API
An API provided by GitHub for querying the growth trend of a repository's stars. It returns star counts aggregated as a time series, bucketed by day or by hour, and does not return the identities of individual stargazers.
Timeline (last 90 days)
GitHub refactored the Star History API, reducing the requests needed to fetch trend data each time from about 2,500 to 24.
The refactored Star History API no longer returns specific stargazer identity information, only aggregated time-series trend data.
The old Star History API required 2,500 or even more paginated requests for popular repositories to enumerate all stargazers.
After the refactor, the number of requests to the Star History API is determined by the time window and bucket granularity, decoupled from the repository's star scale.
The cost of the refactor is a narrowing of the API's capabilities: developers can no longer use this interface to find out who starred a given repository.
For the core scenario of displaying star history trends, aggregated data is already sufficient.
If a developer's existing code is still parsing the stargazer identity field, they need to pay attention to changes in the interface's response structure and move to using aggregated trend data.
All Facts (7)
After the refactor, the number of requests to the Star History API is determined by the time window and bucket granularity, decoupled from the repository's star scale.
50%UnverifiedThe refactored Star History API no longer returns specific stargazer identity information, only aggregated time-series trend data.
50%UnverifiedThe old Star History API required 2,500 or even more paginated requests for popular repositories to enumerate all stargazers.
50%UnverifiedIf a developer's existing code is still parsing the stargazer identity field, they need to pay attention to changes in the interface's response structure and move to using aggregated trend data.
50%UnverifiedThe cost of the refactor is a narrowing of the API's capabilities: developers can no longer use this interface to find out who starred a given repository.
50%UnverifiedFor the core scenario of displaying star history trends, aggregated data is already sufficient.
50%UnverifiedGitHub refactored the Star History API, reducing the requests needed to fetch trend data each time from about 2,500 to 24.
50%