[codex] Harden Scorecard workflow integration#45
Merged
Conversation
This file contains hidden or 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
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.
Summary
Why
The repository already had a Scorecard workflow, but the current Scorecard report was still penalizing the project for unpinned workflow dependencies and broad workflow token scope. This PR makes the integration visible to users and addresses the workflow hardening issues that can be fixed in-repo.
Validation
npm run lintnpm run buildnpm run test:coveragenpm run pack:checknpx prettier --check .github/workflows/ci.yml .github/workflows/codeql.yml .github/workflows/release.yml .github/workflows/scorecard.yml README.md CHANGELOG.mdNotes
npm run validatein the local checkout is blocked by an unrelated untracked.tasks/README.mdformatting issue that is not part of this PR and will not exist in GitHub Actions.masterpredates this branch, so the score should be re-checked after merge or after a run against this branch.