[BUG]: GitHub data cache is not tied to auth scope and survives PAT deletion

Offen
#446 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@Basharkhan7776 arbeitet bereits daran.

Seit 08.11.2026.

  • #448 von @Basharkhan7776 — offen

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
55/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
github, javascript
Bereich
api, database, security

Rechercherichtung

Start by tracing the API response cache calls, including cacheGet(url), and the PAT deletion flow that removes the token and rate-limit entry. Check how IndexedDB stores entries and how requests distinguish authenticated from unauthenticated responses. Done means private data is no longer accessible after PAT deletion and adding a PAT does not reuse incomplete unauthenticated responses.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

bug
Bug Description

API responses are cached in IndexedDB by URL only:

const cached = await cacheGet(url)
if (cached) return cached

The cache key does not include whether the request was authenticated, which token/account was used, or what permissions that token had. Deleting the PAT removes the token and rate-limit entry but does not clear cached GitHub data.

This creates two problems:

  1. Data fetched with a private-repo-capable PAT remains readable in IndexedDB after the PAT is deleted.
  2. Data fetched without a PAT can be served from cache after a PAT is added, so the “complete analysis” may reuse incomplete unauthenticated responses.
Steps to Reproduce
  1. Save a PAT that can read private repositories.
  2. Explore an organization and open several pages so responses are cached.
  3. Delete the PAT in Settings.
  4. Open DevTools → Application → IndexedDB → orgexplorer_cache or orgexplorer.
  5. Observe that cached GitHub response data remains.
Impact

High - Major feature is broken

Code of Conduct
  • I have joined the Discord server and will post updates there
  • I have searched existing issues to avoid duplicates
Vorherrschende Sprache
JavaScript
Sterne
53
Forks
182
Ø Merge
18 Min.
Gemergte PRs (30 T.)
2

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus AOSSIE-Org/OrgExplorer

Alle Issues in AOSSIE-Org/OrgExplorer

Ähnliche Issues

Weitere Issues zu JavaScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.