Skip to content

Add residential proxy data to anonymizer object#1738

Open
oschwald wants to merge 1 commit into
mainfrom
greg/stf-997-add-residential-to-anonymizer
Open

Add residential proxy data to anonymizer object#1738
oschwald wants to merge 1 commit into
mainfrom
greg/stf-997-add-residential-to-anonymizer

Conversation

@oschwald

Copy link
Copy Markdown
Member

Summary

The GeoIP Insights web service is adding a residential sub-object to the anonymizer object, sourced from the full-feed GeoIP Residential Proxy database. Because that feed is a superset of the residential proxies in GeoIP Anonymous Plus, the anonymizer object may now contain only the residential key.

  • New reusable record for the feed shape (confidence, network_last_seen, provider_name) named AnonymizerFeed, so future sibling feeds (VPN, mobile, datacenter) can share it
  • New residential property on the Anonymizer record
  • Tests, fixtures, and changelog updated

(The reusable interface is named AnonymizerFeedRecord per this repo's record-interface naming convention.)

Testing

npm test (130 tests), npm run lint, npm run build, and npm run prettier:ci all pass.

🤖 Generated with Claude Code

This adds support for the new residential sub-object nested within the
anonymizer object in the GeoIP2 Insights web service response. The
residential object is sourced from the GeoIP Residential Proxy
database and contains a confidence score, the last seen date for the
network, and the associated provider name. Because the residential
proxy feed is a superset of what is available in Anonymous Plus, the
anonymizer object may now contain only the residential property. The
shared shape of these feed records is exposed as a new
AnonymizerFeedRecord interface so it can be reused if additional
feeds (e.g. vpn, mobile, datacenter) are added in the future.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 10, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@oschwald, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: dba8a779-464e-4338-a834-ac100386c46d

📥 Commits

Reviewing files that changed from the base of the PR and between 292d322 and 3595aa0.

📒 Files selected for processing (4)
  • CHANGELOG.md
  • fixtures/geoip2.json
  • src/records.ts
  • src/webServiceClient.spec.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch greg/stf-997-add-residential-to-anonymizer

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new residential property to the AnonymizerRecord interface within the GeoIP2 Insights response model. It defines a new AnonymizerFeedRecord interface containing confidence, networkLastSeen, and providerName fields, updates the test fixtures, and adds corresponding unit tests to verify the new property. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant