shannon

KeygraphHQ/shannon

Shannon is an AI pentester for web applications and APIs. It analyzes your source code, identifies attack vectors, and executes real exploits to prove vulnerabilities before they reach production.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
20 Nov 2026
today
Ship score
92/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 48,598 → 51,993 (6 Oct – 17 Nov 2026)
+2,875 stars in the 28 days to 17 Nov 2026

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repository facts

Stars
52.1K
Forks
6.1K
Open issues
23
Watchers
234
Primary language
TypeScript
Created
27 Sep 2025
Owner
KeygraphHQ · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 308 startups in the directory ship primarily in TypeScript.

Topics

#ai-penetration-testing#ai-security#api-security#appsec#ci-cd#cybersecurity#devsecops#ethical-hacking#offensive-security#owasp#penetration-testing#pentesting#pentesting-tools#red-teaming#sarif#security#security-audit#security-automation#security-testing#security-tools

How Jev classified this project

Classified as an open-source startup by Jev, TypeSafe’s classifier, on 22 Sep 2026 — os_startup 96%, self-hostable 44%, hosted offering 54%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Joined the directory 22 Sep 2026, found by the weekly discovery job at confidence 0.95. Answered by jev-1.13.0. How the classification works →

Add the status badge to your README

OSSEAN ship status: shipping — last push 20 Nov 2026This is the badge for KeygraphHQ/shannon, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/KeygraphHQ/shannon.svg)](https://ossean.com/KeygraphHQ/shannon)

Updates daily, from the last push GitHub saw.

The badge links to this profile, even after a GitHub rename. GitHub caches README images, so the badge can take a little longer to update there.