Conversation
Add a security policy document outlining supported versions and vulnerability reporting.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ## 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. |
There was a problem hiding this comment.
Add actual vulnerability reporting channel
The Reporting a Vulnerability section still contains template placeholder text and does not give users a concrete email, issue tracker, or response expectations. Without real instructions, security researchers have no way to disclose findings, undermining the purpose of adding a security policy.
Useful? React with 👍 / 👎.
Add a security policy document outlining supported versions and vulnerability reporting.