Skip to main content

AgenticVulHunter

AgenticVulHunter is a four-stage secure code review tool. It reviews your current Git changes and reports security issues that pass the validation threshold.

Step 1: Install

Install AgenticVulHunter using:

pipx install agenticvulhunter

Step 2: LLM Setup

You only need:

  • Endpoint
  • API key
  • Model

You can configure them using avh_setup.toml or environment variables.

Option 1: avh_setup.toml

Create avh_setup.toml inside the repository you want to review:

[llm]

endpoint = "http://localhost:11434/v1"
api_key = ""
model = "qwen3-coder:30b"

Option 2: Environment Variables

export AVH_ENDPOINT="http://localhost:11434/v1"
export AVH_API_KEY="your-key"
export AVH_MODEL="qwen3-coder:30b"

Environment variables take priority over avh_setup.toml.

Step 3: Run

Run AgenticVulHunter inside your Git repository:

agenticvulhunter review

The terminal shows live progress for all four review stages. BM25 retrieval runs internally against the packaged static rule corpus, but is kept out of the user interface to avoid mixing internal ranking signals with validated findings.

The visible workflow follows the research pipeline:

  1. Select potentially vulnerable changed lines.
  2. Build repository knowledge around each line.
  3. Search for matching CWE knowledge.
  4. Validate the evidence and apply the requested threshold.

Every accepted finding also includes a repository-verified attack path. Source, propagation, control, and sink citations are checked against the referenced code before the finding is shown. If a citation or path link is inconsistent, the validator automatically sends a focused follow-up prompt; incomplete paths are kept in the run artifacts but are not promoted to findings.

The initial result shows the review and a small suggested code fix. In an interactive terminal, enter a finding number to reveal only its plain-language attack path, or press Enter to finish. Suggested fixes are never applied automatically.

To reopen the most recent result later, run:

agenticvulhunter findings

To browse all previous reviews and their final threshold-filtered findings in the terminal, run:

agenticvulhunter runs

Choose a run by number to see its final result. Enter another run number to switch runs, or use f# to open a finding's attack path. Source locations are clickable in terminals that support hyperlinks; d, a, and l open the reviewed diff, annotated diff, and run log.

The default validation threshold is 0.6.

To use another threshold:

agenticvulhunter review 0.7

Metadata

Release files for agenticvulhunter 1.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for agenticvulhunter 1.1.3
File Size Uploaded Provenance Actions
agenticvulhunter-1.1.3.tar.gz 77.1 kB Without provenance Details for agenticvulhunter-1.1.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for agenticvulhunter 1.1.3
File Interpreter ABI Platform Actions
agenticvulhunter-1.1.3-py3-none-any.whl Python 3 none any Details for agenticvulhunter-1.1.3-py3-none-any.whl

Total release size: 172.1 kB

Release files / agenticvulhunter-1.1.3.tar.gz

Download URL agenticvulhunter-1.1.3.tar.gz
Size 77.1 kB
Tags Source
SHA-256 checksum
How to use checksums
18ac5340dbd529cebf37edeb9cc56feaa315e84ef5c48ea3deba930d7b225346
BLAKE2b-256 checksum
How to use checksums
007faf9539c2469dbf43fb86eed187a50bd8dc1b164e57c9588d5a2c2f331a92
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.7

Release files / agenticvulhunter-1.1.3-py3-none-any.whl

Download URL agenticvulhunter-1.1.3-py3-none-any.whl
Size 95.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
bf099652ae7771cb753bab16638b785f6034af3355db265060551582264cba13
BLAKE2b-256 checksum
How to use checksums
42d1986d6eb2c36b3a99f385772173faa9b61ae18344cb986fd23ec4b49a289a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.7

Security for agenticvulhunter 1.1.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page