Githubster guide
GitHub API Rate Limits for Followers and Following Lists
Large GitHub follower and following lists can require several API requests. GitHub applies rate limits to protect its API, which can affect how quickly a public profile comparison completes.
- Public API requests have rate limits
- Larger lists need pagination
- Optional tokens can raise the limit
Try Githubster
Enter a public GitHub username to compare followers, following, and mutual connections.
Open GithubsterWhy follower checks use multiple requests
GitHub returns public followers and following lists in pages. A profile with many connections requires more pages, which means more API requests than a small profile.
When to use an optional token
If GitHub reports a rate limit or you need to inspect a larger public profile, Githubster can use an optional fine-grained personal access token for direct requests to GitHub. Use the minimum permissions and an expiration date.
Keep the token private
Never paste a token into an untrusted site. Githubster keeps an optional token in the current page session and sends it directly to GitHub for the requested API calls.
Frequently asked questions
Does Githubster store my token?
No. The optional token stays in the current page session and is not saved to localStorage or sent to Githubster application servers.
Do public follower lists require a token?
No. Public GitHub data can be requested without a token, subject to GitHub’s unauthenticated rate limits.