AOSSIE-Org / AOSSIE-Org/OrgExplorer
[BUG]: Missing pagination safety guard in fetchContributors() and fetchIssues()
- Lingua principale
- JavaScript
- Stelle
- 34
- Fork
- 92
- Merge medio
- 8g 7h
- PR unite (30g)
- 12
Descrizione
Bug Description
Both fetchContributors() and fetchIssues() iterate through paginated GitHub API responses using an unbounded loop:
js :
for (let page = 1; ; page++) { ... }
Steps to Reproduce :
1. Open services/github.js.
2. Navigate to fetchContributors() and fetchIssues().
3. Observe that both functions use an unbounded pagination loop without a maximum page limit or response validation.
Environment Details :
- OS: Windows 11
- Browser: Brave
- Node.js: 22.18.0
Impact :
Medium - Feature works but has issues
### Code of Conduct
- [x] I have joined the [Discord server](https://discord.gg/hjUhu33uAn) and will post updates there
- [x] I have searched existing issues to avoid duplicates
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start in services/github.js and inspect fetchContributors() and fetchIssues(), focusing on their paginated GitHub API loops and response handling. The issue is complete when both functions have a defined pagination safety limit and validate responses instead of iterating unboundedly.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- github, javascript
- Ambito
- api, backend
- Tipo di issue
- Bug
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Stato di attività
- Tranquilla
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 64/100