-
Notifications
You must be signed in to change notification settings - Fork 11
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
Project risk assessment process/docs - NEW - OSPS-DO-17 #120
base: main
Are you sure you want to change the base?
Conversation
added proposal for OSPS-DO-18 for project's risk assessment process & docs Signed-off-by: CRob <[email protected]>
Signed-off-by: CRob <[email protected]>
The term "threat" is really vague, it's not clear what level we're discussing. E.g., is this a list of threats?: "Unintentional vulnerability in our code", "Malicious vulnerability in our code", "Vulnerability in dependency", "Insecure design"? Can we suggest a specific list as a starting point? Can we identify some OSS projects as examples who have done this? For all our criteria we should be pointing to projects that have done it. |
Co-authored-by: David A. Wheeler <[email protected]> Signed-off-by: CRob <[email protected]>
Co-authored-by: David A. Wheeler <[email protected]> Signed-off-by: CRob <[email protected]>
added proposal for OSPS-DO-18 for project's risk assessment process & docs