Skip to content
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

scorecard: publish results & run weekly #1829

Open
planetf1 opened this issue Jul 1, 2024 · 1 comment
Open

scorecard: publish results & run weekly #1829

planetf1 opened this issue Jul 1, 2024 · 1 comment
Assignees

Comments

@planetf1
Copy link
Contributor

planetf1 commented Jul 1, 2024

When the scorecard support was added it was agreed to run in the PR, and not publish results

We now need to

  • publish the results to openssf
  • run the checks periodically (weekly is the default example from openssf)
  • remove the PR execution
  • add the openssf badge to the repo/dashboard

Followon to #1706

@planetf1 planetf1 self-assigned this Jul 1, 2024
@baentsch
Copy link
Member

baentsch commented Jul 8, 2024

Well, didn't we want to publish results score(s) when they are satisfactory, no?

So, what is a "good/satisfactory score"? What would be needed to achieve it? When and by whom is this worked on? Should this be a(n earlier) line item in the list above?

So, in order to get some answers on these questions, here's some "score card" results of pretty relevant projects, e.g., openssl has 6.6, nginx has 4.8, and kubernetes has 7.4.

So liboqs with 8.1 "beats" all of them: A project with a razor-thin support base has a higher score than some of the most important and most well-maintained projects on GH..... Am I the only one that is a bit surprised now?

In consequence, I think you can discard this comment, @planetf1 . I just post it for posterity (and anyone else wondering) after having gone through this review. Looking at the above, I'm not sure this issue should be high on any work priority list, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

2 participants