Update PIR broker bundle - 2026-04-27

[daxmobile]

Task/Issue URL: https://app.asana.com/0/414730916066338/1214283450657766/f

---

PIR Broker Bundle Update

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

Changes

Added (1):

• weinform.org.json
  Updated (28):
• advancedbackgroundchecks.com.json (0.7.0 → 0.8.0)
• backgroundcheckers.net.json (0.2.0 → 0.3.0)
• beenverified.com.json (0.9.0 → 0.10.0)
• centeda.com.json (0.90.0 → 0.91.0)
• checksecrets.com.json (0.2.0 → 0.3.0)
• fastbackgroundcheck.com.json (0.7.0 → 0.8.0)
• fastpeoplesearch.com.json (0.7.0 → 0.8.0)
• inmatessearcher.com.json (0.2.0 → 0.3.0)
• mugshotlook.com.json (0.5.0 → 0.6.0)
• mylife.com.json (0.7.0 → 0.8.0)
• neighborwho.com.json (0.5.0 → 0.6.0)
• peoplefinders.com.json (0.9.0 → 0.10.0)
• peoplelooker.com.json (0.5.0 → 0.6.0)
• peoplesearch123.com.json (0.2.0 → 0.3.0)
• peoplesearcher.com.json (0.6.0 → 0.7.0)
• peoplesearchusa.org.json (0.2.0 → 0.3.0)
• personsearchers.com.json (0.2.0 → 0.3.0)
• privaterecords.net.json (0.2.0 → 0.3.0)
• privatereports.com.json (0.995.0 → 0.996.0)
• publicsearcher.com.json (0.5.0 → 0.6.0)
• sealedrecords.net.json (0.2.0 → 0.3.0)
• searchpeoplefree.com.json (0.8.0 → 0.9.0)
• secretinfo.org.json (0.4.0 → 0.5.0)
• spyfly.com.json (0.4.0 → 0.5.0)
• truepeoplesearch.com.json (0.7.0 → 0.8.0)
• truthrecord.org.json (0.4.0 → 0.5.0)
• usa-people-search.com.json (0.7.0 → 0.8.0)
• veripages.com.json (0.6.0 → 0.7.0)

Checklist

• Verify broker changes look correct
• All tests must pass

---

Note

Medium Risk
Medium risk because it changes broker scan/opt-out automation steps and selectors across many sites; small selector mistakes or anti-bot flow changes can break matching/extraction at runtime.

Overview
Updates the PIR bundled broker configurations, adding a new weinform.org.json broker and bumping versions across the existing bundle.

Most updates adjust scan/opt-out flows to better handle anti-bot interstitials (Cloudflare challenge/Turnstile) by adding explicit wait expectations (negative selectors or token-present checks) and updating page-ready selectors. Several privatereports.com-family brokers also switch to the api/helper/optOutLight/search entrypoint and simplify/retune form, captcha, and extraction selectors (notably mugshotlook.com, peoplesearcher.com, publicsearcher.com, secretinfo.org, truthrecord.org).

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

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ 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 c5b636f. Configure here.}

[cursor]

Missing failSilently on condition expectations in rewritten brokers

Medium Severity

The condition action for the SVG captcha is missing "failSilently": true on its expectation in all six rewritten/new broker files (mugshotlook, peoplesearcher, publicsearcher, secretinfo, truthrecord, weinform). The parent broker privatereports.com and every other condition action in the codebase (fastbackgroundcheck, fastpeoplesearch, beenverified) include failSilently: true on their condition expectations. The comment itself says "captcha is not always present at this stage," which implies the element may not be found — exactly the scenario failSilently: true is designed for.

---

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

Additional Locations (2)

• pir/pir-impl/src/main/assets/brokers/peoplesearcher.com.json#L91-L99
• pir/pir-impl/src/main/assets/brokers/weinform.org.json#L91-L99

 

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