Improvement of OpenSSF Scorecard Score

[harshitasao]

What would you like to be added?

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.

As this project already has scorecard action, 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: 8.9 Improved Score: 9.7

Scorecard report: https://scorecard.dev/viewer/?uri=github.com/cri-o/cri-o

Here's a few checks we can work on to improve the project's security posture:

• [X] Token-Permissions: Score = 0

  • The issue here is that many workflows doesn’t have a top-level read-only permissions block like present in the other workflows. Scorecard is quite severe in this check: a single workflow without top-level permissions gets a 0/10 for the check.
  • PR: https://github.com/cri-o/cri-o/pull/8487

• [X] Pinned-Dependencies: Score = 8

  • Some github actions and go commands are not pinned by hash, which results in a low score. But pinning go commands would introduce the risk of running outdated versions.
  • Pinning dependencies to a specific hash rather than allowing mutable versions or ranges of versions improves supply chain security.
  • PR: https://github.com/cri-o/cri-o/pull/8487

/cc @joycebrum @diogoteles08 @pnacht @nate-double-u

[harshitasao]

Closing this issue, as all the task are done!

[kwilczynski]

@harshitasao, thank you for taking care of this! Much appreciated!