ci: declare contents:read on test workflow#904
Conversation
Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
95bbfcf to
76897f4
Compare
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
Summary by CodeRabbit
WalkthroughThe pull request adds a workflow-level ChangesCI Workflow Permissions
🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Adds a workflow-level
permissions: contents: readblock. The job here only checks out the repository and runs its tests / validation; no GitHub API call beyond the initial checkout is needed.CVE-2025-30066 (the March 2025
tj-actions/changed-filessupply-chain compromise) is the canonical motivation: a tampered third-party action exfiltratedGITHUB_TOKENfrom workflow logs and the leaked token retained whatever scope was issued at the workflow level. Per-workflow caps bound that runtime authority irrespective of repo or org default, give drift protection if the default ever widens, and register with OpenSSF Scorecard's Token-Permissions check (which only credits explicit per-workflow declarations).YAML validated locally with
yaml.safe_load.