PAGES
← all tools
◆ AI-Powered Offensive Security

shannon

v3.5.0 open-source

Shannon is an autonomous AI pentester for web applications and APIs that analyzes source code, identifies attack pathsattack pathsA possible sequence of steps an attacker could take to reach a valuable target. It connects weaknesses, permissions and reachable systems rather than treating each finding separately., and executes real exploits to prove vulnerabilities.

Summary

shannon is an open-source, autonomous AI pentester that analyzes a web application's source code, maps out attack paths, and then executes real exploits to prove the vulnerabilities it finds, rather than just flagging them. It runs as the full agent from your command line, configured through an interactive credential wizard before you point it at a source-available target. That places it with red teamers and application security engineers who want exploit-backed findings rather than another static scanner's list of maybes, and its own product line distinguishes this open-source edition from its hosted Whitebox and Blackbox Pentester offerings aimed at larger teams. Started in 2025, it has drawn 7 contributors and nearly 400 commits in the past year, with a release only 15 days old.

Shannon is an autonomous AI pentester for web applications and APIs that analyzes source code, identifies attack paths, and executes real exploits to prove vulnerabilities.

How shannon helps

Which vulnerabilities in this codebase can actually be exploited, not just theoretically flagged?

analyzes the source to map attack paths, then executes a real exploit against the running app to confirm each one before it is reported

What attack paths does this application actually expose, from entry point to impact?

traces the source code for reachable routes and chains them into concrete paths an attacker could follow, rather than listing isolated code smells

Which of these findings are safe to hand to a developer as proven, not maybe?

every reported finding is backed by an exploit that actually ran against the target, so the list is confirmed vulnerabilities rather than suspected ones

Did a misconfiguration stop this scan before it ever tested the target?

checks credentials and setup at startup and surfaces any preflight failure immediately, instead of letting the run fail silently partway through

Is this pentest working against the same set of AI models it started with?

pulls the current model catalogue over the network at the start of each scan, so the run reflects what is available now rather than what was current when the tool was installed

all 23 features, with the evidence for each →

Languages

Not documented

Features

23 capabilities

Built from shannon'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 →

What shannon offers you

  • Command-line interface5
  • CI/CD pipeline integration1
  • ML-based detection1
  • Scheduled jobs1
All capabilities 23 capabilities
Preflight validation and error reporting shipped Validates configuration and target state before scanning, providing structured errors for misconfiguration. 8 releases · 2 other sources · first seen Mar 2026

release 8 total

  • Introduces an exploit-readiness probe in the preflight phase to assess attack surface readiness v3.4.0 · Oct 2026 · source · release history
  • Adds --validate-auth mode to the preflight command to verify authentication configuration before a pentest run.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v3.4.0 · Oct 2026 · source · release history
  • Adds an exploit-readiness probe to the preflight subsystem to confirm the environment is ready to execute exploits. v3.4.0 · Oct 2026 · source · release history
  • Adds --validate-auth mode to the preflight command for deeper credential checks before running scans v3.4.0 · Oct 2026 · source · release history
  • Surfaces startup and preflight failures so misconfiguration errors are visible before a scan begins. v3.2.0 · Sep 2026 · source · release history
  • surface startup and preflight failures v3.2.0 · Sep 2026 · source · release history

example

  • Validate auth credentials and confirm exploit-readiness before committing to a full pentest run. npx @keygraph/shannon@latest preflight --validate-auth v3.4.0 · Oct 2026 · source
  • Run the preflight check on a folder that contains multiple repositories without Git metadata. shannon preflight /path/to/non-git-repo v1.8.0 · Jun 2026 · source
AI provider integration and model support shipped Supports multiple AI providers including Anthropic, OpenAI, Google Vertex AI, xAI, DeepSeek, and custom base URLs. 10 releases · first seen Mar 2026

release 10 total

  • Supports custom pi model configs with registry-resolvable model IDs and distinct model error codes. v3.2.0 · Sep 2026 · source · release history
  • Adds per-provider custom base URL configuration for the OpenAI Responses API, enabling use of self-hosted models, gateways (e.g. OpenRouter, LiteLLM), or any compatible endpoint. v3.1.0 · Sep 2026 · source · release history
  • Supports running pentests authenticated via an xAI (Grok) subscription, removing the need for pay-per-token API credits. v2.7.0 · Aug 2026 · source · release history
  • Supports any AI provider via the SHANNON_AI_API_KEY environment variable v2.3.0 · Aug 2026 · source · release history
  • Adds multi-provider model support for running inference across different AI providers v2.1.0 · Jul 2026 · source · release history
  • Upgrades underlying AI models to use Opus 4.8 v1.6.0 · Jun 2026 · source · release history
