Skip to content

Create SECURITY.md for security policy #958

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

Create SECURITY.md for security policy #958

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 +8 to +13
Copy link
Copy Markdown
Contributor

@greptile-apps greptile-apps Bot Apr 20, 2026

Choose a reason for hiding this comment

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

P1 Template version numbers not replaced

The version table still contains the GitHub SECURITY.md template defaults (5.1.x, 5.0.x, 4.0.x). The project's actual version from package.json is 0.1.0, so these rows are misleading and tell security researchers nothing about which release lines are actually patched. The table should be updated to reflect the real supported versions of this project.


## 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
Copy Markdown
Contributor

@greptile-apps greptile-apps Bot Apr 20, 2026

Choose a reason for hiding this comment

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

P1 Reporting instructions are unfilled placeholder text

The "Reporting a Vulnerability" section contains only the GitHub template boilerplate ("Use this section…", "Tell them where to go…") — there is no actual contact address, process, or response timeline. The PR description itself references disclosures@solana.org for Solana Verify security bugs, which suggests at least one valid contact point already exists. Without real content here, this document gives security researchers no actionable way to disclose vulnerabilities.