AOSSIE-Org / AOSSIE-Org/OrgExplorer
[BUG]: Missing pagination safety guard in fetchContributors() and fetchIssues()
- 主要言語
- JavaScript
- スター
- 34
- フォーク
- 92
- 平均マージ
- 8日 7時間
- マージ済み PR(30日)
- 12
説明
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
コントリビューションガイド
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- github, javascript
- 領域
- api, backend
- issue の種類
- バグ
- 難易度
- 2/5
- 見積もり時間
- 1〜3時間
- 活発さ
- 静か
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 64/100