Update security contact to security@layer5.io

[leecalcote]

Updates references to the renamed security reporting address: security-vulns-reports@layer5.io is now security@layer5.io. Only the email address (and its mailto: link) changes.

Summary by CodeRabbit

• Documentation
  • Updated the security vulnerability reporting contact information to use security@layer5.io. The new address is reflected consistently in the project’s security guidance.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: d7d6f2d9-373e-4fc1-9317-32944b2bde8b

---

📥 Commits

Reviewing files that changed from the base of the PR and between ebe4e7b and b9b4616.

---

📒 Files selected for processing (2)

• AGENTS.md
• SECURITY.md

---

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

---

---

📝 Walkthrough

Walkthrough

The vulnerability-reporting address changed from security-vulns-reports@layer5.io to security@layer5.io in AGENTS.md and SECURITY.md.

Changes

Security reporting contact

Layer / File(s)	Summary
Update reporting address AGENTS.md, SECURITY.md	Both documents now list security@layer5.io as the vulnerability-reporting address.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

---

Merge Risk: ⚪ Minimal · up to b9b46

Both documents now direct vulnerability reports to the updated security address. No merge-blocking risk is evident from the supplied change context.

Pre-merge checks | 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: updating the security contact address to security@layer5.io.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

---

---

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

---

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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

[github-actions]

🧹 Preview removed because the pull request was closed.