Skip to content

Reintroduce the Scorecard workflow #3604

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

Open
ppkarwasz opened this issue Apr 12, 2025 · 3 comments
Open

Reintroduce the Scorecard workflow #3604

ppkarwasz opened this issue Apr 12, 2025 · 3 comments

Comments

@ppkarwasz
Copy link
Contributor

We should reconsider enabling the Scorecard action, considering especially that:

  • A Scorecard for Apache Log4j is computed anyway, since Scorecards are computed for 1 million critical projects. Running the action ourselves we have more control on what the public sees.
  • We enabled mandatory PR reviews, so random pushes to our default branch will not decrease our score.

Blocked by ossf/scorecard-webapp#554

@ppkarwasz
Copy link
Contributor Author

@vy, what do you think?

@vy
Copy link
Member

vy commented Apr 15, 2025

We had enabled Scorecards, and it helped with

  1. Creating a maintenance burden (Remember how many times we needed to fix its CI workflow?)
  2. Bringing literally no value by any means

A Scorecard for Apache Log4j is computed anyway, since Scorecards are computed for 1 million critical projects.

Right, and hence, I don't see the reason to duplicate that work. Users interested in Log4j's Scorecards, can find it anyway.

we have more control on what the public sees

Do you imply that OSSF is manipulating the scores? Or, we can manipulate the scores as we see fit?

@ppkarwasz
Copy link
Contributor Author

we have more control on what the public sees

Do you imply that OSSF is manipulating the scores? Or, we can manipulate the scores as we see fit?

No, but the data is hard to find (it requires a Google Cloud account) and it is difficult to check what the score is. We don't need to announce the score via a badge, but we can still compute it.

@ppkarwasz ppkarwasz moved this from To triage to Ready in Log4j bug tracker Apr 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Ready
Development

No branches or pull requests

2 participants