fix: move id-token: write to job-level for Scorecard API compliance - #455
Conversation
The OpenSSF Scorecard API rejects workflows with global write permissions when publish_results: true. Move id-token: write from the top-level permissions block to the analysis job-level permissions to comply with the action's workflow restrictions.
✅ Deploy Preview for commit-check ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Warning Review limit reached
Next review available in: 49 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
|
Problem
The OpenSSF Scorecard workflow is failing with:
The Scorecard Action v2.4.3 enforces workflow restrictions when
publish_results: true:The workflow had
id-token: writeat the top-levelpermissionsblock, which the Scorecard API treated as a global write permission and rejected with a 400 Bad Request.Fix
Move
id-token: writefrom the top-levelpermissionsto the job-levelpermissionsunder theanalysisjob, keeping onlycontents: readat the top level.Verification
git diffshows only the expected permission scope change