Execution control and concurrency shipped Manages worker execution via configurable retry logic, concurrency limits, and shared authentication sessions. 4 releases · 1 other source · first seen Mar 2026

release

  • Runs PI agent sessions at a high thinking level to improve analysis quality v3.4.0 · Oct 2026 · source · release history
  • Authenticated preflight sessions are shared across multiple agents v1.4.0 · May 2026 · source · release history
  • use structured outputs for vuln agent exploitation queues v1.1.0 · Apr 2026 · source · release history
  • Adds configurable pipeline retry and concurrency settings to control worker execution v1.0.0 · Mar 2026 · source · release history

docs

  • A full test run typically takes a few hours. LLM API costs vary by model pricing, target complexity, selected provider, and concurrency. Enabling security code analysis adds model time and cost. seen Oct 2026 · source
Dynamic model catalog management shipped Refreshes available AI models over the network at startup and supports custom model configurations. 4 releases · 1 other source · first seen Jun 2026

release

  • Refreshes the model catalogue over the network at scan start, ensuring newly available AI models are accessible without updating the tool.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v3.3.0 · Sep 2026 · source · release history
  • support custom pi model configs, with registry-resolvable model IDs and distinct model error codes v3.2.0 · Sep 2026 · source · release history
  • Supports setting a base_url for the OpenAI provider via .shannon/config.yaml to route requests to alternative inference endpoints v3.1.0 · Sep 2026 · source · release history
  • Adds Claude Fable 5 support by upgrading the underlying Claude Agent SDK to version 0.3.173 v1.7.0 · Jun 2026 · source · release history

docs

  • Shannon refreshes the model catalogue over the network at scan start, so a newly released model on a catalogue provider resolves without upgrading Shannon. The refresh is bounded and falls back to the built-in catalogue if it times out. , with an optional base URL to route that provider through a proxy or LLM gateway. docs update · Oct 2026 · source
Credential management and authentication shipped Supports various credential types including email login and interactive configuration wizards. 2 releases · 3 other sources · first seen May 2026

release

  • Bumps underlying pi harness to v0.84.2, enabling the new subscription auth flow. v2.7.0 · Aug 2026 · source · release history
  • Adds email_login as a supported credential type for authenticating with remote targets v1.3.0 · May 2026 · source · release history

docs

  • Schedule a technical demo See the pentest it feeds Every secret type, every commit Third-party Config Secrets set via ENV in Dockerfiles, docker-compose files, and config files in the repository. The secrets regex-only tools miss aren't hiding. They're obfuscated. seen Sep 2026 · source

example

  • Run shannon with a custom API key from any supported provider. SHANNON_AI_API_KEY=your_api_key shannon scan v2.3.0 · Aug 2026 · source
  • Configure credentials with interactive wizard npx @keygraph/shannon@latest setup
Output and deliverable handling shipped Configures output directories for scan results, reports, and intermediate deliverables. 3 releases · 2 other sources · first seen Mar 2026

Also counts toward: Command-line interface

release

  • Adds --output-format sarif flag to export results in SARIF format v2.1.0 · Jul 2026 · source · release history
  • Restructures the run folder layout and improves terminal UX v1.9.0 · Jul 2026 · source · release history
  • Adds --output flag to specify a configurable output directory for scan results and deliverables v1.0.0 · Mar 2026 · source · release history

docs

  • Shannon is an open-source pentester. It reads your source, maps routes and data flows, runs real attacks against a live target, and writes PDF and SARIF reports. It runs locally, in CI, or air-gapped with your own model. Shannon Open Source is a complete pentester, not a trial edition. seen Oct 2026 · source

example

  • Save scan results directly to a specific directory instead of the default location shannon scan target --output ./results/v1 v1.0.0 · Mar 2026 · source
Interactive launcher and CLI shipped Provides an interactive launcher that guides first-time setup and exposes CLI commands for tailing agent logs and listing available agents within a workspace. 1 release · 3 other sources · first seen Aug 2026

