Repository navigation
ci: publish Scope Guard Scorecard results - #36
Merged
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
Pin Scorecard Action to v2.5.0 and publish the workflow results to the Scorecard API.
Motivation
The workflow currently uploads SARIF but does not publish a result through the Scorecard API. Publication requires
publish_results: trueand job-levelid-token: write(Scorecard Action documentation).Changes
ossf/scorecard-actiontofa7117db83c52d787ae5a89f350999701505d78e(v2.5.0).publish_results: true.Tests performed
actionlint .github/workflows/scorecard.ymlandgit diff --checkpassed.npm ci;npm test(105 passed);npm run coverage(105 passed; configured thresholds met);npm run lint;npm run typecheck;npm run build;npm run package:smoke;npm run action:check; andnpm audit --omit=dev --audit-level=high(0 vulnerabilities) passed.npm ciprinted npm 11’s install-script approval warning foresbuild; the build and Action checks passed.Compatibility
No application runtime or package changes. Local checks ran on Node 26.10.0/npm 11.19.1; hosted Node 22/24 checks are pending.
Security and privacy
The existing job-level
security-events: write,id-token: writeandcontents: readpermissions are sufficient for publication and SARIF upload. No permissions were expanded; the workflow retains empty top-level permissions.Shopify source/evidence
N/A.
Release impact
Repository CI workflow only. No product Action behaviour, package behaviour, documentation, package version or release workflow changes; no npm release.
Checklist