Skip to content

fix: use a real email address in SECURITY.md #89

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

Merged
merged 1 commit into from
Jan 11, 2024
Merged

fix: use a real email address in SECURITY.md #89

Show file tree
Hide file tree
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
3 changes: 2 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,8 @@ Then customize the code for your repository:
* update `deploy/$YOUR_COMMAND/Dockerfile`
* update `.github/workflows/build.yaml`, replacing `go-cli-github` with `$YOUR_COMMAND`.
* update `.goreleaser.yaml` to build `cmd/$YOUR_COMMAND`
* update the links at the top of the README
* update the links at the top of `README.md`
* update the contact email in `SECURITY.md`

1. Commit and push:

Expand Down
2 changes: 1 addition & 1 deletion SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Only the latest minor version will receive patch releases.
## Reporting a Vulnerability

To report a security issue, please [privately report a security vulnerability](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability#privately-reporting-a-security-vulnerability) through GitHub.
If you do not have a GitHub account, please email security@example.com with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue.
If you do not have a GitHub account, please email scott@smlx.dev with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue.
We will endeavour to respond within 3 working days of your email.

If an issue is confirmed as a vulnerability, we will open a Security Advisory.
Expand Down