Repository navigation
Publish rate-limiter tier matrix and per-route budgets #614
Description
Context
src/middleware/rateLimiter.ts (~281 lines changed) and tests/integration/rateLimiterTiering.integration.test.ts (357 lines) implement tiering, but there is no single matrix telling contributors which routes have which limits.
Proposal
- Generate or hand-maintain a table: route → tier → window → burst
- Document which auth type (session, API key, webhook) maps to which tier
- Add a CI check (or unit test) that every mounted route has an explicit tier entry (fail-open vs fail-closed decision documented)
Acceptance criteria
- Matrix published in docs (new section of docs/API_REFERENCE.md or docs/RATE_LIMITING.md)
- Untiered routes are a CI failure
Activity
ranjeetprabhatedu-dotcom commentedon Oct 19, 2026
Hello maintainers,
I reviewed "Publish rate-limiter tier matrix and per-route budgets" and would like to work on this.
I have reviewed the problem description and acceptance criteria for this issue. I have a clear, tested implementation ready with defensive error handling and 100% green CI proof.
I will deliver a clean, well-tested, and production-ready PR promptly upon assignment. Kindly assign this issue to me.
Thank you!
bitech026 commentedon Oct 19, 2026
@bitech026 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @bitech026 to this issue.
Turawa2 commentedon Oct 19, 2026
@Turawa2 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Turawa2 to this issue.
johnsmccain commentedon Oct 19, 2026
@johnsmccain has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @johnsmccain to this issue.
Amksongs commentedon Oct 19, 2026
@Amksongs has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Amksongs to this issue.
drips-wave commentedon Oct 19, 2026
Congratulations, @johnsmccain! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @johnsmccain: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
grantfox-oss commentedon Oct 19, 2026
🎉 This issue has been marked as completed on GrantFox!
@johnsmccain's PR #627 was approved and merged by @robertocarlous.
🏆 @johnsmccain: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (914 total points). Track your full progress on GrantFox.
👏 Great work, @johnsmccain! Keep contributing to Neurowealth.
drips-wave commentedon Oct 19, 2026
This issue has been completed by @johnsmccain as part of the Stellar Wave Program's 10th Wave 🥳
😎 @johnsmccain: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
feat(rate-limiting): publish the tier matrix and enforce it in CI (Ne…