arkadiyt/bounty-targets-data

This repo contains hourly-updated data dumps of bug bounty platform scopes (like Hackerone/Bugcrowd/Intigriti/etc) that are eligible for reports

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 16 minutes ago
Added to GitGenius on September 17th, 2026
Created on December 4th, 2017
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 671
Total Stargazers: 3,958 (+0)
Total Subscribers: 264 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

bounty-targets-data is a data repository that aggregates bug bounty program scopes from multiple platforms into consolidated, regularly-updated files.

The tool solves the problem of manually tracking eligible targets across fragmented bug bounty platforms. It fetches scope data from Hackerone, Bugcrowd, Federacy, Intigriti, and YesWeHack, then normalizes and publishes it in multiple formats. Users get both simplified lists (domains and wildcards) and raw JSON dumps from each platform, allowing security researchers to quickly identify which targets are in-scope for bounty hunting without visiting each platform individually.

Security researchers and bug bounty hunters should adopt this if they want a single source of truth for target scope data across multiple platforms. It suits projects that need to programmatically access or monitor bounty program eligibility. The tool is particularly valuable for those building scanning tools, automation frameworks, or maintaining their own target lists. The README explicitly notes that wildcard domains may have exclusions, so users must still verify program rules before submitting reports.

The project maintains hourly-updated data dumps with new changes detected every thirty minutes, ensuring scope information stays current as programs add or remove targets. The actual collection and processing logic is maintained in a separate repository, keeping this repository focused purely on serving the data outputs.