Practical overview
When it fits
Use Strix when application security needs to be integrated into development and code review. Its documented GitHub Actions and CI/CD integration makes pull-request scanning a specific supported workflow.
Who it is for
- Development teams adding automated security checks to application workflows
- Application-security teams performing vulnerability discovery and remediation
- Teams using GitHub Actions or CI/CD pipelines for pull-request checks
Documented uses
- Discover vulnerabilities in applications with autonomous AI agents
- Help investigate and remediate identified application vulnerabilities
- Scan pull requests as part of a CI/CD security workflow
- Support AI-assisted bug-bounty or CTF testing workflows
Requirements & limits
The project is open source under the Apache-2.0 license. It is available as a public, active GitHub repository and is documented for Cloud, self-hosted and server environments.
- Whether autonomous AI penetration testing fits the team’s application-security workflow
- Need for GitHub Actions or CI/CD integration, including pull-request scanning
- Preference for an open-source Python project licensed under Apache-2.0
- Whether deployment should run in Cloud, self-hosted or server environments
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Add Strix vulnerability scanning to GitHub Actions pull requests
Run a Strix security test for pull requests in a GitHub Actions workflow.
Before you start
- A GitHub repository using GitHub Actions
- Docker-capable GitHub Actions runner configuration as documented by the workflow
STRIX_LLMandLLM_API_KEYrepository secrets
Steps
Create a workflow triggered by
pull_request.Check out the repository with
actions/checkout@v6andfetch-depth: 0.Install Strix with the command below.
curl -sSL https://strix.ai/install | bashExpose
STRIX_LLMandLLM_API_KEYfrom repository secrets, then runstrix.
Expected outcome
The workflow runs Strix as a pull-request security test; the documented integration is intended to identify vulnerabilities before production.
Guide limitations
- The source does not document repository permissions, branch-protection configuration, or how to configure a specific blocking policy.
- The source does not document runner costs, duration, or compatibility beyond the shown workflow.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 30 September 2026
- Original website title
- usestrix/strix · Official homepage title · retained in its source language

