PAGES
← all tools
◆ Vulnerability Management

Quarry VRC

v1.5.0 open-source

Designed for managing vulnerability discovery at scale with agentic AI and integrates with HackerOne.

Summary

Quarry VRC is an open-source bug bounty hunting console that syncs HackerOne reports, tracks leads, manages payloads, and supports evidence capture workflows. It is free to use and runs as a service, requiring configuration for authentication via APIs. It is aimed at penetration testers who participate in bug bounty programs, and its documentation positions it alongside other tools managing findings from bug bounty platforms. The project has seen six releases in the tracked period, with the most recent update nineteen days ago.

Designed for managing vulnerability discovery at scale with agentic AI and integrates with HackerOne.

How Quarry VRC helps

Which of my HackerOne reports have moved state or bounty since I last checked?

the incremental poller detail-fetches only reports whose list-endpoint change signals moved, logging state and bounty transitions as events that update Tracker badges and bounty alerts between full syncs

Which of my shipped fixes are worth a second look?

the Regression tab queues every resolved report for retest, keeping what the original finding was so a hunter can re-run the same proof of concept against the new patch

Which programs can I even hunt on right now, and what's their scope?

the add-program picker searches every program a given credential can see, including private and invited ones, and pulls in policy and scope immediately on add

Are any of my findings connected to a disclosed CVE or vendor advisory?

configurable RSS/Atom advisory feeds are parsed into vendor, product, and type columns and cross-referenced against the reports already tracked

Did I just commit something from my own environment into a shared repository?

a pre-push script and CI workflow scan every commit for home paths, LAN IPs, real report IDs, private handles, and credentials, and refuse the ones that match

all 17 features, with the evidence for each →

Languages

Not documented

Features

17 capabilities · 3 backed by code, an API document or a real run

Built from Quarry VRC's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • Quarry VRC covers 1 of the 8 vulnerability assessment methods capabilities we track.

What Quarry VRC offers you

  • Command-line interface2
  • REST API2
  • CI/CD pipeline integration1
  • GraphQL API support1
  • Scheduled jobs1
All capabilities 17 capabilities
HackerOne program and scope sync shipped Syncs programs, scopes, visibility, policy, reports, states, bounties, payout splits, and triage threads from the HackerOne API, including private and invited programs discovered via a credential-aware picker. 6 releases · 3 other sources · first seen Aug 2026

release

  • Tracks programs with a Visibility column showing public / private / clear sourced from HackerOne, plus a screenshot-conceal toggle that blurs private program identities in demo screenshots. v1.3.3 · Aug 2026 · source · release history
  • Enables search-based onboarding of any program visible to credentials (including private/invited ones) via the new Add-program picker. v1.3.3 · Aug 2026 · source · release history
  • Shows Visibility column for public/private/clear status and a screenshot-conceal toggle in the Program scope management UI. v1.3.3 · Aug 2026 · source · release history
  • Adds an add-program picker that searches every program a credential can see on HackerOne — including private and invited programs — and onboards one with its policy and scopes immediately populated. v1.3.3 · Aug 2026 · source · release history
  • Syncs programs, scopes, reports, states, bounties, payout splits and triage threads from HackerOne via the HackerOne integration feature. v1.3.3 · Aug 2026 · source · release history
  • Syncs HackerOne programs, scopes, reports, states, bounties, payout splits, and triage threads from the HackerOne API, and enables filing a finished report to a program without copy-pasting into the web form. v1.3.3 · Aug 2026 · source · release history

example

  • Onboard a private program and sync its scope automatically # Use the Add-program picker UI to search for the private program, onboard it, and let Quarry VRC populate policy and scopes. # (No specific CLI/flag named for this yet; relies on UI navigation) v1.3.3 · Aug 2026 · source
  • Sync reports, bounties, and triage from HackerOne python3 core/h1.py --sync
  • Sync program guidelines, scopes, and visibility python3 core/h1.py --sync-programs
Incremental HackerOne report polling verified Polls HackerOne incrementally for report changes, recording state and bounty transitions as events to keep tracker badges, the report-update feed, and bounty alerts current between full syncs; interval is configurable or driveable by an external scheduler. 3 releases · 4 other sources · first seen Aug 2026

Also counts toward: Scheduled jobs

release

  • Adds QUARRY_POLL_MINUTES environment variable to tune the incremental HackerOne poller interval (default: 15 minutes); set to 0 to disable the built-in timer and drive polls from an external scheduler. v1.5.0 · Aug 2026 · source · release history
  • Adds the incremental poller core/h1_watch.py that detail-fetches only reports whose HackerOne list-endpoint change signals moved, recording state and bounty transitions as events to keep Tracker badges, the report-update feed, and bounty alerts current between full syncs. v1.5.0 · Aug 2026 · source · release history
  • Introduces the incremental HackerOne poller defined in core/h1_watch.py for live report-update monitoring between full syncs v1.5.0 · Aug 2026 · source · release history

