Improvement of OpenSSF Scorecard Score about argo-cd

[pnacht]

I've taken a look at this issue and it has to do with argo's setup in OSS-Fuzz.

Specifically, Scorecard identifies that a project is fuzzed by OSS-Fuzz by comparing its URL to the main_repo registered in project.yaml. In argo's case, that is main_repo: "https://github.com/argoproj", not [...]/argoproj/argo-cd.

From what I can tell, the main_repo is pointing to the org because the logic in https://github.com/google/oss-fuzz/blob/master/projects/argo actually fuzzes multiple different repositories at the same time.

This setup works well for the project and I in no means suggest changing it. But it unfortunately means Scorecard can't detect it. And there's currently no "workaround" to correct the Scorecard score for this, I'm afraid.

That being said, Scorecard will soon release a new major version (v5.0) that will include a new feature called "Maintainer annotations", which are meant to mitigate precisely this sort of issue. These annotations will allow maintainers to inform users that "hey, Scorecard didn't quite understand what's going on here".

[crenshaw-dev]

I can see fuzzers in the cncf/fuzzing repo for argo-cd, and it is also integrated with OSS-Fuzz, but the fuzzing score remains 0. I am not sure why this is happening. Help from maintainers will be highly appreciated.

I've wondered about this myself. I assume it has something to do with how the OpenSSF Scorecard calculates the fuzzing score.

[harshitasao]

@crenshaw-dev should I proceed with the PR for this?