# Follow the latest target changes | bbradar.io

> Monitor material scope movement and filter target or Commits feeds by score, opportunity label, and dupe risk.

Source: [https://bbradar.io/docs/pro/latest-changes](https://bbradar.io/docs/pro/latest-changes)

<a id="change-tabs"></a>

## [Understand the change tabs](https://bbradar.io/docs/pro/latest-changes.md#change-tabs)

1. ### Open Latest Targets

   Go to [Latest Targets](https://bbradar.io/latest-targets) while signed in with Pro.
2. ### Choose a feed tab

   Select Added, Re-added, Updated, Removed, or Commits. Only one feed tab is active at a time.
3. ### Review the result card

   Check the program, platform, target identity or repository mapping, timestamps, scope state, opportunity label, score, and dupe risk when available.
4. ### Open the source context

   Use the program or external source link to validate the event against the authoritative platform or repository-host page.

Sanitized product view

Latest changes

Material bounty-scope movement

Pro

AddedRe-addedUpdatedRemovedCommits

Min score: 70Strong TargetLow dupe risk

api.example.test

Acme Cloud · HackerOne

78/100 · Strong Target · Low dupe risk

ADDED

shop.example.test

Acme Cloud · HackerOne

74/100 · Strong Target · Low dupe risk

ADDED

Latest Targets feed filtered by minimum score, opportunity label, and dupe risk. Example data and credentials are fictional or redacted; named product controls match the interface.

| Tab | Meaning |
| --- | --- |
| Added | A new target entered active scope. |
| Re-added | A previously seen target returned to active scope. |
| Updated | An important detail of an existing target changed. |
| Removed | A target was confirmed as no longer active scope. |
| Commits | A supported repository branch changed; this is a separate repository feed. |

[Open Latest TargetsReview scope movement and repository branch updates.](https://bbradar.io/latest-targets)

<a id="search-filter"></a>

## [Search and filter](https://bbradar.io/docs/pro/latest-changes.md#search-filter)

1. ### Search with at least two characters

   Enter a target, program, repository, branch, or SHA fragment appropriate to the active feed.
2. ### Set scope-state options

   For target feeds, include Removed targets, Not eligible for bounty, or Out-of-scope targets only when you need them.
3. ### Set intelligence filters

   Choose a minimum Target Opportunity Score, one opportunity label, and one dupe-risk level. Low dupe risk is the least crowded estimate.
4. ### Narrow by profile

   Select platforms, tags, and languages. Different filter groups combine, so each active group must match.
5. ### Reset when finished

   Use **Reset filters** to return to the default feed.

The opportunity-label choices are Elite Target, Strong Target, Potential Target, and Normal.

The same score, label, and dupe-risk controls also apply on the Commits tab by using the program targets linked to each repository event.

Tip

Use either a label or a minimum score when you want a broad threshold. Combining both is stricter: every result must satisfy both selections.

<a id="export-changes"></a>

## [Export the current page](https://bbradar.io/docs/pro/latest-changes.md#export-changes)

1. ### Filter the target feed

   Set the tab, search, and filters before choosing what to export.
2. ### Choose 5, 10, or 50 targets

   The selector limits the unique target identities taken from the currently loaded page.
3. ### Copy or download

   Select **Copy targets** or **Download .txt**.

This is not a bulk dump of all historical events. Repository changes do not currently have an export control.

<a id="feed-safety"></a>

## [Understand missing changes](https://bbradar.io/docs/pro/latest-changes.md#feed-safety)

Latest Targets focuses on confirmed, meaningful scope changes. Routine corrections, incomplete updates, and changes that have not been confirmed may not appear.

For a timeline of one program’s recorded scope, rewards and supported policy changes, open its **History** tab. [Program History](https://bbradar.io/docs/pro/program-history.md) begins with new observations and has its own coverage; it does not reconstruct older events from this feed.

Note

If you expect a change and do not see it, check the program’s official scope source before acting.