command line

example

  • Disable the built-in poller timer and drive HackerOne report polling from your own external scheduler (e.g. a cron job). QUARRY_POLL_MINUTES=0 v1.5.0 · Aug 2026 · source
  • Reduce poll frequency to every 30 minutes to lower HackerOne API request volume in a low-traffic deployment. QUARRY_POLL_MINUTES=30 v1.5.0 · Aug 2026 · source
Report submission and collaboration via HackerOne shipped Files finished reports to a HackerOne program without copy-pasting into the web form, and manages invitations, collaborators, and bounty splits through a GraphQL client with a write-only masked session cookie. 4 releases · 1 other source · first seen Aug 2026

Also counts toward: GraphQL API support

release

  • The manual New report form is replaced with a How to submit link to the API-submit guide. v1.5.0 · Aug 2026 · source · release history
  • New Integrations-tab card and stdlib GraphQL client for HackerOne: list, accept, or reject program invitations; accept report-collaborator invitations; invite collaborators and set bounty splits; browser session cookie stored write-only and masked. v1.4.0 · Aug 2026 · source · release history
  • Adds GraphQL mutations and queries for HackerOne program invitations, report-collaborator management, and bounty splits via a new Integrations-tab card and stdlib GraphQL client v1.4.0 · Aug 2026 · source · release history
  • Allows filing a finished report to a program with one click through the new UI, eliminating copy-paste into the web form. v1.3.3 · Aug 2026 · source · release history

example

  • Submit a finished report to HackerOne python3 core/h1.py --submit reports/<slug>.md --program <handle> \
Retest and verdict workflow verified Supports recording verdicts against reports (holds, broken, skipped, pending), snoozing due dates, and retesting shipped fixes within a configurable retest window. 1 release · 4 other sources · first seen Aug 2026

Also counts toward: Command-line interface

release

  • Adds a working retest-window control to Settings, replacing the previously unavailable cadence card. v1.5.0 · Aug 2026 · source · release history

command line

example

  • Record a retest verdict for a shipped fix python3 core/regression.py --verdict <report-id> --set broken --note "the v2 route is unpatched"
Instance hardening and access controls shipped Secures the console with IP allow-listing, TLS on first boot, PBKDF2-HMAC authentication, write-only secrets, a strict CSP, and a configurable minimum password length. 3 releases · 2 other sources · first seen Aug 2026

release

  • Introduces QUARRY_MIN_PASSWORD_LENGTH environment variable (default 12) to configure minimum password length. v1.3.3 · Aug 2026 · source · release history
  • Adds QUARRY_MIN_PASSWORD_LENGTH environment variable (default 12) to enforce a configurable minimum password length for admin bootstrap and subsequent password changes. v1.3.3 · Aug 2026 · source · release history
  • Ships standard hardening: IP allow-list checked before auth, TLS on first boot, PBKDF2-HMAC auth, write-only secrets, and a strict default-src 'none' CSP. v1.3.3 · Aug 2026 · source · release history

example

  • Set a stronger minimum password length before bootstrapping the admin account in a production deployment. QUARRY_MIN_PASSWORD_LENGTH=20 docker compose up -d v1.3.3 · Aug 2026 · source
  • Set minimum password length for admin bootstrap via environment variable QUARRY_MIN_PASSWORD_LENGTH=16 docker compose up -d # Configurable password policy via QUARRY_MIN_PASSWORD_LENGTH (default 12) v1.3.3 · Aug 2026 · source
Dashboard and stats shipped Provides a dashboard with tiles for program hacktivity, a leads-by-class breakdown, and other summary metrics exposed via a stats API endpoint. 2 releases · 2 other sources · first seen Aug 2026

Also counts toward: REST API

release

  • Adds a leads_by_class breakdown to the /api/stats endpoint, powering a new Leads by class tile on the Dashboard. v1.5.0 · Aug 2026 · source · release history
  • Adds a new leads_by_class breakdown field to the GET /api/stats endpoint on the Dashboard v1.5.0 · Aug 2026 · source · release history

docs

  • Bug bounty hunting console that syncs HackerOne reports, tracks leads, manages payloads, and supports agentic AI workflows via Markdown and SQLite.

example

  • Check the current leads-by-class breakdown from the stats API to populate dashboards or feed downstream tooling. curl -s https://<quarry-host>/api/stats | jq '.leads_by_class' v1.5.0 · Aug 2026 · source