Also counts toward: Command-line interface

release

docs

  • The interactive launcher walks you through setup and your first pentest. This repository is Shannon: the full open-source agent, run locally from your command line. Shannon is the agent. This repository is Shannon, the open-source pentester you run yourself. seen Oct 2026 · source
  • so npx runs the current release, not a cached older CLI. Run it with no command to open the interactive launcher, which prompts you to run the first time. logs [<workspace>] --agent <name> Tail one agent’s own log. Add --list-agents instead to list the available names. docs update · Oct 2026 · source
  • : what Shannon is, why it exists, and how a scan works, stage by stage. : license, office hours, Discord, acknowledgements, and where to report issues. FAQ : self-hosting, BYOK, SARIF, providers, local models, scan duration, and resuming. seen Oct 2026 · source
Worker networking and environment isolation shipped Forwards host DNS entries to workers and mounts user repositories in isolated environments. 2 releases · 2 other sources · first seen Apr 2026

release

  • docker mode now forwards the host's /etc/hosts entries into each worker container v1.4.0 · May 2026 · source · release history
  • mount user repo as read-only with writable shannon overlay v1.1.0 · Apr 2026 · source · release history

docs

  • Node.js 20.19+ (the source build’s toolchain needs it; the workflow runs on Node.js 18+) seen Oct 2026 · source
  • Node.js : 18+ for the workflow, or 20.19+ for a build from source. The quickest start is the interactive launcher, which walks you through setup and your first pentest: Or run each step yourself: flag is the path to the target’s source repository (mounted read-only inside the worker). docs update · Oct 2026 · source
PDF report navigation shipped Links finding IDs in the PDF report to their corresponding detail sections for faster navigation. 3 releases · first seen Aug 2026

release

  • Links finding IDs in generated PDF reports directly to their detail sections for easier navigation v3.4.0 · Oct 2026 · source · release history
  • Links finding IDs in the PDF report to their corresponding detail sections for faster navigation. v3.4.0 · Oct 2026 · source · release history
  • Adds PDF security report rendering powered by Typst. v2.5.0 · Aug 2026 · source · release history
Expanded vulnerability analysis scope shipped Analyzes injection vectors including LFI, RFI, SSTI, Path Traversal, and Deserialization. 1 release · 2 other sources · first seen Mar 2026

release

  • Expands injection analysis scope to include LFI, RFI, SSTI, Path Traversal, and Deserialization v1.0.0 · Mar 2026 · source · release history

docs

  • # Security code analysis (opt-in). enabled is its only setting. Security code analysis is opt-in, through the block: is the only setting. Omitting the block, or setting enabled: false , turns it off. Either way, all five vulnerability classes still run. docs update · Oct 2026 · source
  • Overview Shannon is Keygraph’s open-source AI pentester for web applications and APIs (AGPL-3.0). It reads your source code, runs real exploits against the running app, and reports only the findings it can prove. docs update · Oct 2026 · source
Workspace management shipped Manages named workspaces for resuming workflows and organizing scan data. 2 releases · 1 other source · first seen Mar 2026

Also counts toward: Command-line interface

release

  • Adds named workspaces and workspace listing capability v1.0.0 · Mar 2026 · source · release history
  • Adds --workspace flag to resume workflows from a named workspace or list available workspaces v1.0.0 · Mar 2026 · source · release history

docs

  • so npx runs the current release, not a cached older CLI. Run it with no command to open the interactive launcher, which prompts you to run the first time. logs [<workspace>] --agent <name> Tail one agent’s own log. Add --list-agents instead to list the available names. docs update · Oct 2026 · source
PHP-to-shell exploit path verification shipped Provides an experimental probe that tests PHP-to-shell upgrade attack paths against a target to validate shell-upload exploits before production. 1 release · 1 other source · first seen Oct 2026

Also counts toward: Command-line interface

release

  • Adds experimental --exp-php2shell upgrade-verification probe flag to the CLI for testing PHP-to-shell attack paths.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v3.5.0 · Oct 2026 · source · release history

example

  • Run the experimental PHP-to-shell upgrade-verification probe against a target during a pentest to validate shell-upload exploit paths before they reach production. npx @keygraph/shannon@latest --exp-php2shell v3.5.0 · Oct 2026 · source
