-
Notifications
You must be signed in to change notification settings - Fork 52
Add security policy #395
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.
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
base: master
Are you sure you want to change the base?
Add security policy #395
Conversation
We should probably check with @petdance about being the security contact. Not sure if that conversation happened somewhere else? |
Another possibility would be to harness GitHub's new Private vulnerability reporting in Security (tab). |
Heavens, no, I shouldn't be a contact for anything. |
Oh, I did not know about this. I've enabled it for this repo. Can we amend the document to reflect this? |
Will do! |
... by GitHub's Report a vulnerability submission form
Done. |
Shall we add a similar SECURITY.md to LWP::UserAgent? |
Please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are some proposed changes in #398. Could you review those? I don't know why it didn't just comment on this PR. Maybe I don't know how to invoke copilot correctly.
I would say Copilot did a good job. It noticed spelling errors and the wrong branch name. |
It looks like I should have requested a review from copilot under the "Reviewers" section. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @mikkoi!
Issue #391