-
Notifications
You must be signed in to change notification settings - Fork 26
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
Adopt Secure Software Development Best Practices of OpenSSF Scorecard #159
Comments
Below is a scan result of the current state of the repo: Low hanging fruits seem to be
Results:
|
@Phil-Friderici @anders-larsson: Quick update: the ScoreCards score of the repo is up from 4.8 to 6.6! I am going to address two more ScoreCards recommendations shortly.
Thanks |
Hi, Sounds OK. I was looking at adding branch production but it appears we lost access to that functionality. I'm all for enabling it though. BR |
@anders-larsson The intention is that you should be able to maintain these settings for your projects. I have upgraded your team to the admin role for the puppet repos. |
Both options (branch protection / security.md) sounds good to me too. |
Thanks for the feedback. I just enabled the branch protection rules. |
I'd like to propose to evaluate and (selectively) adopt secure software development best practices recommended by the Open Source Security Foundation (OpenSSF) [1]. The OpenSSF Scorecard project checks various development best practices of open source projects hosted on GitHub and provides guidance on how to improve those practices [2]. The overall goal of this issue is to adopt best practices to further mature the project.
The proposed steps include:
[1] https://openssf.org/
[2] https://github.com/ossf/scorecard/tree/main#scorecard-checks
The text was updated successfully, but these errors were encountered: