Have a question about how GitScore works or how we handle your data? Find the answers to our most common inquiries below.
No. GitScore relies entirely on the public GitHub REST API. We do not require you to authenticate or log in, which means we physically cannot access your private repositories, private organizations, or any non-public data. Your score is based solely on what is visible to the public.
Your score is calculated dynamically every time you click "Analyze". We fetch the latest data from GitHub in real-time. If you just pushed a new repository or gained a new follower, those changes will be reflected immediately in your next search.
Because GitScore does not require users to log in, we rely on GitHub's unauthenticated API rate limits, which are capped at 60 requests per hour per IP address. If you search for too many profiles in a short time, GitHub will temporarily block requests. If you hit this limit, please wait a few minutes and try again.
While mathematically possible, achieving a perfect score of 1000 is exceptionally rare. It requires tens of thousands of stars, a massive follower count, years of consistent daily activity, and extreme language diversity. A score above 500 is considered excellent, and above 700 is considered elite.
Our activity score focuses on the last 90 days of public events (pushes, pull requests, issues). If you were highly active a year ago but haven't contributed publicly in the last 3 months, your activity score will be lower. We value recent, consistent engagement.
GitScore provides a fun and data-driven way to look at open-source impact, but it should not be the sole metric used for hiring decisions. Many excellent developers do their best work in private, corporate repositories that GitScore cannot see. Use GitScore as a supplement to technical interviews and portfolio reviews.