Report and lead tracker shipped Tracks every report and lead with state, bounty, CWE, impact, payout split, and a privacy badge, with a full lead lifecycle (open, confirmed, ready, submitted, awarded, parked, killed) and in-scope assets mapped to local workspaces. 4 releases · first seen Aug 2026

release

  • The anticipated (hand-recorded, unconfirmed-award) feature is removed from the Tracker, the report detail, and the Dashboard. v1.5.0 · Aug 2026 · source · release history
  • Tracker PRIV column now renders a compact one-letter badge (N, L, or H), with High displayed in red and the full word retained in the hover title. v1.4.0 · Aug 2026 · source · release history
  • Maps in-scope assets to local workspaces for filed leads. v1.3.3 · Aug 2026 · source · release history
  • Adds a Tracker showing every report with state, bounty, CWE, impact, and payout split; a lead workflow with states open, confirmed, ready, submitted, awarded, parked, and killed; and in-scope assets mapped to local workspaces. v1.3.3 · Aug 2026 · source · release history
UI search, sort, and view modes shipped Adds search toggles, sortable columns, card and list view with a persisted toggle, and a compact status-chip legend across Leads, Tracker, Programs, Targets, Payloads, Regression, and Files tabs. 4 releases · first seen Aug 2026

release

  • Adds a Search toggle and compact Sort control to Leads, Tracker, Programs, Targets, Payloads, and Regression, and applies the shared status-chip legend to Regression buckets. v1.5.0 · Aug 2026 · source · release history
  • Adds a name filter and sortable columns to the Files tab. v1.5.0 · Aug 2026 · source · release history
  • Updates the UI with card and list views for Leads, Tracker and Advisories, controlled by a persisted toggle v1.5.0 · Aug 2026 · source · release history
  • Adds a card and list view across Leads, Tracker, and Advisories with a persisted toggle, equal-height cards with bottom-flush metadata, and PRIV plus C/I/A impact badges consistent with table mode. v1.5.0 · Aug 2026 · source · release history
Private-data leak prevention shipped Ships a shell script and CI workflow that gate every commit, refusing home paths, LAN IPs, real report IDs, private handles, and credentials from reaching the repository. 3 releases · 1 other source · first seen Aug 2026

Also counts toward: CI/CD pipeline integration

release

  • path_denied in core/common.py now matches case-insensitively, preventing re-cased secrets from bypassing the deny-list v1.4.2 · Aug 2026 · source · release history
  • Adds leak scanner script scripts/check-no-private-data.sh run via .github/workflows/no-private-data.yml to prevent operator-private data from reaching the repo. v1.3.3 · Aug 2026 · source · release history
  • Adds scripts/check-no-private-data.sh and CI workflow .github/workflows/no-private-data.yml to gate every commit, refusing home paths, LAN IPs, real report IDs, private handles, and credentials from reaching the repository. v1.3.3 · Aug 2026 · source · release history

example

  • Run the leak scanner locally before pushing to ensure no operator-private data (home paths, LAN IPs, report IDs, credentials) is committed. bash scripts/check-no-private-data.sh v1.3.3 · Aug 2026 · source
Proxy integration for request capture and screenshots shipped Connects to Caido and Burp proxy instances via configurable environment variables to capture HTTP request/response pairs and full-screen OS screenshots as evidence. 3 releases · 1 other source · first seen Aug 2026

release

  • Screenshot and evidence-feed endpoints (/api/screenshot and /api/evidence/feed) read backend hosts from CAIDO_URL and BURP_URL environment variables instead of request bodies v1.4.2 · Aug 2026 · source · release history
  • Callers passing caido_url or burp_url in the screenshot or evidence-feed request body must now set CAIDO_URL and BURP_URL in the environment instead v1.4.2 · Aug 2026 · source · release history
  • Adds CAIDO_URL and BURP_URL environment variables to point capture backends at Caido and Burp proxy instances (use http://host.docker.internal:<port> inside a container) for request/response and full-screen OS screenshot capture. v1.4.0 · Aug 2026 · source · release history

example

  • Configure Quarry VRC to use a local Burp instance for screenshots via environment variables export BURP_URL=http://localhost:8080 export CAIDO_URL=http://localhost:9000 v1.4.2 · Aug 2026 · source
Evidence capture and report drafting shipped Records an evidence timeline, a scope-filtered proxy feed, and supports drafting reports with file attachments via server routes and a CLI flag. 3 releases · first seen Aug 2026

Also counts toward: Command-line interface

release

  • Adds --attach CLI flag and server routes to capture request/response renders from Caido and Burp, full-screen OS screenshots, evidence timeline, scope-filtered proxy feed, and draft reports with file attachments v1.4.0 · Aug 2026 · source · release history
  • New server routes and CLI for evidence capture: records an evidence timeline, a scope-filtered proxy feed, and supports drafting and attaching files to reports. v1.4.0 · Aug 2026 · source · release history
  • Adds --attach CLI flag to the report-intent flow for attaching files to drafted reports. v1.4.0 · Aug 2026 · source · release history
Vendor-neutral report and lead standards shipped Ships a standards folder defining vendor-neutral report shape and lead lifecycle that any hunter on the team can adopt for consistent reporting. 2 releases · 1 other source · first seen Aug 2026

release

  • New standards/ folder ships vendor-neutral report and lead standards any Quarry hunter can adopt for a consistent report shape and lead lifecycle. v1.4.0 · Aug 2026 · source · release history
  • Packages vendor-neutral report and lead standards in the standards/ folder for hunters to adopt consistent report shape and lead lifecycle v1.4.0 · Aug 2026 · source · release history

example

  • Adopt the vendor-neutral report and lead standards shipped with Quarry for consistent reporting across a team. In the Quarry VRC UI, go to the Integrations tab, then review and configure your HackerOne session cookie in the new HackerOne card; reference the standards in the `standards/` folder for report… v1.4.0 · Aug 2026 · source
Payload library shipped Ships a searchable payload library cloned from PayloadsAllTheThings, with one row per documented block, searchable from the UI and CLI. 2 releases · 1 other source · first seen Aug 2026

release

  • Provides a searchable clone of PayloadsAllTheThings with one row per documented block in the Payload library. v1.3.3 · Aug 2026 · source · release history
  • Includes a searchable payload library cloned from PayloadsAllTheThings, one row per documented block. v1.3.3 · Aug 2026 · source · release history

example

  • Search the payload library python3 core/payloads.py --search "jwt none"
REST API for external access shipped Exposes a Bearer-token authenticated API so external scripts and agents can query the console without a browser session. 2 releases · 1 other source · first seen Aug 2026

Shared capability: REST API

Also counts toward: REST API

release

  • Exposes a Bearer-token API for external scripts and agents to query the console without a browser session in the Agentic-AI-native feature. v1.3.3 · Aug 2026 · source · release history
  • Provides a Bearer-token API so external scripts and agents can query the console without a browser session. v1.3.3 · Aug 2026 · source · release history

example

  • Query the console programmatically using the new Bearer-token API curl -H 'Authorization: Bearer <YOUR_TOKEN>' http://localhost:8080/api/leads # The Bearer-token API allows external scripts and agents to query the console without a browser session. v1.3.3 · Aug 2026 · source
Report and lead index verified Maintains a searchable index of leads and reports built from Markdown and SQLite, rebuildable via CLI. 2 other sources · first seen Aug 2026

command line

example

  • Rebuild lead and report index from Markdown python3 core/ingest.py --rebuild
Advisory feed integration shipped Parses configurable RSS/Atom advisory feeds (CISA and VulDB by default, user-replaceable) into Vendor/Product/Type columns and cross-references them against your reports. 2 releases · first seen Aug 2026

Shared capability: Vulnerability database matching

release

  • Adds configurable RSS/Atom advisory feeds (CISA and VulDB by default, user-replaceable) parsed into Vendor / Product / Type columns and cross-referenced against your reports. v1.3.3 · Aug 2026 · source · release history
  • Parses configurable RSS/Atom feeds (CISA, VulDB default) into Vendor/Product/Type columns in the Advisory feeds feature. v1.3.3 · Aug 2026 · source · release history
Program hacktivity monitoring shipped Displays a dashboard tile watching the public hacktivity feed of an operator-selected HackerOne program. 2 releases · first seen Aug 2026

release

  • Adds a program hacktivity tile on the dashboard that watches whichever program's public activity feed the operator selects. v1.3.3 · Aug 2026 · source · release history
  • Watches a selected program's public activity feed via the Program hacktivity tile. v1.3.3 · Aug 2026 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for Quarry VRC, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail Quarry VRC puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

4 entries

  1. August 20264
    Show

    4 entries

    Project health

    Issue, contributor and maintainer activity in skraft9/quarry-vrc, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 2 +2 vs prior 12 months
    2. Maintainers 1 +1 joined · −0 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed not measured of issues opened, last 12 months
    5. Median time to close not measured issues closed, last 12 months
    6. Open backlog not measured open issues today
    1. Issues opened / month not measured
    2. Open backlog not measured
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars not measured
    Issue themes, last 12 months not measured

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →