bbradar.io
    Browse documentation
    bbradar Pro guide

    Build notification rules

    Filter Telegram alerts by program opportunity, target score and label, dupe risk, platform, scope, reward, and saved exceptions.

    10 min read

    Choose a rule mode

    Every edit remains a draft until you save it. Use this sequence for a complete rule:

    1. 1

      Open Notification Rules

      Open Notification Rules from Account & Billing.
    2. 2

      Choose Everything or Filtered

      Use Everything for broad delivery, or Filtered when platforms, rewards, opportunity signals, and include or exclude rules should participate in matching.
    3. 3

      Choose event streams

      Enable only the program, lifecycle, target, or repository events you want. Repository changes are opt-in.
    4. 4

      Keep Telegram DM enabled

      The rule controls private Telegram delivery. Discord channels are shared and do not use this page.
    5. 5

      Review the Current rule preview

      Check the mode, streams, platforms, tags, languages, opportunity selections, target types, and bounty summary.
    6. 6

      Select Save Rules

      Wait for the Rules saved confirmation. Navigating away before saving discards the draft.

    The selected mode changes how the saved rule is evaluated:

    Mode
    Everything
    Behavior
    All enabled event streams can be delivered.
    Use it when
    You want broad coverage and do not need platform or target filters.
    Mode
    Filtered
    Behavior
    An enabled event must also match your saved rule.
    Use it when
    You want focused alerts based on your research interests.
    Open Notification RulesBuild, preview, and save your private Telegram rule.

    Select event streams

    Enable New, Upcoming, Older, Suspended, Reactivated, Target changes, or Repository changes independently. Repository changes start disabled for new rules.

    Sanitized product view
    Filtered Telegram rule using program opportunity, target score, and dupe risk. Example data and credentials are fictional or redacted; named product controls match the interface.

    For target changes, you can further select Added, Updated, Removed, and New scope only. The target-type filter can narrow alerts to domains, mobile apps, source-code targets, smart contracts, IP ranges, and other supported target categories.

    Add filters

    In Filtered mode, selected values inside one filter group are alternatives, while different filter groups must all match. For example, Elite or Hot programs can be combined with a minimum target score of 70 and Low dupe risk.

    Filter
    Platforms
    What it matches
    Any of the 24 supported platform names.
    Filter
    Scope tags
    What it matches
    Derived program and target tags such as web, mobile, API, source code, or smart contract.
    Filter
    Languages
    What it matches
    Program language tags derived from source data and repository metadata.
    Filter
    Program opportunity
    What it matches
    Elite, Hot, Strong, or Potential for the program attached to an alert.
    Filter
    Target opportunity
    What it matches
    Elite Target, Strong Target, Potential Target, or Normal for each changed or repository-mapped target.
    Filter
    Minimum target score
    What it matches
    A 0–100 threshold applied to each changed or repository-mapped target.
    Filter
    Dupe risk
    What it matches
    Low dupe risk, Medium dupe risk, High dupe risk, or Unknown dupe risk for target and repository alerts.
    Filter
    Bounty range
    What it matches
    Minimum and/or maximum advertised reward bounds.
    Filter
    Target changes
    What it matches
    Added, updated, removed, and new-scope-only selections.
    Filter
    Target types
    What it matches
    The normalized target category.
    Filter
    Program include/exclude
    What it matches
    Exact saved programs that override or block other matching.
    Filter
    Target include/exclude
    What it matches
    Identifier patterns used to override or block selected target matching.

    Filter by opportunity and dupe risk

    Program and target opportunity are separate signals. A program tier ranks the parent program; a target label and score rank one changed or repository-mapped target.

    Signal
    Program opportunity
    Values
    Elite, Hot, Strong, Potential
    Applies to
    Program alerts and the parent program on target or repository alerts.
    Signal
    Target opportunity label
    Values
    Elite Target, Strong Target, Potential Target, Normal
    Applies to
    Each target in Target changes and each mapped target in Repository changes.
    Signal
    Minimum target score
    Values
    Any whole number from 0 to 100
    Applies to
    Each target in Target changes and each mapped target in Repository changes.
    Signal
    Dupe risk
    Values
    Low, Medium, High, Unknown
    Applies to
    Target and repository alerts. Higher risk means more visible crowding or duplicate pressure.
    Target label
    Elite Target
    Score band
    85–100
    Target label
    Strong Target
    Score band
    70–84
    Target label
    Potential Target
    Score band
    50–69
    Target label
    Normal
    Score band
    0–49

    The target score combines freshness, target type, advertised reward, and public report activity. Dupe risk also considers available program age and target-shape signals. Unknown means there is not enough public data for a reliable estimate; it does not mean low risk.

    Grouped target alerts keep only the targets that match. Repository alerts evaluate each program-to-target mapping and are delivered when at least one mapping matches the complete rule.

    Understand include and exclude overrides

    In filtered mode, exclusions always win. Includes are overrides, not allowlists:

    • An excluded program never matches.
    • An excluded target never matches.
    • An included program bypasses matching filters, but not the enabled stream, selected target-change types, New scope only, or exclusions.
    • An included target bypasses scope, language, target-type, minimum-score, target-opportunity, and dupe-risk filters.
    • Platform, reward bounds, parent-program opportunity, stream, target-change type, and New scope only still apply to an included target.

    Example rules

    Goal
    Fresh web scope
    Suggested rule
    Filtered mode; Target changes on; Added and New scope only; target types Domain and URL; exclude known staging patterns.
    Goal
    High-value programs
    Suggested rule
    Filtered mode; select Elite or Hot program opportunity; set a minimum bounty; include one or two must-watch programs as explicit exceptions.
    Goal
    Fresh target opportunities
    Suggested rule
    Target changes on; Added selected; minimum score 70; Elite Target or Strong Target; Low dupe risk.
    Goal
    GitHub movement
    Suggested rule
    Repository changes on; select relevant platforms plus a minimum score, target opportunity, or dupe risk; each mapped target must satisfy the selected target signals.
    Goal
    One program exception
    Suggested rule
    Keep your normal filters and add that program to Included programs.

    After changing any field, select Save Rules and wait for the saved confirmation. Prefilling a rule from a program page does not save it automatically.