AOSSIE-Org / AOSSIE-Org/OrgExplorer
[BUG]: Missing pagination safety guard in fetchContributors() and fetchIssues()
- Lenguaje dominante
- JavaScript
- Estrellas
- 34
- Forks
- 92
- Merge medio
- 8 d 7 h
- PR fusionados (30 d)
- 12
Descripción
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
Guía de contribución
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- github, javascript
- Área
- api, backend
- Tipo de issue
- Error
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 64/100