security: reject shared-writable cloud review authority - #178
Conversation
|
Warning Review limit reached
Next review available in: 53 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
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 |
Purpose
Fail cloud-review decision authority closed when its Unix storage directory is writable by group or other principals. Read-only decision files are not durable authorization evidence if another principal can unlink or replace entries through the parent directory.
Test-first state
Current RED head
7b4d7c1b254117437c62df0847efe8a046a7f02dadds a Unix integration regression through the publicload_latest_decisionsboundary. It makes an existing review directory mode0777and requires stable refusalcloud-review-directory-writable-by-others.No production behavior is changed yet. The exact-head Test workflow must demonstrate the expected RED before the narrow fix is applied.
Scope
This lane owns only cloud-review directory authority and its focused regression. It does not modify the active global coverage owner #156, provider-global-sync #177, generic-cleanup #174, Podman desktop #150, or canonical documentation #149.
Keep Draft until RED is observed, the narrow production fix turns the same regression GREEN, all exact-head required checks pass, and live-base/writer evidence remains clean.