Skip to content

[BUILD]: Add least privilege principle to engine-benchmarks workflow - #903

Merged
michalharakal merged 3 commits into
SKaiNET-developers:developfrom
MacOS:engine-benchmarks-workflow/add-least-privilege
Aug 11, 2026
Merged

michalharakal merged 3 commits into
SKaiNET-developers:developfrom
MacOS:engine-benchmarks-workflow/add-least-privilege

Conversation

@MacOS

@MacOS MacOS commented Jul 30, 2026

Copy link
Copy Markdown
Collaborator

This PR adds the least privilege principle to the engine-benchmarks.yml workflow by setting the contents permissions to read at the workflow level, which sets all other permissions to none (#898).

The OpenSSF Score should increase after this PR has been merged.

This PR is different from #899 because setting all permissions to none at the workflow level had not effect on the OpenSSF score.

@MacOS
MacOS requested review from Copilot and michalharakal July 30, 2026 08:19
@MacOS MacOS self-assigned this Jul 30, 2026
@MacOS MacOS added enhancement New feature or request github_actions Pull requests that update GitHub Actions code labels Jul 30, 2026

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the engine-benchmarks GitHub Actions workflow to follow the principle of least privilege by explicitly restricting the workflow’s GITHUB_TOKEN permissions, supporting the security goals in issue #898 and aiming to improve the OpenSSF Score.

Changes:

  • Set workflow-level permissions to contents: read (implicitly setting all other token permissions to none).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@MacOS

MacOS commented Aug 11, 2026

Copy link
Copy Markdown
Collaborator Author

@michalharakal :)

michalharakal
michalharakal previously approved these changes Aug 11, 2026
The merge conflict resolution with develop kept this PR's original
top-level `contents: read`, dropping develop's `permissions: {}`
(from e187c15) that every other workflow now follows. Both jobs
already declare their own `contents: read`, so behavior is unchanged,
but the fail-safe default matters for any job added later.
@michalharakal
michalharakal merged commit 7383d90 into SKaiNET-developers:develop Aug 11, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants