bug-hunter

Adversarial AI bug hunter with auto-fix skill for Claude Code, Cursor, Codex CLI, GitHub Copilot CLI, Kiro CLI, Opencode, Pi Coding Agent, and more. Multi-agent pipeline finds security vulnerabilities, logic errors, and runtime bugs, then fixes them autonomously on a safe branch.

Not yet testedsource: GitHubJavaScriptMITcommit 3be69733a27a

JavaScript, MIT licensed. The project labels itself: adversarial ai, ai code review, auto fix, bug detection, claude, claude code, code quality and codex cli.

bug-hunter has not been verified yet.

Measured by Argusic on a fresh machine every time. Every number links to its evidence.

At a glance

verdict
Not yet tested
Argusic Score
not scored yet
recorded runs
0
last tested
-
stars
519
forks
62
open issues
0
watchers
8
size
57 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

  • agents verified to run · Python · 7 shared topics
  • agnix verified to run · Rust · 7 shared topics
  • cc-safety-net verified to run · TypeScript · 6 shared topics
  • no_human verified to run · Python · 6 shared topics
  • claude-tap verified to run · Python · 5 shared topics
  • pstack-claude verified to run · JavaScript · 5 shared topics

Run history

No recorded runs.

Topics (from GitHub)

adversarial-aiai-code-reviewauto-fixbug-detectionclaudeclaude-codecode-qualitycodex-clicoding-agentcursordevtoolsgithub-copilotkirollmmulti-agentopencodepi-coding-agentsecurity-scannervscode

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/bug-hunter.svg)](https://argusic.com/subject/bug-hunter)

Questions

Does bug-hunter run?
bug-hunter has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test bug-hunter?
On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
Where is the evidence for bug-hunter?
All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion