docs(security): drop response-SLA, add no-bounty and safe-harbor - #854
Conversation
Remove the "Response expectations" section — a service-level promise that mainly attracts low-effort "beg bounty" reports and isn't essential up front. Add a "No bug bounty" section stating there is no paid program and reserving the right to disregard low-effort unsolicited reports (with a link to Troy Hunt's write-up), and a "Safe harbor" section matching gominimal/pkgs to protect good-faith research. Offer PGP key exchange in the reporting section, also for parity with the pkgs policy. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 20 seconds Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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. Comment |
Follow-up to #850 (community health), applying review feedback to
SECURITY.mdand squaring it withgominimal/pkgs.What & why
gominimal/pkgspolicy for cross-repo consistency.Cross-repo note
gominimal/pkgsstill has its "What to expect" SLA section and no bug-bounty disclaimer. If we're standardizing on this stance,pkgsshould get the same two edits (drop the SLA, add No-bug-bounty) so the two policies stay in parity — flagging for a follow-up there.🤖 Generated with Claude Code