Fix: Unbounded concurrent API requests in explore() causes Secondary Rate Limit (Abuse) bans

[Dotify71]

Fixes #124.

This PR adds a batching loop to the explore() function when fetching contributors. Previously, it fired off API requests for all repositories concurrently, which instantly triggered GitHub's secondary rate limits (abuse bans) for large organizations. The requests are now chunked in batches of 5, identical to the pattern used in runAudit().

Summary by CodeRabbit

• Performance Improvements
  • Improved contributor data loading during repository exploration by processing results in smaller groups.
  • Reduced request spikes, helping exploration remain more stable when reviewing organizations with many repositories.
  • Existing contributor totals and exploration behavior remain unchanged.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: a1faf96c-f14f-4838-bf33-9df53d0fed90

📥 Commits

Reviewing files that changed from the base of the PR and between 3dab61e and 7530d60.

📒 Files selected for processing (1)

• src/context/AppContext.jsx

---

Walkthrough

The explore flow now fetches repository contributors in sequential batches of five, using Promise.allSettled within each batch while preserving existing aggregation behavior.

Changes

Explore contributor fetching

Layer / File(s)	Summary
Batch contributor requests src/context/AppContext.jsx	Contributor requests are processed in sequential batches of five, with results retained under each organization/repository key.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• AOSSIE-Org/OrgExplorer#89: Updates PAT-aware repository selection in the same contributor-fetching flow.
• AOSSIE-Org/OrgExplorer#115: Refactors the PAT-aware exploration and contributor-analysis workflow.

Suggested labels: Typescript Lang

Suggested reviewers: rahul-vyas-dev, ri1tik, bhavik-mangla

Poem

I’m a rabbit with batches neat,
Five requests hop on down the street.
No wild API stampede in sight,
Contributors arrive just right.
Hop, hop—explore takes flight!

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main fix: batching explore() contributor requests to avoid rate-limit abuse.
Linked Issues check	✅ Passed	The batching change in explore() matches issue #124's requirement to limit concurrent contributor requests to small Promise.allSettled batches.
Out of Scope Changes check	✅ Passed	The PR only adjusts contributor-fetch batching in AppContext.jsx and introduces no unrelated changes.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}