Open-source AI penetration testing tool to find and fix your app’s vulnerabilities.
This week brought substantial fixes to Docker connection handling—better error messages, proper context handling, and alignment with how the Docker CLI itself connects. The CLI now runs headless when no terminal is attached instead of crashing, and users can interactively pick and resume prior runs…
Get this in your inbox every Monday →A deterministic 0–100 hygiene score — README, license, CI, tests, docs, and freshness.
Who ships this repo — author concentration and the bus factor across the last 300 mainline commits.
How welcoming this repo is to contributors — issue throughput, close time, responsiveness, and good-first-issue count.
What this project is built on — dependency count by ecosystem, the license mix, and anything worth a legal look before you adopt it.
Whether this project's CI can be trusted — pass rate, run times, flaky runs, and which workflow is the weak link.
Grounded in strix's README, structure, and recent commits — answers won't invent code they haven't seen.
A Monday email with what shipped, in plain English — no account needed.
Showing raw commit titles for the newest commits. Sign in to generate AI summaries.
feat(cli): add -r for --resume and a title column to the resume picker
Stop false "ended without calling finish_scan" error on PR reviews (#1449)
prompts: let the verified user define and change scope in chat (#1443)
fix(execution): only unpark a silent wait_for_user while the agent is still waiting on the user
fix(docker): keep DOCKER_HOST on from_env so TLS settings apply; a missing current context is an error
A floor, not a guess: counts only commits whose author, co-author trailer, or message explicitly credits an AI tool (Claude, Copilot, Cursor, aider, Codex…). Based on 30 mainline commits. Unattributed AI code isn't counted here — the full audit estimates that separately.