chore: secure ci workflow - #481
Merged
Merged
Conversation
Kawron
requested a deployment
to
workflow-approval
August 24, 2026 12:50 — with 
GitHub Actions
Waiting
GitHub Actions
Waiting
Kawron
requested a deployment
to
workflow-approval
August 24, 2026 12:50 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
Unit Test Results192 tests 192 ✅ 40s ⏱️ Results for commit 0793b01. ♻️ This comment has been updated with latest results. |
Kawron
requested a deployment
to
workflow-approval
August 25, 2026 06:58 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
pszkamruk-splunk
approved these changes
Aug 25, 2026
dhruvanshus-crest
approved these changes
Aug 25, 2026
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
3 participants
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.
Replaced
pull_request_targetwithpull_requestto prevent untrusted fork code from accessing repository secrets or write permissions. Fork and Dependabot PRs receive tokenless Semgrep scanning, while same-repository PRs receive authenticated FOSSA and Semgrep jobs. Authenticated scans also run after merge on pushes to develop, master, and release/**.You can read more about why pull_request_target is not secure in this article: https://securitylab.github.com/resources/github-actions-preventing-pwn-requests/.