Skip to content

docs(security): add SECURITY.md - #10

Merged
JosueBrenes merged 1 commit into
mainfrom
docs/security-policy
Jul 22, 2026
Merged

JosueBrenes merged 1 commit into
mainfrom
docs/security-policy

Conversation

@JosueBrenes

Copy link
Copy Markdown
Member

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.

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.
@vercel

vercel Bot commented Jul 22, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
acta-docs Ready Ready Preview, Comment Jul 22, 2026 6:20am

Request Review

@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@JosueBrenes, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2f841d6c-1401-45ce-ac3c-05f87b5d0d23

📥 Commits

Reviewing files that changed from the base of the PR and between 14c613b and ce70dc0.

📒 Files selected for processing (1)
  • SECURITY.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/security-policy

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@JosueBrenes
JosueBrenes merged commit 4844132 into main Jul 22, 2026
5 checks passed
@JosueBrenes
JosueBrenes deleted the docs/security-policy branch July 22, 2026 06:21

This branch was successfully deployed

1 active deployment
Preview — ce70dc04 Deployed Jul 22, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant