Skip to content

Create SECURITY.md with policy details #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jz197781 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Create SECURITY.md with policy details #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
View file
Open in desktop
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.

| Version | Supported |
| ------- | ------------------ |
| 5.1.x | :white_check_mark: |
| 5.0.x | :x: |
| 4.0.x | :white_check_mark: |
| < 4.0 | :x: |
Comment on lines +5 to +13
Copy link

@gemini-code-assist gemini-code-assist bot Dec 2, 2025

Choose a reason for hiding this comment

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

high

The content in the 'Supported Versions' section appears to be the default template text and presents a confusing support schedule (e.g., version 5.0.x is unsupported while the older 4.0.x is supported). Please replace this placeholder with the project's actual version support policy. For clarity, it's best to list versions in descending order and accurately state their support status.


## Reporting a Vulnerability

Use this section to tell people how to report a vulnerability.

Tell them where to go, how often they can expect to get an update on a
reported vulnerability, what to expect if the vulnerability is accepted or
declined, etc.
Comment on lines +17 to +21
Copy link

@gemini-code-assist gemini-code-assist bot Dec 2, 2025

Choose a reason for hiding this comment

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

critical

The 'Reporting a Vulnerability' section contains only placeholder text. It is critical to provide clear, actionable instructions for anyone who finds a security vulnerability. Please replace this placeholder with specific details, including the exact reporting channel (e.g., a dedicated email address or GitHub's private vulnerability reporting feature) and what reporters can expect regarding response times and the handling process.

Suggested change
Use this section to tell people how to report a vulnerability.
Tell them where to go, how often they can expect to get an update on a
reported vulnerability, what to expect if the vulnerability is accepted or
declined, etc.
To report a security vulnerability, please use the **Private Vulnerability Reporting** feature on GitHub.
You can expect a response from our team within 48 hours of submission. If the vulnerability is accepted, we will work on a fix and disclose it publicly after the patch is released.