Skip to content

Create SECURITY.md for security policy #22797

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
stoyanovaantoaneta76-hash wants to merge 1 commit into
base: master
Choose a base branch
from
+21 −0
Open

Create SECURITY.md for security policy #22797

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: |
Copy link

@cubic-dev-ai cubic-dev-ai bot Jan 24, 2026 •
edited
Loading

Choose a reason for hiding this comment

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

P2: SECURITY.md still contains a template Supported Versions table (5.1.x/5.0.x/4.0.x) that conflicts with the project’s documented 7.x/6.x releases, so the security policy does not reflect actual supported versions.

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At SECURITY.md, line 10:

<comment>SECURITY.md still contains a template Supported Versions table (5.1.x/5.0.x/4.0.x) that conflicts with the project’s documented 7.x/6.x releases, so the security policy does not reflect actual supported versions.</comment>

<file context>
@@ -0,0 +1,21 @@
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 5.1.x   | :white_check_mark: |
+| 5.0.x   | :x:                |
+| 4.0.x   | :white_check_mark: |
</file context>
Fix with Cubic

| 5.0.x | :x: |
| 4.0.x | :white_check_mark: |
| < 4.0 | :x: |

## Reporting a Vulnerability

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

@cubic-dev-ai cubic-dev-ai bot Jan 24, 2026 •
edited
Loading

Choose a reason for hiding this comment

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

P2: Reporting instructions are still placeholder template text, so the security policy lacks any real vulnerability reporting process.

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At SECURITY.md, line 17:

<comment>Reporting instructions are still placeholder template text, so the security policy lacks any real vulnerability reporting process.</comment>

<file context>
@@ -0,0 +1,21 @@
+
+## 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
</file context>
Fix with Cubic


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.