Create SECURITY.md

[trewc456-ai]

Summary by CodeRabbit

• Documentation
  • Added a security policy document with supported version information.
  • Included guidance on how to report security issues and what to expect after submitting a report.

[coderabbitai]

📝 Walkthrough

Walkthrough

Added a new SECURITY.md file documenting the project's security policy, including a supported versions table and instructions for reporting vulnerabilities.

Changes

Security Policy Documentation

Layer / File(s)	Summary
Add security policy document SECURITY.md	New file introduces "Supported Versions" and "Reporting a Vulnerability" sections, including a version support table and reporting guidance text.

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

🚥 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 title accurately describes the main change: adding a new SECURITY.md file.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Warning

Tools execution failed with the following error:

Failed to run tools: 13 INTERNAL: Received RST_STREAM with code 2 (Internal server error)

---

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[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`:
- Around line 5-6: The SECURITY.md section still contains placeholder template
guidance instead of the project’s actual security policy. Replace the
placeholder text in the security policy area with repository-specific
instructions that identify how to report vulnerabilities, the expected response
timeline, and how issues are handled; update the relevant SECURITY.md sections
consistently so the document reflects the real policy rather than template
language.

🪄 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1564624b-e8d9-48b8-a543-ff1ae82be65c

📥 Commits

Reviewing files that changed from the base of the PR and between e3dfe8b and 31fec80.

📒 Files selected for processing (1)

• SECURITY.md

[coderabbitai]

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Replace the placeholder guidance with the actual policy.

These are still GitHub template instructions, so the document doesn’t yet tell users where to report issues, what response timeline to expect, or how vulnerability handling works here. Please replace them with project-specific details.

Also applies to: 17-21

🤖 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` around lines 5 - 6, The SECURITY.md section still contains
placeholder template guidance instead of the project’s actual security policy.
Replace the placeholder text in the security policy area with
repository-specific instructions that identify how to report vulnerabilities,
the expected response timeline, and how issues are handled; update the relevant
SECURITY.md sections consistently so the document reflects the real policy
rather than template language.