Strix
v1.7.0 open-sourceThe section your link pointed to isn't on Strix's page any more, so we've brought you to the top.
Strix is an open-source AI penetration testing tool that autonomously finds and fixes vulnerabilities in applications.
strix --target ./app-directory --fail-on high
export STRIX_API_TYPE=responses
export STRIX_LLM="openai/gpt-4o"
export LLM_API_KEY="your-api-key"
strix --target ./app-directory
strix --resume
export STRIX_LLM="openrouter/z-ai/glm-5.3"
export LLM_API_KEY="your-api-key"
strix --target ./app-directory
strix --target ./my-app --workspace-file ./fixtures/test-users.json
strix view my-run-name --host 0.0.0.0 --port 8080 --no-open
export LLM_EXTRA_HEADERS='{"X-Gateway-Token": "my-gateway-secret"}'
export STRIX_LLM="openai/gpt-4o"
export LLM_API_KEY="your-api-key"
strix --target https://your-app.com
strix --target ./openapi.yaml
export STRIX_REASONING_EFFORT=max
strix --target https://your-app.com
strix --update
strix view my-run-name
strix --target-list ./targets.txt
strix --scan-mode quick
curl -sSL https://strix.ai/install | bash
strix scan --instruction ./pentest_instructions.yaml
strix scan 192.168.1.50
strix --non-interactive --target https://example.com
strix --target ./my-repo --target https://staging-api.example.com
Summary
Strix is an open-source AI pentesting tool that runs autonomous agents against an application to find and report exploitable vulnerabilities. It is run from the command line, installable via PyPI, and fits into CI/CD pipelines so scans trigger on pull requests and findings surface before code reaches production; results can also be viewed through a local dashboard. It targets application security and red teams running pentests rather than SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. analysts, with skills covering areas like AWS, GCP, Auth0, Active DirectoryActive DirectoryMicrosoft's directory service for Windows networks that centralises authentication and authorisation; cyber tools target or integrate with it because it controls identity and access across most enterprise environments., and OAuth, and it emits SARIFSARIFStatic Analysis Results Interchange Format, a standard for sharing code-analysis findings, including locations and rule details. It lets scanners report results to a common review interface. output for GitHub code-scanning and ASPMASPMApplication security posture management, combining findings about applications from multiple tools and relating them to business context. It helps teams decide which fixes matter most. ingestion. Development is active, with 66 contributors, over 1,700 commits in the past year, and a release 14 days ago.
Strix is an open-source AI penetration testing tool that autonomously finds and fixes vulnerabilities in applications.
How Strix helps
Which exploitable vulnerabilities exist in this application before it reaches production?
launches autonomous agents against the running app that probe it the way an attacker would, and reports back confirmed, exploitable findings rather than a list of suspicious patterns
Which pull requests are introducing a security hole?
runs the same agent-driven scan in the pipeline on each pull request and surfaces findings before the merge, so an insecure change can be blocked ahead of production
Can an attacker chain a misconfiguration into something in my cloud accounts or identity provider?
draws on built-in skills for AWS, GCP, Auth0, Active Directory and OAuth to attempt the same reconnaissance and abuse paths a real attacker would try against those services
Which dependency vulnerabilities are worth acting on first?
reports software composition findings alongside a severity score for each so the flagged package can be triaged by actual risk rather than by presence alone
How do I get these findings into the code-scanning view my team already uses?
emits results in SARIF format tagged with STRIDE categories, ready for ingestion by GitHub code scanning or an ASPM pipeline
Am I chasing the same vulnerability every time I re-scan this target?
applies a dedicated deduplication step across runs so repeated findings from earlier scans don't reappear as new noise
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for Strix, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Strix puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
20 entries
No entries match these filters.
- October 20261
- September 20263
- August 20262
- July 20264
- June 20261
- May 20261
- March 20261
- February 20262
- January 20262
- December 20251
- November 20252
Project health
Issue, contributor and maintainer activity in usestrix/strix, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 73 +69 vs prior 12 months
- Maintainers 2 +1 joined · −1 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 96% of issues opened, last 12 months
- Median time to close 7.3 days first maintainer reply 45 hours
- Open backlog 165 of 364 issues ever filed
- Issues opened / month 24 · 0 communitymaintainers
- Open backlog 165
- Contributors / month 5
- Commits / month 50
- Stars 62,859
- bugs 36%
- features 23%
- docs 1%
- other 40%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.