bbradar.io
    Browse documentation
    bbradar Pro guide

    Follow the latest target changes

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

    6 min read

    Understand the change tabs

    1. 1

      Open Latest Targets

      Go to Latest Targets while signed in with Pro.
    2. 2

      Choose a feed tab

      Select Added, Re-added, Updated, Removed, or Commits. Only one feed tab is active at a time.
    3. 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. 4

      Open the source context

      Use the program or external source link to validate the event against the authoritative platform or GitHub page.
    Sanitized product view
    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
    Added
    Meaning
    A newly confirmed canonical target entered active scope.
    Tab
    Re-added
    Meaning
    A previously seen target returned to active scope.
    Tab
    Updated
    Meaning
    A material property of an existing target changed.
    Tab
    Removed
    Meaning
    A target left active scope after removal safeguards and confirmation.
    Tab
    Commits
    Meaning
    A monitored GitHub branch head moved; this is a separate repository feed.
    Open Latest TargetsReview scope movement and repository branch-head changes.

    Search and filter

    1. 1

      Search with at least two characters

      Enter a target, program, repository, branch, or SHA fragment appropriate to the active feed.
    2. 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. 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. 4

      Narrow by profile

      Select platforms, tags, and languages. Different filter groups combine, so each active group must match.
    5. 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. There they are evaluated against targets mapped to each repository event, while the event itself keeps its repository and branch-head model.

    Export the current page

    1. 1

      Filter the target feed

      Set the tab, search, and filters before choosing what to export.
    2. 2

      Choose 5, 10, or 50 targets

      The selector limits the unique target identities taken from the currently loaded page.
    3. 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.

    Why some changes are suppressed

    bbradar suppresses historical backfills, normalization-only migrations, unchanged reactivations, unconfirmed additions, and other non-actionable transitions from the latest feed. Empty or suspiciously large removals are guarded so a partial upstream response does not look like a real scope clear.