PAGES
← all tools
◆ AI-Powered Offensive Security

Strix

v1.7.0 open-source

Strix is an open-source AI penetration testing tool that autonomously finds and fixes vulnerabilities in applications.

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

all 20 features, with the evidence for each →

Languages

Not documented

Features

20 capabilities across 6 areas · 5 backed by code, an API document or a real run

Built from Strix's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • Strix covers 1 of the 5 supply chain security capabilities we track.

What Strix offers you

  • Command-line interface4
  • CI/CD pipeline integration1
Vulnerability Scanning and Testing 4 capabilities Strix performs AI-driven penetration testing against web applications, APIs, and cloud environments, covering a wide range of attack techniques out of the box. It accepts live targets, API specs, and batch scope files, then executes skills autonomously to find exploitable weaknesses.
AI-driven penetration testing skills shipped Runs a built-in and extensible library of penetration testing skills across authentication, cloud platforms, frameworks, and infrastructure without manual configuration per test. 34 releases · 4 other sources · first seen Nov 2025

release 34 total

  • Prompts agents to include local Git blame in technical details of findings. v1.7.0 · Oct 2026 · source · release history
  • Requires http_exchange_ids for proxy-validated findings, linking HTTP exchange evidence directly to reported vulnerabilities. v1.7.0 · Oct 2026 · source · release history
  • Adds the ability for agents to delete a vulnerability report they previously filed. v1.7.0 · Oct 2026 · source · release history
  • Adds Exa as a web search provider alongside Perplexity for agent-driven reconnaissance. v1.6.2 · Sep 2026 · source · release history
  • feat(web_search): add Exa as a web search provider alongside Perplexity v1.6.2 · Sep 2026 · source · release history
  • Adds semantic browser and Electron security skills. v1.6.0 · Sep 2026 · source · release history

docs

  • Autonomous AI penetration testing agents that find, validate, and fix application vulnerabilities using real exploit proof-of-concepts.

example

  • Scan a raw IP address directly when the target has no hostname or DNS record. strix scan 192.168.1.50 v0.4.0 · Nov 2025 · source
  • Grey-box authenticated testing strix --target https://your-app.com --instruction "Perform authenticated testing using credentials: user:pass"
  • Black-box web application assessment strix --target https://your-app.com
Software composition analysis (SCA) shipped Identifies vulnerable third-party dependencies, traces the full transitive chain, reports CVSS scores, and rates how reachable each vulnerability is from exploitable down to theoretical. 11 releases · 1 other source · first seen Jul 2026

Shared capability: Dependency scanning

release 11 total

  • Adds contextual CVSS breakdown and requires usage evidence on dependency reports. v1.6.0 · Sep 2026 · source · release history
  • Adds contextual CVSS breakdown and required usage evidence on dependency vulnerability reports. v1.6.0 · Sep 2026 · source · release history
  • SCA findings now include a structured reachability evidence ladder for dependency vulnerabilities, grading confidence from theoretical to exploitable. v1.5.0 · Aug 2026 · source · release history
  • Requires a repo-relative manifest_path field on dependency CVE findings in reports. v1.5.0 · Aug 2026 · source · release history
  • Dependency CVE findings now require a repo-relative manifest_path field, giving precise location context in reports. v1.5.0 · Aug 2026 · source · release history
  • Adds a structured reachability evidence ladder for dependency findings. v1.5.0 · Aug 2026 · source · release history

example

  • Scan a local codebase strix --target ./app-directory
Multi-target batch scanning shipped Reads a file of multiple targets so an entire bug-bounty scope or asset list can be scanned in a single run. 3 releases · 3 other sources · first seen Nov 2025

Also counts toward: Command-line interface

