ci(semgrep): declare contents: read on the daily scan#9
Open
arpitjain099 wants to merge 1 commit into
Open
Conversation
Drops the default `GITHUB_TOKEN` scope down to read-only for the only workflow in the repo. Semgrep findings are reported to Cloudflare's internal Semgrep instance via `SEMGREP_APP_TOKEN`, so the GitHub token only needs to read the checkout. Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
Author
|
I have read the CLA Document and I hereby sign the CLA |
arpitjain099
force-pushed
the
ci/add-permissions
branch
from
7458d3e to
fcf96d7
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds a top-level
permissions: contents: readtosemgrep.yml, the sole workflow here. The scan runs in the officialreturntocorp/semgrepcontainer, reads the checkout, and reports findings to Cloudflare's own Semgrep AppSec instance viaSEMGREP_APP_TOKEN— none of that requires write scopes on the GitHub token.Verified with
yaml.safe_load.