Quarry VRC
v1.5.0 open-sourceThe section your link pointed to isn't on Quarry VRC's page any more, so we've brought you to the top.
Designed for managing vulnerability discovery at scale with agentic AI and integrates with HackerOne.
QUARRY_POLL_MINUTES=0 curl -s https://<quarry-host>/api/stats | jq '.leads_by_class' QUARRY_POLL_MINUTES=30 export BURP_URL=http://localhost:8080 export CAIDO_URL=http://localhost:9000 QUARRY_MIN_PASSWORD_LENGTH=20 docker compose up -d bash scripts/check-no-private-data.sh
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
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
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 → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
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…
Releases
4 entries
No entries match these filters.
- August 20264
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.
- Contributors 2 +2 vs prior 12 months
- Maintainers 1 +1 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed not measured of issues opened, last 12 months
- Median time to close not measured issues closed, last 12 months
- Open backlog not measured open issues today
- Issues opened / month not measured
- Open backlog not measured
- Contributors / month 0
- Commits / month 0
- Stars 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.