chore: add SECURITY.md for reporting vulnerabilities

[german-boop]

I have added a SECURITY.md file that outlines the process for users to report any potential security vulnerabilities privately.

This aligns with GitHub practices and provides a clear policy for addressing security issues, even in smaller projects.

Summary by CodeRabbit

• Documentation
  • Added security policy documentation detailing supported versions and their security update status.
  • Outlined vulnerability reporting process with expected resolution timelines.
  • Provided guidance for submitting security reports through GitHub's private vulnerability reporting feature.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

A SECURITY.md file is added to document security governance, including a supported versions table, vulnerability reporting procedures, and guidance on using GitHub's private vulnerability reporting feature.

Changes

Cohort / File(s)	Summary
Security Documentation SECURITY.md	New file establishing security policy with supported versions (5.1.x, 5.0.x, 4.0.x, < 4.0) and vulnerability reporting guidelines.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 With whiskers twitched and paws held high,
A SECURITY.md hops on by!
Versions tracked and paths so clear,
Safe and sound throughout the year! 🔒✨

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 39cf7a1 and a375217.

📒 Files selected for processing (1)

• SECURITY.md

---

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