Repository navigation
fix(security): Phase 0 critical hardening (guildModuleAccess enforcement) - #664
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 21 minutes and 57 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
5d7e123 to
4d188e6
Compare
|
…ent) (#664) * fix(security): require guildModuleAccess on roles and moderation routes * test(security): update role and moderation tests to mock guildAccessService



Summary
requireGuildModuleAccesson guild routes (roles.ts, moderation.ts)reaction-roles,roles/exclusive) now requireoverview:viewaccessmoderation:viewormoderation:manageaccessguildAccessServicefor successful auth flowsChanges
packages/backend/src/routes/roles.ts— AddedrequireGuildModuleAccess('overview', 'view')to both routespackages/backend/src/routes/moderation.ts— AddedrequireGuildModuleAccess('moderation', 'view'/'manage')to all 8 routesRisk
None. Both fixes are non-breaking:
Verification