release

  • Adds --target list-file CLI option to scan multiple targets specified in a file (#711) v1.1.0 · Jul 2026 · source · release history
  • Adds --target-list CLI option to supply multiple targets from a file. v1.1.0 · Jul 2026 · source · release history
  • Enables multi-target scanning to assess repos, URLs, and APIs in a single execution v0.3.1 · Nov 2025 · source · release history

example

  • Scan multiple repositories specified in a file using the new list-file target option strix scan --target targets.txt v1.1.0 · Jul 2026 · source
  • Scan a list of targets (e.g., all apps in scope for a bug-bounty engagement) from a file rather than passing each on the command line. strix --target-list ./targets.txt v1.1.0 · Jul 2026 · source
  • Scan multiple components (a local repo and a staging API) simultaneously to perform a full-stack assessment. strix --target ./my-repo --target https://staging-api.example.com v0.3.1 · Nov 2025 · source
API specification scanning shipped Takes an OpenAPI, Swagger, or Postman collection file as a scan target and tests every declared endpoint against the live server directly. 2 releases · 2 other sources · first seen Aug 2026

release

  • Supports API specs and Postman collections as scan targets. v1.5.0 · Aug 2026 · source · release history
  • Supports API specs (OpenAPI/Swagger) and Postman collections as scan targets, letting agents test every declared endpoint without crawling. v1.5.0 · Aug 2026 · source · release history

example

  • Scan every endpoint declared in an OpenAPI spec against a live staging server, skipping crawl-based discovery. strix --target ./openapi.yaml v1.5.0 · Aug 2026 · source
  • Test API endpoints from OpenAPI spec strix --target ./openapi.yaml --target https://api.your-app.com
AI Agent Infrastructure 4 capabilities Strix manages the LLM-powered agent that drives scanning, controlling which models and providers are used, how much context the agent holds, and what the scan costs. These controls make long, complex scans reliable and predictable.
LLM provider and model configuration verified Lets the user choose from multiple inference providers and models, with fine-grained controls over how the agent calls tools, streams responses, and caches prompts. 31 releases · 8 other sources · first seen Jan 2026

release 31 total

  • Adds a structured per-attempt provider request log with provider request IDs for LLM call traceability. v1.7.0 · Oct 2026 · source · release history
  • Adds STRIX_API_TYPE environment variable to force the Responses API vs chat completions endpoint, overriding model-based auto-detection. v1.7.0 · Oct 2026 · source · release history
  • Adds STRIX_API_TYPE environment variable to force responses vs chat completions. v1.7.0 · Oct 2026 · source · release history
  • Adds openrouter/z-ai/glm-5.3 as the new top recommended model, with GLM-5.3, Fable 5.1, and Gemini 3.7 Flash added to the recommended model list. v1.6.1 · Sep 2026 · source · release history
  • Adds GLM-5.3, Fable 5.1, and Gemini 3.7 Flash to the recommended model list (with openrouter/z-ai/glm-5.3 as the top pick). v1.6.1 · Sep 2026 · source · release history
  • Improves scan startup performance by bootstrapping Caido concurrently with the scan start. v1.6.0 · Sep 2026 · source · release history

command line

example

  • Force Strix to use the Responses API instead of chat completions when your provider or model requires it. export STRIX_API_TYPE=responses export STRIX_LLM="openai/gpt-4o" export LLM_API_KEY="your-api-key" strix --target ./app-directory v1.7.0 · Oct 2026 · source
  • Switch to the new top-pick model for a pentest scan without editing config files. export STRIX_LLM="openrouter/z-ai/glm-5.3" export LLM_API_KEY="your-api-key" strix --target ./app-directory v1.6.1 · Sep 2026 · source
  • Route Strix through a corporate proxy or inject an auth header when using a self-hosted OpenAI-compatible LLM gateway. LLM_EXTRA_HEADERS='{"X-Custom-Auth": "Bearer <token>"}' strix scan <target> v1.5.0 · Aug 2026 · source
  • Disable streaming for a local LLM endpoint that returns responses only after completion, preventing scan hangs. LLM_DISABLE_STREAMING=1 strix scan <target> v1.5.0 · Aug 2026 · source
  • Push the LLM to use maximum reasoning effort on a complex target when using a provider that supports the setting. export STRIX_REASONING_EFFORT=max strix --target https://your-app.com v1.5.0 · Aug 2026 · source
  • Push a supported reasoning model to maximum effort when scanning a complex target. STRIX_REASONING_EFFORT=max strix scan <target> v1.5.0 · Aug 2026 · source
Docker sandbox isolation and resource control shipped Runs the scan agent inside a Docker sandbox with optional CPU and memory limits, directory mounts for large repositories, and a smaller image variant for constrained environments. 12 releases · first seen Jul 2026

release 12 total

  • Makes read_only local sources become :ro bind mounts in the container runtime. v1.7.0 · Oct 2026 · source · release history
  • Adds lazy initialization of MCP connections so connections are not established until actually needed. v1.7.0 · Oct 2026 · source · release history
  • Adds --workspace-file CLI flag and extra_files config key to place caller-provided files into the sandbox workspace before a scan starts. v1.6.0 · Sep 2026 · source · release history
  • Adds extra_files config key and --workspace-file CLI argument to place caller-provided files into the sandbox workspace before a scan runs. v1.6.0 · Sep 2026 · source · release history
  • Mounts local targets into the sandbox instead of copying them, reducing setup overhead. v1.5.0 · Aug 2026 · source · release history
  • Mounts local targets into the sandbox instead of copying them, reducing startup overhead for local directory scans. v1.5.0 · Aug 2026 · source · release history
Context and agent memory management shipped Keeps agent memory within model context limits by capping tool output size, spilling large outputs to disk, and compacting conversation history automatically. 9 releases · first seen Nov 2025

release 9 total

  • Initializes MCP connections lazily to reduce startup time. v1.7.0 · Oct 2026 · source · release history
  • Changes MCP error handling so that call errors no longer quarantine the connection. v1.6.1 · Sep 2026 · source · release history
  • MCP call errors no longer quarantine the connection, keeping MCP integrations live after transient failures. v1.6.1 · Sep 2026 · source · release history
  • Adds MCP server support, with per-task connection isolation and connection status surfaced in the UI. v1.6.0 · Sep 2026 · source · release history
  • Adds MCP server support, with connections isolated per task, on-demand tool resolution instead of bulk registration, and connection status surfaced in the UI; connections survive transient transport failures. v1.6.0 · Sep 2026 · source · release history
  • Bounds per-tool output before it enters agent history, and spills oversized output to the sandbox workspace instead of dropping it. v1.4.0 · Jul 2026 · source · release history
LLM cost tracking and budget control verified Tracks LLM token spend in real time, enforces a configurable USD budget cap with warnings, and lets the user pause or continue when the limit is approaching. 8 releases · 1 other source · first seen Jun 2026

Also counts toward: Command-line interface

release 8 total

  • Adds budget_policy=pause to park every agent at the cost limit until the operator explicitly resumes, preventing runaway spend. v1.7.0 · Oct 2026 · source · release history
  • Adds budget_policy=pause setting to park agents at the cost limit until resumed by the operator. v1.7.0 · Oct 2026 · source · release history
  • Adds graduated wrap-up warnings, a budget reserve, and an interactive budget pause/continue flow during scans. v1.4.0 · Jul 2026 · source · release history
  • Reports cost for streamed OpenRouter calls and attributes OpenRouter usage to the Strix app. v1.1.0 · Jul 2026 · source · release history
  • Attributes OpenRouter usage to the Strix app for accurate billing/tracking (#760) v1.1.0 · Jul 2026 · source · release history
  • Adds --max-budget-usd flag to cap token/cost spend per scan. v1.1.0 · Jul 2026 · source · release history

command line

  • --max-budget-usd — Maximum LLM cost in USD (> 0). The scan stops cleanly when this limit is reached. Graduated wrap-up warnings are sent to all agents as it is approached. v1.5.0 · Aug 2026 · command-line history
Reporting and Integration 4 capabilities Strix produces structured output designed for ingestion by code-scanning platforms and ASPM tools, and exposes reports programmatically for downstream automation. A local web viewer provides a human-readable interface with run history and report delivery.
Local results viewer verified Serves a local web interface showing run history, a scan switcher, email report delivery, and links to the broader platform suite. 11 releases · 5 other sources · first seen Nov 2025

release 11 total

  • Adds --host option to strix view to expose the local results viewer on a custom interface (e.g. --host 0.0.0.0). v1.6.0 · Sep 2026 · source · release history
  • Adds strix cloud subcommand for the managed platform CLI, covering login, scans, billing, and the full cloud API. v1.6.0 · Sep 2026 · source · release history
  • Strix now quits after a scan completes instead of hosting a local viewer — workflows that relied on the viewer launching automatically must now run strix view separately. v1.4.0 · Jul 2026 · source · release history
  • CLI now exits after a scan completes instead of launching a local viewer — use strix view to open results separately. v1.4.0 · Jul 2026 · source · release history
  • Adds a Feedback & support tab to the local viewer UI. v1.3.0 · Jul 2026 · source · release history
  • Adds a prominent scan switcher to the local viewer with renamed pentest terminology. v1.3.0 · Jul 2026 · source · release history

command line

  • workspace — Workspace number from `workspaces list`, ID, or exact name. v1.6.0 · Sep 2026 · command-line history

example

  • Log in to the managed cloud platform and kick off a cloud-managed scan from the CLI. strix cloud login && strix cloud scans start <target> v1.6.0 · Sep 2026 · source
  • Expose the scan results viewer on all interfaces at a fixed port when reviewing findings on a remote dev box over SSH. strix view my-run-name --host 0.0.0.0 --port 8080 --no-open v1.6.0 · Sep 2026 · source
  • After a scan finishes (Strix no longer auto-opens the viewer), inspect results in the local dashboard. strix view my-run-name v1.4.0 · Jul 2026 · source
  • Expose local results dashboard on network strix view --host 0.0.0.0 --port 8080 --no-open
SARIF output for code-scanning and ASPM integration verified Outputs findings as SARIF 2.1.0 with STRIDE categories mapped from CWEs, ready for GitHub code scanning and ASPM platform ingestion. 6 releases · 1 other source · first seen Jul 2026

release

  • Hardens CSV injection in report output. v1.6.0 · Sep 2026 · source · release history
  • Omit SARIF version-control provenance for multi-repo scans to reduce output noise (#726) v1.1.0 · Jul 2026 · source · release history
  • Emits SARIF 2.1.0 output for GitHub code-scanning and ASPM ingestion. v1.1.0 · Jul 2026 · source · release history
  • Tags SARIF rules with STRIDE categories derived from CWE mappings. v1.1.0 · Jul 2026 · source · release history
  • Adds SARIF 2.1.0 emitter for GitHub code-scanning and ASPM ingestion (#626) v1.1.0 · Jul 2026 · source · release history
  • Adds STRIDE tagging of SARIF rules derived from CWE to align findings with threat models (#708) v1.1.0 · Jul 2026 · source · release history

command line

Finding deduplication shipped Runs a deduplication model across scan results to reduce repeated findings when the same target is scanned multiple times. 4 releases · first seen Jan 2026

release

  • Adds update_vulnerability_report agent API so an agent can revise a previously filed finding. v1.6.0 · Sep 2026 · source · release history
  • Adds update_vulnerability_report agent API so an agent can revise an already-filed finding during a run. v1.6.0 · Sep 2026 · source · release history
  • Adds a dedicated deduplication model to reduce duplicate findings across scan runs. v1.4.0 · Jul 2026 · source · release history
  • LLM-based vulnerability deduplication detects semantically similar findings and merges them into a single canonical entry. v0.6.0 · Jan 2026 · source · release history
Programmatic report access shipped Provides read-only programmatic tools for listing and retrieving scan reports so results can be consumed by scripts or external systems. 3 releases · first seen Jul 2026

release

  • get_report tool for retrieving report data by ID v1.4.0 · Jul 2026 · source · release history
  • Adds list_reports and get_report read-only tools for programmatic report access. v1.4.0 · Jul 2026 · source · release history
  • list_reports tool for read-only listing of existing reports v1.4.0 · Jul 2026 · source · release history
User Interface and Experience 2 capabilities Strix ships both a terminal UI and a local web viewer so users can monitor and review scans in whichever environment suits them. The terminal interface is optimised for responsiveness even during long, output-heavy scans.
Interactive terminal UI (TUI) shipped Offers an interactive terminal UI with smooth scrolling, throttled refresh, overflow hints, and a dedicated renderer for SCA findings. 13 releases · first seen Feb 2026

Shared capability: Dependency scanning

release 13 total

  • Animates the wait_for_agents indicator in the TUI. v1.7.0 · Oct 2026 · source · release history
  • Lets the verified user define and change scope interactively in chat. v1.7.0 · Oct 2026 · source · release history
  • Adds interactive run picker when --resume is supplied with no run name, letting operators choose from prior runs in the terminal. v1.7.0 · Oct 2026 · source · release history
  • Improves startup performance by moving heavy imports off the startup path and pre-warming them in the background. v1.6.0 · Sep 2026 · source · release history
  • Moves heavy imports off the startup path and pre-warms them in the background, reducing CLI startup time. v1.6.0 · Sep 2026 · source · release history
  • Replaces the Textual TUI with a Go/Bubble Tea interface for improved terminal UI performance. v1.5.0 · Aug 2026 · source · release history
CLI self-update verified Updates the Strix binary in place with a single command and prints the correct upgrade instruction for package-manager installations. 2 releases · 3 other sources · first seen Jul 2026

Also counts toward: Command-line interface

release

  • Adds strix --update command for in-place CLI self-update and automatic update notifications. v1.4.0 · Jul 2026 · source · release history
  • strix --update flag for self-updating from CLI v1.4.0 · Jul 2026 · source · release history

command line

  • --update — Update strix to the latest version and exit. Self-updates the standalone binary install; for pip/pipx/uv installs, prints the matching upgrade command instead. v1.4.0 · Jul 2026 · command-line history

example

  • Keep Strix up to date without reinstalling — run this after any release to pull the latest version in place. strix --update v1.4.0 · Jul 2026 · source
  • Update your Strix installation directly from the command line without downloading binaries. strix --update v1.4.0 · Jul 2026 · source
Deployment and Security Hardening 2 capabilities Strix is distributed as standalone builds for multiple architectures and stores credentials with restrictive file permissions to reduce local exposure. These features cover the operational basics needed to run the cyber tool safely across different environments.
Credential storage hardening shipped Creates files that hold locally stored credentials with owner-only permissions to prevent other users on the same system from reading them. 2 releases · first seen Aug 2026

release

  • Creates credential files with owner-only permissions. v1.5.0 · Aug 2026 · source · release history
  • Credential files are now created with owner-only permissions, hardening local secret storage. v1.5.0 · Aug 2026 · source · release history
Linux ARM64 support shipped Ships standalone release builds for Linux ARM64 so the tool can run on ARM-based servers and devices without recompilation. 2 releases · first seen Jul 2026

release

Other 4 capabilities
CI/CD severity gating shipped Fails headless CI jobs automatically when findings meet or exceed a configurable severity threshold, allowing pipelines to enforce a minimum security bar. 4 releases · 4 other sources · first seen Nov 2025

Also counts toward: CI/CD pipeline integration, Command-line interface

release

  • Adds --fail-on flag to the CLI to gate headless exit code on finding severity, enabling CI pipelines to fail on configurable severity thresholds.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v1.7.0 · Oct 2026 · source · release history
  • Adds --fail-on <SEVERITY> flag to gate headless exit codes on finding severity. v1.7.0 · Oct 2026 · source · release history
  • --scan-mode CLI flag with quick, standard, and deep options for controlling scan depth v0.5.0 · Dec 2025 · source · release history
  • Adds --non-interactive flag to run Strix in headless mode for automation and CI/CD integration v0.3.1 · Nov 2025 · source · release history

example

  • Fail a CI job automatically when Strix finds any high- or critical-severity vulnerability during a headless scan. strix --target ./app-directory --fail-on high v1.7.0 · Oct 2026 · source
  • Run a fast scan focused on recent changes for CI/CD pipelines strix --scan-mode quick v0.5.0 · Dec 2025 · source
  • Run Strix in CI/CD without an interactive REPL and fail the pipeline if vulnerabilities are detected. strix --non-interactive --target https://example.com v0.3.1 · Nov 2025 · source
  • Headless non-interactive scan strix -n --target https://your-app.com
File-based pentest configuration shipped Accepts external YAML files for pentest instructions instead of requiring long CLI strings. 1 release · 3 other sources · first seen Nov 2025

release

  • Adds --instruction flag to accept file-based pentest configs instead of CLI strings v0.4.0 · Nov 2025 · source · release history

example

  • Inject a custom config or seed file into the sandbox so the agent can use it during a scan. strix scan --workspace-file ./seeds/auth_tokens.json <target> v1.6.0 · Sep 2026 · source
  • Inject a custom config or seed file into the sandbox so agents can reference it during a pentest without baking it into the target directory. strix --target ./my-app --workspace-file ./fixtures/test-users.json v1.6.0 · Sep 2026 · source
  • Run a pentest using instructions defined in an external YAML file rather than a long CLI string. strix scan --instruction ./pentest_instructions.yaml v0.4.0 · Nov 2025 · source
Standalone binary installation shipped Provides a method to install the cyber tool as a standalone binary without external dependencies. 1 release · 1 other source · first seen Dec 2025

release

  • Standalone binary installation via the curl -sSL https://strix.ai/install | bash one-liner v0.5.0 · Dec 2025 · source · release history

example

  • Install Strix as a standalone binary without Python dependencies curl -sSL https://strix.ai/install | bash v0.5.0 · Dec 2025 · source
Agent session persistence shipped Allows long-running agent sessions to be saved and resumed later. 1 release · first seen May 2026

release

  • Enables save and resume workflow for long-running agent sessions v1.0.0 · May 2026 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. 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 →

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…

Explore the full chart →

Releases

Show

20 entries

  1. October 20261
  2. September 20263
  3. August 20262
  4. July 20264
  5. June 20261
  6. May 20261
  7. March 20261
  8. February 20262
  9. January 20262
  10. December 20251
  11. November 20252
    Show

    20 entries

    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.

    1. Contributors 73 +69 vs prior 12 months
    2. Maintainers 2 +1 joined · −1 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 96% of issues opened, last 12 months
    5. Median time to close 7.3 days first maintainer reply 45 hours
    6. Open backlog 165 of 364 issues ever filed
    1. Issues opened / month 24 · 0 communitymaintainers
    2. Open backlog 165
    3. Contributors / month 5
    4. Commits / month 50
    5. Stars 62,859
    Issue themes, last 12 months
    • 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.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →