Skip to content
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

[BUG]: Create a Security Policy #4670

Closed
3 tasks done
joycebrum opened this issue May 16, 2023 · 0 comments · Fixed by #4671
Closed
3 tasks done

[BUG]: Create a Security Policy #4670

joycebrum opened this issue May 16, 2023 · 0 comments · Fixed by #4671
Labels
triage New bug, unverified

Comments

@joycebrum
Copy link
Contributor

Required prerequisites

What version (or hash if on master) of pybind11 are you using?

None

Problem description

Hi again, I'd like to suggest another minor change that might improve the overall security posture of pybind11 😄

A Security Policy is a GitHub standard document (SECURITY.md) that can be seen in the "Security Tab" to instruct users about how to report vulnerability in the safest and most efficient way possible.

image

It is a Scorecard Recommendation (being a security measure of medium priority) and a Github Recommendation.

Together with this issue I'll submit one suggestion of Security Policy, feel free to edit it directly or ask me for editions until it is in compliance with how pybind11 would best handle vulnerability reports.

Reproducible example code

No response

Is this a regression? Put the last known working version here if it is.

Not a regression

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage New bug, unverified
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant