Jaishree2310/GlassyUI-Components

[BUG] useGitHubStars cache poisoned with 0 stars during API rate limits or offline state

Open

#698 opened on Jun 5, 2026

View on GitHub
 (3 comments) (0 reactions) (1 assignee)TypeScript (217 forks)auto 404
good first issuegssoc'26gssoc:approvedlevel:beginnertype:bug

Repository metrics

Stars
 (114 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

In useGitHubStars.ts, the hook fetches stargazers count from the GitHub API but does not check if the response was successful (r.ok). Under rate limits (status 403) or offline errors, the parsed JSON is an error payload. The hook defaults data.stargazers_count to 0, setting and caching 0 stars in localStorage for a whole hour, instead of retaining the last known cached count.

Steps to Reproduce

  1. Hit the GitHub API rate limit.
  2. Refresh the website.
  3. The website now displays ★ 0 stars, overwriting the previously correct cached count.

Suggested Fix

Check r.ok and ensure stargazers_count is a valid number before updating the cache.

Contributor guide

Research direction
Investigate the useGitHubStars hook to add a check for r.ok (response success) and ensure stargazers count is a valid number before updating the cache. Also, consider retaining the last known cached count when the API fails.
Tech stack
typescriptreact
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ReactTypeScriptGitHub API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70