-
Notifications
You must be signed in to change notification settings - Fork 496
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
Test for security policy in other places than SECURITY.md #4192
Comments
What people think about this? Should we try to address it with a pr? |
Hey @CsatariGergely! I think this could be a positive change, as many projects indeed have the content of a security policy directly on their README. But I'm not sure if this would be worth a 10/10, because there is also some value on having a dedicated SECURITY.md, as:
That said, I'd be in favor of a PR, but I'd first define a more detailed plan for the resultant scoring. WDYT, @spencerschrock @raghavkaul |
Having a SECURITY.md is a well known convention. If we start parsing the README, my thoughts go to detection mechanisms and false positives. Do we know how widespread the issue is? And what we'd be looking for in a README? |
I agree with this. The extent to which a That said, I would definitely be in support of an additional check for the presence of |
Is your feature request related to a problem? Please describe.
There are lots of projects which are describing their security policy in other places, than a SECURITY.md file.
Describe the solution you'd like
Expected content of a security policy should be checked in README.md also.
Describe alternatives you've considered
None
Additional context
None
The text was updated successfully, but these errors were encountered: