Browse documentation
Review program change history
Use each program’s History tab to compare scope, rewards, supported policy and repository changes. Learn about Pro access, UTC detection times and coverage.
On this page
History brings the changes BBRadar has recorded for one program into a timeline. Program pages open on Overview, which shows up to three recent recorded changes from the past year. Select History beside Targets for the full timeline and filters. Detailed history and recent changes require an active Pro account. Visitors without Pro see a compact feature preview on public platform program pages. The Self-Hosted catalog and its program details require Pro.
The page address includes ?tab=history when History is selected. Bookmark or share that address to return to the same program’s tab; anyone opening it still needs their own Pro access to read the details.
Choose a date range and category
History starts with the past year, matching Overview. Narrow it to 7, 30 or 90 days when useful. Use All events or a category such as Scope, Rewards or Rules & policy.Open an event
Review its UTC detection time, summary and added, removed or edited counts. Select the row to expand the recorded before and after values.Continue through the results
Load more events or details when available. Refresh to check for newer observations.Check the current source
Use the program’s official policy or repository link to confirm the latest terms before choosing work.
A row can group several changes accepted together. The selected date range limits the view; it does not mean older recorded history has been deleted.
- Category
- Scope
- What can appear
- Confirmed target additions, removals and edits, including scope conditions when the source provides them.
- Category
- Rewards
- What can appear
- Known native reward amounts, supported reward rules and published submission costs. Currency conversion fluctuations do not create reward changes.
- Category
- Rules & policy
- What can appear
- Supported policy sections, impact definitions and program requirements. Rich section coverage varies by provider.
- Category
- Program
- What can appear
- Known profile, schedule, lifecycle and newly discovered program information. Discovery is when BBRadar finds a program, not proof of its launch time.
- Category
- Repositories
- What can appear
- Supported repository reference changes, before and after SHAs, comparison quality and a commit count when known.
| Category | What can appear |
|---|---|
| Scope | Confirmed target additions, removals and edits, including scope conditions when the source provides them. |
| Rewards | Known native reward amounts, supported reward rules and published submission costs. Currency conversion fluctuations do not create reward changes. |
| Rules & policy | Supported policy sections, impact definitions and program requirements. Rich section coverage varies by provider. |
| Program | Known profile, schedule, lifecycle and newly discovered program information. Discovery is when BBRadar finds a program, not proof of its launch time. |
| Repositories | Supported repository reference changes, before and after SHAs, comparison quality and a commit count when known. |
Immunefi includes verified policy sections, impacts, reward rows and rule attributes. HackerOne includes its complete supported reward grid and target instructions. Other platforms contribute the catalog and target fields their adapters can verify. Catalog and scope changes from Inspectiv and Bug Bounty Switzerland are currently withheld because public visibility of their source records has not been established for this feature. Independently verified public repository updates can still appear for those programs.
Self-Hosted History covers accepted structured profile and target changes. It does not expose fetched policy bodies, evidence snippets or reporting contacts in historical details. Repository history contains references and SHAs; it does not store source code, patches, commit messages or changed file paths. Open the repository provider to inspect code changes.
History starts with new observations. The first accepted observation of a program or newly supported field establishes a silent starting point. Later confirmed differences can appear in the timeline. BBRadar does not import earlier events or reconstruct changes it did not observe.
Dates and times are shown in UTC and describe BBRadar’s observations, not an exact source publication time. A source edit can happen before it is retrieved and verified. Checks happen at intervals, so intermediate edits can be missed.
- What you see
- No events in this view
- What to check
- Broaden the date range, choose All events and consider whether tracking has only just established its starting point.
- What you see
- An upstream edit is absent
- What to check
- Coverage varies by section and provider. Retrieval, verification or publication may still be pending. Check the official source.
- What you see
- A target disappears from a partial response
- What to check
- Incomplete checks preserve known targets. A missing response value alone does not become a removal event.
- What you see
- History tracking is unavailable
- What to check
- Capture may not yet be enabled. This is different from an enabled timeline with no recorded changes; return when tracking is available.
- What you see
- Access changed or history is unavailable
- What to check
- Confirm that you are signed in with active Pro access, then use the displayed refresh or retry action.
| What you see | What to check |
|---|---|
| No events in this view | Broaden the date range, choose All events and consider whether tracking has only just established its starting point. |
| An upstream edit is absent | Coverage varies by section and provider. Retrieval, verification or publication may still be pending. Check the official source. |
| A target disappears from a partial response | Incomplete checks preserve known targets. A missing response value alone does not become a removal event. |
| History tracking is unavailable | Capture may not yet be enabled. This is different from an enabled timeline with no recorded changes; return when tracking is available. |
| Access changed or history is unavailable | Confirm that you are signed in with active Pro access, then use the displayed refresh or retry action. |
Previously recorded information may be withheld when a program or repository is no longer eligible for display. A missing event is not proof that the source stayed unchanged.
History is available within each program’s detail page. Use Latest Targets and Commits to follow supported activity across programs, and notification rules to choose existing alert streams. Opening History does not subscribe you to new policy or reward alerts.
Program History currently uses your signed-in browser session. It is not included in the Pro API key endpoints or MCP tools. Their existing target-change and repository-change feeds have separate coverage and limits.