-
Notifications
You must be signed in to change notification settings - Fork 0
Fix cross-target toolchain setup #26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security & Privacy | 🛡️ Analyzed with Security Review | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
sed -n '1,115p' .github/workflows/test-build-options.ymlRepository: Reloaded-Project/devops-rust-lightweight-binary
Length of output: 3630
🏁 Script executed:
Repository: Reloaded-Project/devops-rust-lightweight-binary
Length of output: 33596
🌐 Web query:
official actions/checkout persist-credentials default README💡 Result:
The
persist-credentialsinput for the officialactions/checkoutGitHub Action has a default value oftrue[1][2]. When set totrue(the default), the action configures the authentication token or SSH key used to fetch the repository into the local git configuration [1][3][2]. This allows subsequent steps in your workflow to execute authenticated git commands (such asgit fetchorgit push) automatically [1][3]. The credentials are removed during the post-job cleanup [1][3]. In recent versions ofactions/checkout, the implementation of this persistence has been improved for security; credentials are now stored in a separate file within$RUNNER_TEMPrather than directly in.git/config[1][4]. If you wish to prevent the action from persisting these credentials, you can explicitly setpersist-credentialstofalsein your workflow configuration [1][3].Citations:
Sensitive Data Exposure
CWE: CWE-522 — Insufficiently Protected Credentials
Do not retain checkout credentials during the build.
The local action runs
cargoin the checked-out external project. If its build scripts or dependencies run Git commands, persisted checkout credentials can authenticate those commands. Setpersist-credentials: falseon both checkout steps.Proposed fix
- name: Checkout Action uses: actions/checkout@v6 + with: + persist-credentials: false - name: Checkout Test Repository uses: actions/checkout@v6 with: + persist-credentials: false repository: Sewer56/prs-rs🧰 Tools
🪛 GitHub Check: CodeQL
[warning] 15-96: Workflow does not contain permissions
Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {{contents: read}}
🪛 zizmor (1.29.0)
[warning] 77-78: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false
(artipacked)
[warning] 1-396: overly broad permissions (excessive-permissions): default permissions used due to no permissions: block
(excessive-permissions)
[warning] 14-94: overly broad permissions (excessive-permissions): default permissions used due to no permissions: block
(excessive-permissions)
🤖 Prompt for AI Agents
Source: Linters/SAST tools