Skip to content

Tracker detection #245

Open
Open

Description

@jksalcedo

Adds and displays “contains trackers” per package/version if detected.

Activity

  1. jksalcedo commented on Apr 7, 2026

    @jksalcedo
    OwnerAuthor

    Implementation proposal: Tracker detection per package/version

    Summary

    Add and display tracker detection status at the package version level with clear states:

    • Contains trackers
    • No trackers detected
    • Unknown (not scanned / failed)

    This keeps the UX privacy-focused while being transparent about uncertainty.


    Proposed design

    1) Data model updates (package version)

    Add fields:

    • containsTrackers: Boolean? (null = unknown)
    • trackerCount: Int? (optional)
    • trackerEvidence: List<String> (optional; SDK/domains/signatures)
    • trackerScanStatus: NOT_SCANNED | SCANNING | SCANNED | FAILED
    • trackerScannedAt: Instant?
    • trackerDetectionVersion: String? (ruleset/scanner version for reproducibility)

    2) Detection pipeline

    Create TrackerDetectionService:

    1. Resolve package version artifact/metadata.
    2. Run detector(s) (signature-based initially; extensible interface).
    3. Normalize result:
      • containsTrackers = (trackerCount > 0)
    4. Persist fields + status.
    5. Emit update for reactive UI refresh (if applicable).

    3) Triggering strategy

    • Primary: run detection on version ingestion.
    • Secondary: backfill worker for existing NOT_SCANNED versions.
    • Retries for FAILED with exponential backoff + max attempts.

    4) UI behavior

    In package/version views:

    • containsTrackers == true → Contains trackers
    • containsTrackers == false && trackerScanStatus == SCANNED → No trackers detected
    • otherwise → Tracker status unknown

    Version detail can optionally show:

    • tracker count
    • evidence list
    • last scanned timestamp

    Task checklist

    • Add package-version tracker fields + DB migration
    • Implement TrackerDetectionService](#)
  2. caiv250 commented on Apr 12, 2026

    @caiv250

    You could use Exodus privacy for the same, it would be easier and better since they already have quite a large database, nonetheless if you want to make your own database, go ahead.
    On a second thought an alternative would be better, but could you maybe consider this as a different service separated (but used by) Librefind? It would be better as it could help other people in different services than Librefind

  3. jksalcedo commented on Aug 23, 2026

    @jksalcedo
    OwnerAuthor

    I'll be using Exodus privacy

  4. TheTearMiser commented on Sep 15, 2026

    @TheTearMiser

    https://github.com/MuntashirAkon/AppManager

    Fully foss option providing TotalVirus Scanning and Hash checking as well as being an installer.

    The features inside Libre Find is already scope-creapin this dirrectiin and the effects of that are being shown jn the fact that the main things this app are for are still sketchy and were adding features?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions