Update contact email for reporting vulnerabilities

[taltas]

Security email update

Summary by CodeRabbit

• Documentation
  • Updated the vulnerability reporting contact email from security@roocode.com to support@zoocode.dev. All reporting instructions and acknowledgement/mitigation timelines remain unchanged. This is a documentation-only update; there are no functional changes or public API modifications.

[coderabbitai]

Warning

Rate limit exceeded

@edelauna has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 22 minutes and 9 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 2a8ce0b4-7f7a-4ae1-9dcc-a3e04871a68e

📥 Commits

Reviewing files that changed from the base of the PR and between 4e890ed and 9a40eb2.

📒 Files selected for processing (1)

• SECURITY.md

📝 Walkthrough

Walkthrough

This PR updates SECURITY.md to change the vulnerability reporting email from security@roocode.com to support@zoocode.dev. No other reporting instructions or timelines were modified.

Changes

Security Policy Contact Update

Layer / File(s)	Summary
Contact Information SECURITY.md	Vulnerability reporting email address updated to support@zoocode.dev.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minutes

Poem

🐰 A little change, a tidy clue,
The mailbox hops to something new.
From roocode's gate to zoocode's door,
Reports land safe — that's all for sure!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is minimal (one sentence) and lacks critical required sections like Related GitHub Issue, Description, Test Procedure, and Pre-Submission Checklist from the template.	Add the required template sections, particularly: link the related GitHub Issue, explain implementation details and design choices, describe how the change was tested, and complete the Pre-Submission Checklist.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically summarizes the main change: updating the contact email for vulnerability reporting, which matches the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch security-text

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[edelauna]

📧