Repository navigation
Check that each Scorecard run reached scorecard.dev - #38
Merged
Merged
Conversation
scorecard-action reports a failed publish as a warning on a green run. On 2026-11-09 a publish from askalf/pitlane was answered 500, scorecard.dev served "not found" for the repository for fifteen hours, and the README badge read "invalid repo path" with no run red. scorecard-publish.yml runs askalf/ci's scorecard-publish-check action on workflow_run of the Scorecard workflow: a successful run whose result is not at scorecard.dev gets one more dispatch, and a dispatch that is unpublished too fails the job.
askalf
marked this pull request as ready for review
November 10, 2026 03:23
askalf
enabled auto-merge (squash)
November 10, 2026 03:25
sprayberry-redline
approved these changes
Nov 10, 2026
sprayberry-redline
left a comment
sprayberry-redline
left a comment
Collaborator
There was a problem hiding this comment.
Verdict: approve. The new workflow targets completion of the existing Scorecard workflow and limits execution to successful runs in public repositories. The action is pinned to a commit, runs without a checkout, and receives only the actions permission needed for a retry dispatch.
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.
What and why
scorecard-actionreports a failed publish to scorecard.dev as a warning, and the run stays green. On 2026-11-09 that happened to askalf/pitlane: its publish was answered 500, scorecard.dev served "not found" for the repository for about fifteen hours, and the README badge read "invalid repo path" with no run red. This repository shows the same badge and publishes the same way.This adds
.github/workflows/scorecard-publish.yml, the caller askalf/ci's README gives for itsscorecard-publish-checkaction (askalf/ci#199). Onworkflow_runofScorecard, for a run that succeeded on the default branch, the action reads what scorecard.dev serves for the repository. If the run's result is not there it dispatches Scorecard once more; if the unpublished run was itself a dispatch, the job fails. It is a workflow of its own because scorecard.dev accepts results only from a job whose steps it recognises.The job runs on a GitHub-hosted runner with
actions: writeand no other permission, and checks out nothing. The action is pinned at the commit that added it; the pin bump moves it with the other askalf/ci pins.It ran for the first time on askalf/ci's
mainon 2026-11-10 after askalf/ci#200: it read the run from the event and reportedpublished: scorecard.dev serves a result dated 2026-11-10T03:17:46Z for askalf/ci; run 42748482341 started 2026-11-10T03:17:37Z. The retry path has not run for real, since no publish has failed since.Checks
npm testpasses (268 pass, 0 fail)npm run buildrun anddist/committed (not needed: no source file changes)docs/rules.md(no rule changes)