Update PIR broker bundle - 2026-04-06

[daxmobile]

Task/Issue URL:https://app.asana.com/1/137249556945/project/414730916066338/task/1213965665740964?focus=true

PIR Broker Bundle Update

Automated update of PIR broker JSON files from the remote bundle.

Changes

Added (2):

• anywho.com.json
• spyfly.com.json

Checklist

• Verify broker changes look correct
• All tests must pass

---

Note

Medium Risk
Adds two new broker JSON configs that will change which sites PIR scans/opts out from; the SpyFly flow depends on Cloudflare Turnstile/UI selectors and is explicitly incomplete (stops before results), which could cause scan failures or no-op behavior if enabled.

Overview
Adds new PIR broker configurations for AnyWho and SpyFly.

anywho.com.json introduces a templated people-search scan and delegates opt-out to its parent (spokeo.com) via parentSiteOptOut. spyfly.com.json adds a scan workflow that navigates to the privacy request form, fills user data, gates on Turnstile completion, and then terminates on the email step (extracting no results), with no opt-out step defined.

^{Reviewed by Cursor Bugbot for commit be9d46f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit be9d46f. Configure here.}

[cursor]

Missing optOut step causes broker loading failure

High Severity

The spyfly.com.json broker defines only a scan step and no optOut step. When PirRepository.updateBrokerData() processes this broker, it calls broker.steps.first { it.contains("\"stepType\":\"optOut\"") } which throws NoSuchElementException because no matching step exists. While the exception is caught in BrokerJsonProcessor, the entire broker (including its scan step) silently fails to persist to the database, making it completely non-functional. Every other broker in the repository includes both a scan and an optOut step.

---

_{Please tell me if this was useful or not with a 👍 or 👎.}

 

^{Reviewed by Cursor Bugbot for commit be9d46f. Configure here.}

[cursor]

Inconsistent state format in profile URL identifier template

Medium Severity

The scan navigate URL uses ${state|stateFull|downcase} (producing a full state name like "california"), but the profileUrl identifier template uses ${state|downcase} (producing an abbreviation like "ca"). Every other broker in the repository that includes state in both the scan URL and profile URL identifier (e.g., spokeo.com.json, freepeopledirectory.com.json) uses the same state format in both. This mismatch likely means stateFull was accidentally omitted from the identifier, which would cause profile URL pattern matching to fail and prevent proper profile identification.

---

_{Please tell me if this was useful or not with a 👍 or 👎.}

Additional Locations (1)

• pir/pir-impl/src/main/assets/brokers/anywho.com.json#L15-L16

 

^{Reviewed by Cursor Bugbot for commit be9d46f. Configure here.}