Discofork
Repository brief

KeygraphHQ/shannon

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-31T09:43:55.463Z
1mo ago

KeygraphHQ/shannon

Shannon Lite is an actively maintained TypeScript/Node.js monorepo for an autonomous, white-box AI pentester for web apps and APIs. It is open source under AGPL-3.0, has very high adoption signals (34,958 stars, 3,530 forks), and the recent work suggests the project is moving toward an `npx`-installable CLI with CI/CD and ephemeral worker architecture. For fork interest, it looks most relevant to teams exploring autonomous AppSec tooling, CLI/workflow packaging, or security automation infrastructure.

GitHub
Loading tags...
Stars34,958
Forks3,530
Default branchmain
Last pushed2026-03-26T21:12:12Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork if you want a more experimental, black-box-first pentesting workflow and are comfortable with divergence from upstream. Stick with upstream if you need the mature white-box, Docker-centric, source-guided architecture and the latest maintained feature set.

Pick this fork if you want a Shannon variant that already carries proxy-oriented and benchmarking-oriented changes. Avoid it if you want the latest upstream CLI/distribution work or a low-maintenance base, because it is materially behind and heavily diverged.

Choose this fork if you want a benchmark-heavy, experimentally tuned Shannon variant with a few operator conveniences. Choose upstream instead if you want the newest packaging, deployment, and runtime work.

Choose this fork if you value benchmark artifacts and local operational tweaks over staying current with upstream. Choose upstream if you want the latest CLI, packaging, and release workflow improvements.

Prefer this fork if you want benchmark-heavy evaluation data, router/model experimentation, or a fork that is already shaped around CLI and worker workflows. Prefer upstream if you want the most current Shannon Lite codebase, broader provider support, and easier ongoing maintenance.

Choose this fork if you want Shannon as a benchmarked, router-aware experimentation platform. Choose upstream if you want the latest maintained product path, broader packaging/workflow updates, and less merge debt.

Choose this fork if you want a research-heavy Shannon variant with benchmark data and workflow experimentation. Choose upstream if you want the latest maintained product packaging, release flow, and compatibility improvements with less maintenance burden.

Prefer this fork only if you need the benchmark artifacts or router/provider experiments it adds. For most adopters who want the newest, most maintainable Shannon experience, upstream is the better starting point because this fork is far behind and heavily diverged.

Prefer this fork if your goal is model-eval, benchmarking, or router experimentation. Prefer upstream if you want the current Shannon product with newer CLI, packaging, and worker/deployment workflows.

Choose this fork if you want benchmark-heavy, multi-provider router experimentation around Shannon; choose upstream if you want the latest CLI, release, and worker architecture with less merge risk.

KeygraphHQ/shannon · Discofork