Skip to content

Enhance SECURITY.md with more information and suggestions - #74

Open
wycliffekimondo024-sketch wants to merge 1 commit into
Leonxlnx:mainfrom
wycliffekimondo024-sketch:patch-1
Open

Enhance SECURITY.md with more information and suggestions#74
wycliffekimondo024-sketch wants to merge 1 commit into
Leonxlnx:mainfrom
wycliffekimondo024-sketch:patch-1

Conversation

@wycliffekimondo024-sketch

Copy link
Copy Markdown

Added sections for additional information and skill suggestions.

Added sections for additional information and skill suggestions.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b6e224fc25

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread SECURITY.md
Comment on lines +10 to +13
| 5.1.x | :white_check_mark: |
| 5.0.x | :x: |
| 4.0.x | :white_check_mark: |
| < 4.0 | :x: |

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Replace the template version matrix

This support matrix appears to be the default GitHub template rather than this repo's actual release policy: the README/CHANGELOG only document the v1 and v2 skill lines, and there are no 4.x/5.x tags in the repository. Publishing these rows marks non-existent 5.1.x and 4.0.x releases as supported while omitting the real installable versions, which can mislead users about which versions will receive security fixes.

Useful? React with 👍 / 👎.

Comment thread SECURITY.md
Comment on lines +17 to +21
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.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Replace placeholder vulnerability instructions

When GitHub surfaces this SECURITY.md to someone reporting a vulnerability, this section gives only template text and no actual private contact or process, so reporters have no actionable security channel or response expectations. Please replace the placeholder with the real reporting destination and handling policy instead of leaving generic instructions.

Useful? React with 👍 / 👎.

@wycliffekimondo024-sketch

Copy link
Copy Markdown
Author

It's advisable to include a security policy to prevent misuse of content

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant