chore: use grok-build-0.1 for SquidGate - #1
Merged
Conversation
🛡️ Security Scan ResultsThe added workflow uses an unpinned third-party action, introducing a supply chain risk. MEDIUM — Unpinned third-party GitHub ActionFile: The workflow references the third-party action 'SquidSec/SquidGate@v1' using a mutable tag instead of a specific commit SHA. This allows supply chain attacks if the tag is moved to point to malicious code. CWE: CWE-829 | OWASP: A06:2021 Recommendation: Pin to a full commit SHA: uses: SquidSec/SquidGate@. Consider the same for actions/checkout@v4. |
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.
Point SquidGate at xAI grok-build-0.1 (custom provider, api.x.ai). Uses LLM_API_KEY repo secret.