"Implement API Response Caching to Reduce GitHub API Rate Limiting"

[hima08656]

Description
The application currently makes direct API calls to GitHub on every user search, which can quickly exhaust the rate limit (60 requests/hour for unauthenticated users, 5000 for authenticated). This results in failed requests and degraded user experience.

Current Behavior
Each search triggers a fresh API call
No data persistence between sessions
Users hit rate limits during frequent searches
Duplicate requests for the same user data

Proposed Solution
Implement a caching mechanism using localStorage or sessionStorage:
Cache API responses with timestamps
Set cache expiration (e.g., 15 minutes)
Serve cached data when available and valid
Fall back to API only when cache is expired or missing
Add visual indicator showing cached vs. live data

Benefits
Reduced API calls by ~70-80%
Faster load times for repeat searches
Better user experience
Prevents rate limit errors

I would like to work on this issue under GSSoC'26

[mehul-m-prajapati]

@hima08656 : There is a PAT token input, so 5000 req/hour for authenticated user, so dont need caching I think