Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions SECURITY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
# Security Policy

## Supported Versions

Use this section to tell people about which versions of your project are
currently being supported with security updates.

Comment on lines +5 to +7
Copy link

Copilot AI Dec 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This section contains placeholder text that should be replaced with actual information about which versions of the project are supported with security updates. Remove this instructional text and provide project-specific details.

Suggested change
Use this section to tell people about which versions of your project are
currently being supported with security updates.

Copilot uses AI. Check for mistakes.
| Version | Supported |
| ------- | ------------------ |
| 5.1.x | :white_check_mark: |
| 5.0.x | :x: |
| 4.0.x | :white_check_mark: |
| < 4.0 | :x: |
Comment on lines +10 to +13
Copy link

Copilot AI Dec 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The version numbers in this table appear to be generic placeholder examples (5.1.x, 5.0.x, 4.0.x). Replace these with the actual versions of your project that are currently supported with security updates.

Suggested change
| 5.1.x | :white_check_mark: |
| 5.0.x | :x: |
| 4.0.x | :white_check_mark: |
| < 4.0 | :x: |
| 5.2.3 | :white_check_mark: |
| 5.2.2 | :white_check_mark: |
| 5.1.0 | :x: |
| < 5.1.0 | :x: |

Copilot uses AI. Check for mistakes.

## Reporting a Vulnerability

If you discover a security vulnerability in this project, please report it by emailing **security@example.com** or by submitting a report via our [GitHub Security Advisories](https://github.com/OWNER/REPO/security/advisories).

We aim to respond to all vulnerability reports within **5 business days**. You will receive updates on the status of your report at least once per week until the issue is resolved or closed.

After you submit a report, our security team will investigate the issue and contact you for any additional information if needed. If the vulnerability is accepted, we will work with you to coordinate a fix and public disclosure. If the vulnerability is declined, we will provide a clear explanation.