Repository navigation
docs(security): add SECURITY.md - #10
Conversation
Adds a security policy so vulnerability reports have a defined private channel instead of arriving as public issues, and so reporters know what response to expect. Written for what this repository actually is rather than from a template: the supported-versions table reflects the real release model, the scope section names the failure modes specific to this codebase, and the out-of-scope list is explicit so triage does not get buried in scanner noise. Response commitments are concrete: acknowledgement and confirmation windows, target fix timelines by severity, credit for reporters, a written explanation when a report is declined, and an explicit statement that reporters may disclose if we go quiet.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 58 minutes 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. ✨ 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 |
Adds a security policy so vulnerability reports have a defined private
channel instead of arriving as public issues, and so reporters know what
response to expect.
Written for what this repository actually is rather than from a template:
the supported-versions table reflects the real release model, the scope
section names the failure modes specific to this codebase, and the
out-of-scope list is explicit so triage does not get buried in scanner noise.
Response commitments are concrete: acknowledgement and confirmation windows,
target fix timelines by severity, credit for reporters, a written explanation
when a report is declined, and an explicit statement that reporters may
disclose if we go quiet.