Add SECURITY.md + CODEOWNERS; bump CI actions off Node 20

[CryptoFewka]

Pre-public hardening: review findings #8 and #9 plus a CODEOWNERS file.

SECURITY.md (#8)

• Directs reporters to GitHub Private Vulnerability Reporting (Security tab -> Report a vulnerability) as the primary channel, with security@getoptimum.xyz as a plain-text fallback. Not defanged: GitHub renders it as a clickable mailto, which is the low-friction path we want; defanging only deters scraper-spam to a role alias at the cost of usability.
• Documents supported versions (latest 1.x) and how keysync handles the ovi_live_* key (HTTPS-only, refuses credential-in-URL, no token caching, never logged) so researchers have the threat model up front.
• Action item for you: enable "Private vulnerability reporting" in repo Settings -> Security so the preferred channel actually exists.

CODEOWNERS

• * @getoptimum/devops (team slug confirmed via the org). Note: the @getoptimum/devops team must have write access to this repo for review requests to be auto-assigned; otherwise GitHub flags the entry as unknown.

CI action bump (#9)

• actions/checkout v4.2.2 -> v7.0.0, actions/setup-python v5.3.0 -> v6.3.0 in both test.yml and release.yml. Both run on Node 24, clearing the Node 20 deprecation warning. Pinned to commit SHAs verified against the upstream release tags; inputs used (python-version, cache: pip) are unchanged across these majors.

Docs/CI only, no package code touched. pytest 109 passed; both workflows parse as valid YAML.

Written with Claude Code

[coderabbitai]

Warning

Review limit reached

@CryptoFewka, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 25 minutes and 9 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository: getoptimum/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 838a1e9f-d88c-4cf5-b09f-2029c9d798c3

📥 Commits

Reviewing files that changed from the base of the PR and between b11e61b and 6e8cdb0.

⛔ Files ignored due to path filters (1)

• .github/CODEOWNERS is excluded by none and included by none

📒 Files selected for processing (3)

• .github/workflows/release.yml
• .github/workflows/test.yml
• SECURITY.md

---

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