Repository navigation
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.
HIGH (Security Scan): Same-repository pull requests from non-Dependabot users are routed to the cached runner. PR code can execute during CI, so a malicious or compromised contributor can target the runner’s cached state and any credentials or other resources available to that runner. The previous configuration used GitHub-hosted runners.
Suggestion: Run pull-request code on an isolated, ephemeral GitHub-hosted runner, or ensure the cached runner is ephemeral and isolated from credentials and other jobs. Restrict cached-runner use to trusted code if that isolation cannot be guaranteed.
Evidence:
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.
Not a bug: only same-repo PRs reach the cached runner, and opening one needs write access to this repo, which is the same trust an org member already has to merge. Fork and Dependabot PRs stay on GitHub-hosted runners. The cached runner holds no registry or App secrets and nothing it builds is published: pushes and publishes run on the uncached, tmpfs-backed runner. This is the accepted design from crunchtools/trentina security.yml (fleet sweep a275).