Skip to content

Conversation

AdamKorcz
Copy link

This PR adds the Scorecard action to Notebooks’s CI.

Scorecard is a tool that scans for a number of supply-chain threats and assesses whether Notebook mitigates these threats. Running Scorecard allows projects to avoid degradation in its development pipeline, ie. the action continuously monitors for all Scorecards heuristics and alerts if a given PR increases the risk of a given threat. Projects can also add a badge to demonstrate their Scorecard score.

I highly recommend enabling the “Branch-Protection” check which is disabled in this PR, however, for instructions on enabling it, see the workflow.

Signed-off-by: Adam Korczynski <[email protected]>
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign kimwnasptd for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@AdamKorcz AdamKorcz changed the title CI: Add Scorecard workflow ci: Add Scorecard workflow Sep 9, 2025
Copy link
Contributor

@andyatmiami andyatmiami left a comment

Choose a reason for hiding this comment

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

We will need to rework this PR a bit to account for the fact that actual feature development occurs on a couple non-standard branches:

  • notebooks-v1
  • notebooks-v2

It is also important to note that the notebooks-v1 and notebooks-v2 branches themselves are wholly unrelated/mutually exclusive/contain completely different code bases.

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

Successfully merging this pull request may close these issues.

2 participants