Update SECURITY.md

[Muhammad-Hashim]

Description of change

Pull-Request Checklist

• Code is up-to-date with the main branch
• npm run lint passes with this change
• npm run test passes with this change
• This pull request links relevant issues as Fixes #0000
• There are new or updated unit tests validating the change
• Documentation has been updated to reflect this change
• The new commits follow conventions outlined in the conventional commit spec

Summary by CodeRabbit

• Documentation
  • Updated vulnerability reporting contact information in security guidelines.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates the vulnerability reporting contact information in SECURITY.md. The email address in the "If you believe you've found a security issue" section is replaced with new contact details, maintaining the same policy structure and response commitment.

Changes

Security Contact Update

Layer / File(s)	Summary
Policy Contact Update SECURITY.md	The vulnerability reporting email address in the security policy is replaced with new contact information.

---

🎯 1 (Trivial) | ⏱️ ~2 minutes

---

A tiny tweak to keep us secure,
New contact lines, so pure and sure,
Security thrives with care so keen,
Updated paths for bugs unseen! 🐰✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title 'Update SECURITY.md' is directly related to the changeset, which updates the SECURITY.md file with a new vulnerability reporting contact.
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 Muhammad-Hashim-patch-1

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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

[Muhammad-Hashim]

sasddasd

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@SECURITY.md`:
- Line 7: The SECURITY.md line containing the fragment "email: `" is missing the
actual contact and an ending backtick; update that line to include the real
security contact email and close the markdown code span (e.g., change the
"email: `" entry to something like email: `security@yourdomain.com`) so the
contact is complete and the markdown is valid.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7d0ed9d7-f83b-44b5-9281-5ff07adc9469

📥 Commits

Reviewing files that changed from the base of the PR and between 79f018a and 5e0f192.

📒 Files selected for processing (1)

• SECURITY.md

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Critical: Missing email address and broken markdown syntax.

The vulnerability reporting contact information is incomplete. Line 7 contains `email: `` but no actual email address is provided, and the opening backtick is never closed. This breaks the security reporting process entirely—security researchers cannot report vulnerabilities without valid contact information.

Please provide the complete email address in proper markdown format.

📧 Expected fix format

-Instead, email: `
+Instead, email: `security@example.com`

Replace security@example.com with the actual security contact email address for this repository.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	Instead, email: `
	Instead, email: `security@example.com`

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@SECURITY.md` at line 7, The SECURITY.md line containing the fragment "email:
`" is missing the actual contact and an ending backtick; update that line to
include the real security contact email and close the markdown code span (e.g.,
change the "email: `" entry to something like email: `security@yourdomain.com`)
so the contact is complete and the markdown is valid.