Automated model catalogue updates shipped Automatically fetches updated model catalog entries from the network at scan start. 1 release · first seen Sep 2026

release

  • shannon now automatically fetches updated model catalogue entries from the network when a scan begins, removing the need to manually update local models before scanning. v3.3.0 · Sep 2026 · source · release history
Agentic SAST shipped Performs static application security testing using agentic AI capabilities. 1 release · first seen Sep 2026

release

Live scan status shipped Displays live status updates during active scans via the CLI. 1 release · first seen Aug 2026

Also counts toward: Command-line interface

release

  • Overhuals CLI commands and adds live scan status display during active scans. v2.5.0 · Aug 2026 · source · release history
Severity classification shipped Assigns severity levels to findings during the analysis phase. 1 release · first seen Aug 2026

release

SARIF export shipped Exports scan results in SARIF format for interoperability with other tools. 1 release · first seen Jul 2026

release

  • Adds --output-format sarif flag to export results in SARIF format v2.1.0 · Jul 2026 · source · release history
SIEM integration shipped Exports scan results specifically for integration with SIEM or vulnerability management platforms. 1 other source · first seen Jul 2026

example

  • Export scan results for integration with SIEM or vulnerability management platforms shannon scan --provider openai --model gpt-4 --output-format sarif report.json v2.1.0 · Jul 2026 · source
Data processing and MCP integration shipped Structures intermediate deliverables using MCP collectors within the worker environment. 1 release · first seen Jun 2026

release

  • Adds worker support for MCP collectors to structure intermediate deliverables v1.5.0 · Jun 2026 · source · release history
Security policy enforcement shipped Enforces operational security policies such as blocking execution when run with root privileges. 1 release · first seen May 2026

release

  • Running shannon with sudo or as root now blocks execution. v1.2.0 · May 2026 · source · release history
CI/CD pipeline integration documented Runs pentests as part of GitHub Actions or GitLab CI pipelines, supporting pull-request, release, and scheduled triggers with the ability to gate on exploited findings. 1 other source

Also counts toward: CI/CD pipeline integration, Scheduled jobs

docs

  • CI/CD integrations : run pull-request, release, and scheduled pentests with the GitHub Action or GitLab component, and gate on exploited findings. seen Oct 2026 · source
Code Property Graph analysis documented Uses Code Property Graph data-flow analysis with LLM evaluation of context to identify vulnerabilities. 1 other source

Also counts toward: ML-based detection

docs

  • Code Property Graph data-flow analysis, with an LLM evaluating context at every node and an agent validating every candidate path. Schedule a technical demo See the pentest it feeds Taint-style data flow and single-line point issues SQL injection User input reaches a query parameter via unescaped concatenation. seen Sep 2026 · source
Exploit-proven findings documented Every reported finding includes a working exploit that demonstrates the vulnerability. 1 other source

docs

  • No exploit, no report: every pentest finding ships with the working exploit that proves it. Keygraph Pro for startups and nonprofits, at no cost. Everything in Pro, every module included For U.S. 501(c)(3) nonprofits and pre-Series-A startups Up to 20 Active Developers Month to month while you qualify seen Oct 2026 · source

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 shannon, 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 shannon 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 →

Website history

keygraph.io, every change

Keygraph's 33 pages as they looked each month from October 2026 to October 2026: 33 renders, 0 changes of tagline or palette. Step through them, play them, or put any two months side by side.

Website history is included with Researcher and Business.

See plans →

Releases

Show

33 entries

  1. October 20267
  2. September 202610
  3. August 20265
  4. July 20262
  5. June 20264
  6. May 20263
  7. April 20261
  8. March 20261
    Show

    33 entries

    Project health

    Issue, contributor and maintainer activity in KeygraphHQ/shannon, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 7 +7 vs prior 12 months
    2. Maintainers 3 +3 joined · −0 left, last 12 months
    3. Bus factor 2 committers behind half the commits
    4. Community-filed 99% of issues opened, last 12 months
    5. Median time to close 3.7 days first maintainer reply 13 hours
    6. Open backlog 5 of 147 issues ever filed
    1. Issues opened / month 6 · 0 communitymaintainers
    2. Open backlog 5
    3. Contributors / month 2
    4. Commits / month 9
    5. Stars 48,124
    Issue themes, last 12 months
    • other 100%

    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

    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 →