Create SECURITY.md for security policy

[Dargon789]

Added a security policy document outlining supported versions and vulnerability reporting.

Summary by Sourcery

Documentation:

• Introduce SECURITY.md documenting supported versions for security updates and guidance on reporting vulnerabilities.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
legion	Ready	Preview, Comment	Apr 30, 2026 11:23am

[sourcery-ai]

Reviewer's Guide

Adds a new SECURITY.md file defining the project’s security policy, including supported versions and guidance for reporting vulnerabilities.

File-Level Changes

Change	Details	Files
Introduce a SECURITY policy document for the project.	Create SECURITY.md at the repository root with a Security Policy header and sections for supported versions and vulnerability reporting Document which major/minor release lines are currently supported with security updates using a markdown table Provide placeholder guidance text explaining that this document should be used to describe how to report vulnerabilities and what reporters can expect	SECURITY.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[sourcery-ai]

Hey - I've left some high level feedback:

• The SECURITY.md still contains template placeholder text (e.g., “Use this section to tell people…”); please replace these with concrete, project-specific details about supported versions and vulnerability disclosure.
• Consider clarifying what the version numbers in the support table correspond to (e.g., library vs. service, semantic versioning policy) and what “supported” entails in terms of security fix commitments and timelines.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The SECURITY.md still contains template placeholder text (e.g., “Use this section to tell people…”); please replace these with concrete, project-specific details about supported versions and vulnerability disclosure.
- Consider clarifying what the version numbers in the support table correspond to (e.g., library vs. service, semantic versioning policy) and what “supported” entails in terms of security fix commitments and timelines.

Fix all in Cursor

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

This pull request adds a new SECURITY.md file to define the project's security policy. The review feedback correctly identifies that the file currently contains boilerplate placeholder text for supported versions and vulnerability reporting instructions, which need to be updated with project-specific details and links.