Summary
The GitProxy UI currently calls the GitHub API directly from the client to retrieve project information. These requests are unauthenticated and frequently hit GitHub’s primary rate limit.
Problem
Because these requests come from the client, they use a shared IP address across the organisation. When GitHub applies rate limiting, it affects everyone using the UI.
According to the GitHub docs, the primary rate limit for unauthenticated requests is 60 requests per hour.
https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2026-03-10
Proposed change
Move this GitHub API call from the client to the backend so the request can use an authenticated token.
Authenticated requests have a much higher rate limit, which should significantly reduce failures. Per the GitHub docs, this can scale up to 12,500 requests per hour.
Summary
The GitProxy UI currently calls the GitHub API directly from the client to retrieve project information. These requests are unauthenticated and frequently hit GitHub’s primary rate limit.
Problem
Because these requests come from the client, they use a shared IP address across the organisation. When GitHub applies rate limiting, it affects everyone using the UI.
According to the GitHub docs, the primary rate limit for unauthenticated requests is 60 requests per hour.
https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2026-03-10
Proposed change
Move this GitHub API call from the client to the backend so the request can use an authenticated token.
Authenticated requests have a much higher rate limit, which should significantly reduce failures. Per the GitHub docs, this can scale up to 12,500 requests per hour.