ci: add Strix security scanning for Chronos - #15
Closed
sx4im wants to merge 2 commits into
Closed
Conversation
Wire up headless Strix scans on pull requests and manual dispatch so Chronos can be security-tested with validated findings and SARIF upload. Requires STRIX_LLM and LLM_API_KEY repository secrets. Co-authored-by: Saim <contact@saimshafique.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Avoid failing PR checks before STRIX_LLM and LLM_API_KEY are configured. Co-authored-by: Saim <contact@saimshafique.com>
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
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.
Summary
Adds a GitHub Actions workflow that runs Strix (open-source AI pentesting) against Chronos on pull requests and via manual
workflow_dispatch.What's included
.github/workflows/strix-security.yml— headlessquickscan with PR diff-scope, completion check, SARIF upload, and artifact uploadSTRIX_LLM/LLM_API_KEYsecrets are not configured yet.gitignore— ignorestrix_runs/scan artifactsLive scan status (cloud agent)
Strix 1.5.2 was installed and the sandbox image
ghcr.io/usestrix/strix-sandbox:1.3.0was pulled successfully. A full scan could not be completed in this environment because:LLM_API_KEY/STRIX_LLM(orSTRIX_API_TOKENfor app.strix.ai) is available to the agentllama3.1:8b) fallback was attempted; Strix abandoned turns after 300s with no stream events (CPU inference too slow for agent prompts)Result: 0 validated findings (scan interrupted before analysis).
Required to complete the scan
Add repository secrets, then re-run the workflow (Actions → Strix Security Scan → Run workflow), or reply with a key so the agent can finish:
STRIX_LLM— e.g.openai/gpt-5.4oranthropic/claude-sonnet-4-6LLM_API_KEY— provider API keyAlternatively, create a token at app.strix.ai → Settings → API Access and use the managed cloud path (
STRIX_API_TOKEN) with no local Docker/LLM.