Harden link checker workflow dependencies - #266
Celeste de Guzman (CelesteDG) wants to merge 1 commit into
Conversation
Pin third-party actions to immutable release commits and reduce token exposure in the scheduled link checker. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Learn Build status updates of commit fa4ba60: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Celeste de Guzman (@CelesteDG) - Do you want us to wait for Mark's approval or go ahead and merge? #label:"aq-pr-triaged" |
Summary
lycheeverse/lychee-actionandpeter-evans/create-issue-from-fileto immutable release commit SHAsactions/checkoutv3.7.0 pin and prevent it from persisting credentialscontentspermission from write to readSecurity impact
The workflow previously executed two third-party actions from mutable branch references during scheduled, push, and dispatch runs with a write-scoped
GITHUB_TOKEN. Compromise of either upstream branch could therefore execute untrusted code with repository permissions (CWE-829).This change preserves the existing triggers, preprocessing,
.lychee.tomlconfiguration, failure behavior, and automated issue reporting while reducing token exposure.Pinned releases
actions/checkoutv3.7.0 (existing pin)lycheeverse/lychee-actionv2.9.0peter-evans/create-issue-from-filev6.0.0Validation