GitHub adds aggregate star-history endpoint to reduce stargazer scraping and expensive API pagination

GitHub says it restricted stargazer and watcher lists to repository admins and collaborators after public lists enabled spam/phishing scraping and created heavy database load. It built a new star history endpoint that returns up to 30 weeks of daily star counts in one request without identities, replacing workflows that could require thousands of paginated stargazer requests for large repos like react/react.

Builders of repository analytics tools can switch from identity-bearing stargazer pages to aggregate counts, reducing privacy exposure and rate-limit pressure. The trade-off is narrower data: the reported endpoint covers up to 30 weeks of daily counts, so the article leaves open how tools should handle longer historical analyses or other resolutions.