-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Improvement of OpenSSF Scorecard Score #10457
Labels
Comments
8 tasks
Discussed on a community call on 22.8.2024: These are useful things, so this issue should be kept. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I'm Harshita. I’m working with CNCF and the Google Open Source Security Team for the GSoC 2024 term. We are collaborating to enhance security practices across various CNCF projects. The goal is to improve security for all CNCF projects by both using OpenSSF Scorecards and implementing its security improvements.
After the opening of the scorecard action addition PR, I'm here to increase the final score by going over each check. I've listed all of the checks where work needs to be done, in order of its criticality. I plan to submit each PR for each fix. Please let me know what you think and for which ones a PR is welcome that I will submit it ASAP.
Current Score: 6.3
Scorecard report: https://scorecard.dev/viewer/?uri=github.com/strimzi/strimzi-kafka-operator
Here's a few checks we can work on to improve the project's security posture [ in order of its criticality ]:
Signed-Releases: Score = 0
Token-Permissions: Score = 0
Fuzzing: Score = 0
Pinned-Dependencies: Score = 0
/cc @joycebrum @diogoteles08 @pnacht @nate-double-u
The text was updated successfully, but these errors were encountered: