What it is
VulnHunter is an AI tool that finds and fixes security bugs in
computer code. It works in three simple steps:
- πFind. It reads the code like an attacker. It looks at
every place where data from outside can come in. It follows that data to see if it can reach
a dangerous action. Then it double-checks each result and removes the weak ones. What is left
is a short list of real bugs, each with a working example of the attack.
- π οΈFix. For each real bug, it writes a fix and a test that
proves the fix works. Then it makes a "pull request" β a proposed code change a human can review.
- β
Check. A separate part re-reads the fixed code and says,
for each bug, whether it is truly fixed. It trusts only the code, not what anyone says.
Why this matters: many tools list hundreds of "maybe" bugs and
waste people's time. VulnHunter is built to report only bugs it can prove β fewer results,
but real ones.
VulnHunter is a suite of three Claude Code skills plus two Python runtimes,
optimised for Claude Opus. Detection is attacker-first and forward: enumerate
user-controllable inputs, trace each to dangerous sinks, then run a falsification pass that
discards candidates resting on unsupported assumptions. Only findings backed by an executable
PoC survive. Remediation is test-driven; verification is a separate read-only agent.
β
VulnHunter does remediate. The suite has three parts: the
scanner (/vulnhunt) finds bugs and is read-only; the fixer
(/vulnhunter-fix) writes the actual code fix and opens a pull request; the
verifier (/vulnhunt-fix-verify) checks it. So "the scanner never edits your
code" and "VulnHunter fixes code" are both true β different parts do different jobs.
β οΈ Only the fixer changes code, and only on a git branch, gated by an operator. All parts send
code to a model provider; scan only repositories you're authorized to analyze.
π Words to know
Plain meanings for the words used on this page. Hover is not needed β the meaning
is written next to each word everywhere it appears.
InputAny data that comes from outside the program β a web form, a file, a URL, a message.
SinkA place in the code where data is used in a dangerous way β running a command, a database query, opening a file.
Vulnerability / bugA weakness an attacker can use to do something they should not.
Exploit / PoCA small working example that shows the bug is real. PoC = "proof of concept".
False positiveA warning that looks like a bug but is not real. VulnHunter is built to avoid these.
SkillOne tool inside VulnHunter that does one job. There are three: find, fix, check.
AgentAn AI worker that reads code and reasons. VulnHunter splits work across many agents.
Read-onlyCan look at the code but cannot change it.
Pull request (PR)A proposed code change on GitHub that a person reviews before it is accepted.
Claude Code / Claude OpusThe AI system VulnHunter runs on. You bring your own access to it.
Automation & scale
vulnhunter-agent β headless runtime
Runs a scan by itself β with no person watching β for example every night or after each code change. It saves a record of what happened and creates one GitHub ticket for each real bug it found. All the settings (which AI, which keys, which GitHub) come from one settings file, so the same setup works in any environment.
Clones the target, runs /vulnhunt via the Claude Agent SDK, writes a schema-validated scan_manifest.json, and optionally publishes results + files deduplicated issues. Auth is a single chokepoint: api_key (default), bedrock_oauth, or bedrock_sigv4. Use it as a base image you extend β wrap, don't fork; build against the manifest.
harness β batch & benchmark (dev-only)
A practice area for the scanner. One mode runs it over a whole list of code projects at once. The other mode runs it on projects where the real bugs are already known, then counts how many the scanner caught β so the team can measure how well it works.
Batch scanning from REPO_LIST.txt (resumable) and an accuracy benchmark (clone β scan β LLM-judge β tally) against ground_truth/<repo>.json.
Technology stack
Runtime hostClaude Code CLI on Claude Opus (you supply model access).
SkillsPrompt-only Markdown (SKILL.md + phase files). Installed via install.sh.
LanguagesPython 3.12+ for the runtime agent & harness; jsonschema, Claude Agent SDK.
Code intelligenceGraphify AST extraction (dist graphifyy) with a grep fallback.
Model accessAnthropic API (default) or Amazon Bedrock (OAuth proxy / SigV4).
ExternalGitHub (issues Β· PRs Β· forks) via gh / tokens.
ContractsJSON-Schema-validated manifest & verdict + finding/fix/result schemas.
LicenseApache-2.0. Source: github.com/capitalone/VulnHunter.