Skip to content

Create SECURITY.md for security policy and reporting #3

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
Lawrence Lucas Large (LukeLarge) wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Create SECURITY.md for security policy and reporting #3

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.

Comment on lines +5 to +7
Copy link

Copilot AI Feb 27, 2026

Choose a reason for hiding this comment

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

This reads as the default template text rather than a project-specific policy. Replace with concrete supported version ranges (or maintenance branches) and a clear reporting process (private contact method, expected response timelines, disclosure expectations).

Copilot uses AI. Check for mistakes.
| 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

Copilot AI Feb 27, 2026

Choose a reason for hiding this comment

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

The markdown table has an extra leading pipe (||), which will render as an unintended empty first column. Use a single leading pipe for each row (e.g., | Version | Supported |).

Copilot uses AI. Check for mistakes.
Comment on lines +8 to +13
Copy link

Copilot AI Feb 27, 2026

Choose a reason for hiding this comment

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

Relying only on emoji icons for support status can be less clear for some readers and assistive technologies. Consider using explicit text such as Supported / Not supported (optionally alongside emoji) to make the table more universally readable.

Suggested change
| Version | Supported |
| ------- | ------------------ |
| 5.1.x | :white_check_mark: |
| 5.0.x | :x: |
| 4.0.x | :white_check_mark: |
| < 4.0 | :x: |
| Version | Supported |
| ------- | ---------------------------- |
| 5.1.x | :white_check_mark: Supported |
| 5.0.x | :x: Not supported |
| 4.0.x | :white_check_mark: Supported |
| < 4.0 | :x: Not supported |

Copilot uses AI. Check for mistakes.

## 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

Copilot AI Feb 27, 2026

Choose a reason for hiding this comment

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

This reads as the default template text rather than a project-specific policy. Replace with concrete supported version ranges (or maintenance branches) and a clear reporting process (private contact method, expected response timelines, disclosure expectations).

Copilot uses AI. Check for mistakes.