Fix formatting in SECURITY.md for version support

[nasrin256]

white_check_mark

Summary by CodeRabbit

• Documentation
  • Added security policy guidance with supported versions and their support status
  • Added vulnerability reporting procedures with expected response timelines

[coderabbitai]

Walkthrough

Introduces a new SECURITY.md file documenting security policy, including a supported versions table with support status markers and guidance for reporting vulnerabilities with expected response timelines.

Changes

Cohort / File(s)	Change Summary
Security Documentation SECURITY.md	New file with supported versions table and vulnerability reporting procedures

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A shield of words now guards the way,
Security policies here to stay,
Report your bugs with gentle care,
We'll hop to fix them, swift and fair! 🛡️

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title Check	⚠️ Warning	The raw summary indicates that the pull request introduces a completely new SECURITY.md file with comprehensive security policy guidance, including a "Supported Versions" table and a "Reporting a Vulnerability" section. However, the title "Fix formatting in SECURITY.md for version support" frames this as a formatting fix to an existing file, which mischaracterizes the primary nature of the change. The term "fix formatting" implies updating or correcting the structure of an already-existing file, not introducing a brand new security policy document. While the title does reference real elements of the changeset (SECURITY.md and version support), the characterization of the change is misleading about what was actually implemented.	Consider revising the title to accurately reflect the main change, such as "Add SECURITY.md with security policy and version support guidelines" or "Introduce SECURITY.md with vulnerability reporting and version support information." This would more clearly communicate to teammates that this pull request introduces a new security policy document rather than making formatting updates to an existing file.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b525009 and dbd7e2e.

📒 Files selected for processing (1)

• SECURITY.md (1 hunks)

🔇 Additional comments (1)

SECURITY.md (1)

8-13: Verify the version support matrix is intentional.

The table shows versions 5.1.x and 4.0.x as supported, while 5.0.x and versions below 4.0 are unsupported. This is an atypical support pattern (usually the latest release and one or two previous minor versions receive updates). Confirm this matrix matches your project's security maintenance policy.