Integrate HackerOne with Vulnetix. Use the HackerOne API v1 to export vulnerability reports from your bug bounty programme and upload findings to Vulnetix.
Run HackerOne in CI
Scan on every push and upload the report as a workflow artifact:
- name: Export HackerOne reports
env:
H1_IDENTIFIER: ${{ secrets.H1_IDENTIFIER }}
H1_TOKEN: ${{ secrets.H1_TOKEN }}
H1_PROGRAM: ${{ secrets.H1_PROGRAM }}
run: |
curl -s "https://api.hackerone.com/v1/reports?filter[program][]=$H1_PROGRAM&filter[state][]=triaged&page[size]=100" -u "$H1_IDENTIFIER:$H1_TOKEN" | jq '.data' > h1-reports.json
- name: Upload to Vulnetix
run: vulnetix upload --file h1-reports.json
How Vulnetix compares: better together
Vulnetix does not replace HackerOne. Keep running it. Vulnetix sits on top of HackerOne (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
HackerOne is strongest at its core category and also carries features in Network & Vulnerability Scanners, just as Vulnetix spans categories.
| Capability | Vulnetix | HackerOne |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ✗ |
| SCA / dependencies | ✓ 40+ ecosystems, transitive graph | ✗ |
| DAST (dynamic testing) | ~ Ingests DAST results; no native dynamic engine | ✗ |
| Container & image | ✓ Image CVEs, base image, Dockerfile | ✗ |
| IaC / misconfiguration | ✓ Terraform, k8s, CloudFormation | ✗ |
| Secret scanning | ✓ 1,000+ rules, source + binary + git history | ✗ |
| Cloud / CSPM | ✓ Cloud-posture findings, compliance tab | ✗ |
| Mobile (MAST) | ~ Ingests mobile scanner output; no native mobile engine | ✗ |
| License compliance | ✓ SPDX, copyleft/AGPL/SSPL policy | ✗ |
| SBOM generation | ✓ CycloneDX 1.7 + SPDX 2.3, cosign-signable | ✗ |
| Malware / supply-chain | ✓ De-duplicated corpus + install-time firewall (25+ registries) | ✗ |
| Network / infra vuln | ~ Ingests network scanner output; no native network scanner | ~ Attack Surface Management / CTEM continuously discovers external assets; not an infra vuln scanner engine |
| Fuzzing | ✗ Ingests fuzzing crashes; no native fuzzer | ✗ |
| Pentest / bug bounty | ✗ Ingests pentest/bug-bounty findings; not a testing service | ✓ Core: bug bounty, VDP, and Pentest-as-a-Service via crowd of researchers |
| The Vulnetix orchestration layer | ||
| Cross-scanner dedup & one queue (ASPM) | ✓ Correlates every scanner into one prioritised queue with ownership routing | ~ Hai Triage de-dupes researcher submissions; not cross-scanner ASPM dedup |
| Exploit-intel prioritisation | ✓ EPSS, CISA KEV, Coalition ESS, CWSS, Vulnetix LEV | ✗ |
| Reachability analysis | ✓ Tree-sitter + CVEAffected; direct/transitive/semantic | ✗ |
| Versioned VEX + audit trail | ✓ Immutable OpenVEX/CycloneDX, cosign-signable | ✗ |
| Safe Harbour autofix | ✓ Resolves + applies the nearest safe version | ✗ |
| End-of-life policy | ✓ Flags/blocks past-EOL runtimes & packages | ✗ |
| SSVC / risk-based policy | ✓ SSVC v2 + CISA/FedRAMP/Essential-8 presets | ✗ |
✓ full · ~ partial · ✗ not covered
What HackerOne does well
- World's largest vetted ethical-hacker community powering public/private/hybrid bug bounty, VDP, and PTaaS engagements
- Hai Triage: AI-plus-human-in-the-loop intake that filters duplicates/spam and risk-ranks findings to cut submission noise
- Bi-directional integrations (Jira, ServiceNow, SIEM/SOAR) so validated reports flow into existing dev and security workflows
- H1 Platform / CTEM positioning with continuous attack-surface discovery and exploitability validation
Where Vulnetix adds to it: Vulnetix ingests and orchestrates HackerOne bug-bounty and PTaaS reports into one prioritised queue with its scanner output; it does not run the human-driven testing itself. Vulnetix layers cross-scanner dedup, EPSS/CISA KEV/LEV exploit-intel scoring, reachability, immutable versioned VEX, EOL and SSVC policy, and Safe Harbour autofix on top of those findings.
No migration, no rip-and-replace. HackerOne keeps doing what it does best; Vulnetix adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today.
Centralise HackerOne results in Vulnetix
Upload HackerOne JSON, CSV output to the Vulnetix platform to deduplicate findings, prioritise them with EPSS, CISA KEV and Coalition ESS exploit intelligence, and track remediation across every scanner in a single queue.