Improvement of OpenSSF Scorecard Score

[harshitasao]

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.3

Scorecard report: https://scorecard.dev/viewer/?uri=github.com/openkruise/kruise

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

• Vulnerabilities: Score = 8

  • After running the osv scanner locally, a significant amount of vulnerabilities were found that need to be fixed.
  • May need to add an osv-scanner.toml to mark some of these as not impacting/ignored.
  • Open vulnerabilities are easily exploited by attackers and should be fixed as soon as possible.

• Token-Permissions: Score = 9

  • 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: fix: fixed the token-permission and pinned dependencies issue #1707

• Fuzzing: Score = 0

  • Integrating the project with OSS-Fuzz by following the instructions here. The most difficult one on the list, maintainers help, is highly appreciated. For example, helping in identifying the components where fuzz testing will be added.
  • Issue: [feature request] Add fuzz-testing #1713

• Pinned-Dependencies: Score = 0

  • Github actions and container images in dockerfile are not pinned by hash, which results in a low score. But pinning container images would introduce the risk of running outdated images.
  • Pinning dependencies to a specific hash rather than allowing mutable versions or ranges of versions improves supply chain security.
  • PR: fix: fixed the token-permission and pinned dependencies issue #1707

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