scorecard workflow #156
Merged
scorecard workflow #156
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Manually creating a workflow to publish an OpenSSF scorecard.
dani-santos-code
approved these changes
Jul 27, 2023
This was referenced Jul 27, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Manually creating a workflow to publish an OpenSSF scorecard. We want hansel's users to be assured of our security practices, and scorecards offer us a way to measure and demonstrate.
This uses a shared workflow in https://github.com/Shopify/github-workflows to centralize how the scorecard is created and published, we only provide that workflow with permission to:
contents:read), so it has a local copy of the source to inspectid-token: write), so it can publish results to the Scorecards serviceWe pass an organization-level
SCORECARD_TOKENas an argument, which grantsadministration:readpermissions that aren't available to Actions by default. This allows the scorecard action to inspect branch protection settings of the repository, and include that in the generated results.Testing instructions
We could remove the branch filter from theThe action requires it be run from the default branch. It will first run when the PR is merged (and ideally subsequently as it shames me into improving branch protection settings 😆 ).pushtrigger to test this in a branch.