version-tracker-import-h1

Import HackerOne program and scope data from bounty-targets-data JSON into a SQLite database.

1|Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework --skill version-tracker-import-h1-maybe4a6f7365
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-tracker-import-h1
Source: https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework/tree/main/version-tracker/skills/version-tracker-import-h1
Command: npx skills add https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework --skill version-tracker-import-h1-maybe4a6f7365

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bug bounty researchers need an up-to-date inventory of HackerOne programs and their in-scope assets before version checking or hunting can begin. Manually tracking hundreds of programs and thousands of scope entries is impractical, and scope changes (added assets, changed bounty eligibility) are easy to miss. ## Core Features & Use Cases - Bulk Program Import: Downloads the arkadiyt/bounty-targets-data HackerOne JSON (~15MB) and upserts programs, platforms, targets, and scope records into SQLite. - Scope Change Detection: Compares each import against previous state and writes scope_change_event rows for added assets, removed assets, eligibility changes, and instruction changes. - Idempotent Refresh: Computes a content hash of the source JSON and skips the import entirely when nothing has changed, making daily or weekly refreshes cheap. - Use Case: Bootstrap a target inventory by running the importer once, then schedule daily refreshes so your version-tracking pipeline always works against current HackerOne scope data. ## Quick Start Initialize the database with the schema, then ask the agent to import HackerOne programs using the version-tracker importer script.

Frequently Asked Questions about version-tracker-import-h1

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I import HackerOne scope data into a database?

Run the import_h1.py script after initializing the SQLite database with schema.sql. It downloads the hackerone_data.json file from the arkadiyt/bounty-targets-data repository and upserts programs, targets, and scope records automatically.

How to track bug bounty scope changes over time?

The importer compares each new import against the previous scope state and writes scope_change_event rows. It detects added assets, removed assets, bounty eligibility changes, and instruction changes, so rerunning it on a schedule builds a full change history.

Does the HackerOne importer skip unchanged data?

Yes, it computes a content hash of the downloaded JSON and compares it against the last recorded source row. If the hash matches, the import is skipped entirely, which keeps frequent refreshes fast.

Why is the id field in hackerone_data.json unreliable as a key?

Every record in hackerone_data.json has id set to 0, so it cannot distinguish programs. The importer keys programs on platform_id plus external_handle instead, which is stable across imports.

What are the limitations of the bounty-targets-data HackerOne dataset?

The dataset is updated daily by a third party, so scope data may be stale relative to the live HackerOne program pages. The JSON is also around 15MB, making the first import take roughly 10-15 seconds.