Skip to content

Add OpenSSF Scorecard workflow and badge - #149

Merged
ndgrigorian merged 1 commit into
masterfrom
add-openssf-scorecard-workflow
Jul 29, 2026
Merged

Add OpenSSF Scorecard workflow and badge#149
ndgrigorian merged 1 commit into
masterfrom
add-openssf-scorecard-workflow

Conversation

@xaleryb

@xaleryb xaleryb commented Jul 29, 2026

Copy link
Copy Markdown
Collaborator

Summary

Adds the OpenSSF Scorecard workflow and the corresponding README badge, aligning mkl_random with the other projects in the org.

mkl_random is currently the only one of these repositories without .github/workflows/openssf-scorecard.yml:

Repository openssf-scorecard.yml Scorecard
dpctl yes 8.2
dpnp yes 8.5
mkl_umath yes 8.1
mkl_fft yes 8.2
mkl_random no 7.3

Why it matters beyond the badge

Running the analysis from within the repository lets Scorecard evaluate checks that an external scan cannot see. The published report for mkl_random contains 14 checks, while the other four report 18 — missing are CI-Tests, Contributors, Dependency-Update-Tool and Vulnerabilities, even though .github/dependabot.yml is present and CI is extensive.

Those four checks would score well here, so simply having them evaluated raises the aggregate score without any change to the codebase.

Notes

  • The workflow is copied verbatim from mkl_fft, so every action stays pinned by commit hash and the four projects remain consistent.
  • Top-level permissions: read-all; the elevated security-events: write / id-token: write are scoped to the job, matching the other repositories, so Token-Permissions and Dangerous-Workflow are unaffected.
  • The Upload to code-scanning step publishes Scorecard's own SARIF findings to the Security tab (these are Scorecard results, not code vulnerabilities), same as in the sibling projects. Happy to drop that step if it is not wanted — it does not affect the score.

Related, applied separately via repository rulesets

  • maintenance/1.4.x had no branch protection at all; it now carries the same rules as master (this branch is the target of the 1.4.2 release).
  • master now requires branches to be up to date before merging. Its required status checks were configured but earning no points, because Scorecard's tier evaluation stops early and the unmet tier 2 was suppressing tier 3.

Together these take Branch-Protection from 1 to an expected 8.

Aligns mkl_random with dpctl, dpnp, mkl_umath and mkl_fft, which all run
the Scorecard action from the repository itself.

Running the analysis in-repo lets Scorecard evaluate checks that the
external scan cannot see. The published report for mkl_random currently
contains 14 checks, while the other repositories report 18: CI-Tests,
Contributors, Dependency-Update-Tool and Vulnerabilities are missing even
though .github/dependabot.yml is present.

The workflow is copied verbatim from mkl_fft, so all action versions stay
pinned by commit hash and consistent across the projects.

@antonwolfy antonwolfy left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thank you @xaleryb

@antonwolfy antonwolfy added this to the 1.5.0 release milestone Jul 29, 2026
@ndgrigorian
ndgrigorian merged commit 63e21f0 into master Jul 29, 2026
107 checks passed
@ndgrigorian
ndgrigorian deleted the add-openssf-scorecard-workflow branch July 29, 2026 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants