Skip to content

Document residential sub-object of the anonymizer object - #1701

Merged
horgh merged 2 commits into
mainfrom
greg/stf-1005-document-anonymizer-residential
Jul 17, 2026
Merged

Document residential sub-object of the anonymizer object#1701
horgh merged 2 commits into
mainfrom
greg/stf-1005-document-anonymizer-residential

Conversation

@oschwald

@oschwald oschwald commented Jul 14, 2026

Copy link
Copy Markdown
Member

Summary

Documents the new residential sub-object of the anonymizer object (confidence, network_last_seen, provider_name) in the GeoIP Insights response docs, and adds release notes for both GeoIP and minFraud.

The minFraud responses page inherits the anonymizer object through the existing "ip_address is the GeoIP Insights response body" reference, matching how the anonymizer object itself was documented, so no schema changes are needed there.

This should be merged when the web services begin returning the field.

Validation

cspell, internal-link check, and prettier pass on the changed files.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • New Features

    • Added residential proxy details to GeoIP Insights and minFraud response data, including confidence, last-seen network date, and provider name.
    • Documented when residential proxy information may appear.
  • Documentation

    • Updated response examples, schemas, and release notes for the new anonymizer data.
  • Chores

    • Improved link validation for anchor and text fragments.
    • Updated site tooling versions.

@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

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

Next review available in: 49 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: 299aacdc-6436-4a9c-ab97-72810254b4b6

📥 Commits

Reviewing files that changed from the base of the PR and between 3e6ad71 and 1791a9a.

⛔ Files ignored due to path filters (1)
  • mise.lock is excluded by !**/*.lock
📒 Files selected for processing (7)
  • .precious.toml
  • content/geoip/docs/web-services/responses.md
  • content/geoip/release-notes/2026.md
  • content/minfraud/release-notes/2026.md
  • lychee.toml
  • mise.toml
  • wrangler.toml
📝 Walkthrough

Walkthrough

The change documents GeoIP and minFraud anonymizer.residential response data, adds related 2026 release notes, expands fragment validation, and updates pinned site tooling versions.

Changes

Residential anonymizer documentation

Layer / File(s) Summary
GeoIP response schema and examples
content/geoip/docs/web-services/responses.md
Documents anonymizer.residential, its three fields, presence conditions, and updated response examples.
Product release notes
content/geoip/release-notes/2026.md, content/minfraud/release-notes/2026.md
Adds dated release notes covering the residential anonymizer object and affected products.

Site tooling configuration

Layer / File(s) Summary
Link checker and tool versions
lychee.toml, mise.toml
Enables full URL fragment checking and updates pinned site tooling versions.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested reviewers: horgh

Poem

A bunny hops through fields of JSON bright,
“Residential details,” it adds with delight.
Anchors now bloom, tools gain speed,
Release notes record each needed seed.
Hop, hop—clean docs succeed!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main change: documenting the new residential sub-object of the anonymizer object.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch greg/stf-1005-document-anonymizer-residential

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
Contributor

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 adds a new residential sub-object to the anonymizer object for GeoIP Insights, minFraud Insights, and minFraud Factors. It updates the response documentation, JSON examples, and release notes to describe the new fields: confidence, network_last_seen, and provider_name. The review feedback recommends correcting the punctuation of several Markdown links by placing the trailing periods outside of the link brackets and parentheses.

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.

{{< geoip-schema-row key="confidence" valueType="integer" valueTypeNote="min: 1, max: 99" insights="true">}}
A score ranging from 1 to 99 that represents our percent confidence that the network is an actively used residential proxy.

[Learn more about anonymizer confidence on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/anonymizer-and-proxy-data-maxmind)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

When a sentence ends with a Markdown link, the period should be placed outside the link brackets and parentheses, not inside the link text.

Suggested change
[Learn more about anonymizer confidence on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/anonymizer-and-proxy-data-maxmind)
[Learn more about anonymizer confidence on our Knowledge Base](https://support.maxmind.com/knowledge-base/articles/anonymizer-and-proxy-data-maxmind).
References
  1. When a sentence ends with a Markdown link, the period should be placed outside the link brackets and parentheses, not inside the link text.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Claude, on behalf of Greg: Keeping the period inside the link — that placement is this file's existing convention (30+ occurrences throughout responses.md), so changing only the new lines would make them inconsistent with the surrounding document.

{{< geoip-schema-row key="network_last_seen" valueType="string" insights="true">}}
The last day that the network was sighted in our analysis of residential proxies. This is in the ISO 8601 date format (YYYY-MM-DD).

[Learn more about anonymizer and proxy detection on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/anonymizer-and-proxy-data-maxmind)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

When a sentence ends with a Markdown link, the period should be placed outside the link brackets and parentheses, not inside the link text.

Suggested change
[Learn more about anonymizer and proxy detection on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/anonymizer-and-proxy-data-maxmind)
[Learn more about anonymizer and proxy detection on our Knowledge Base](https://support.maxmind.com/knowledge-base/articles/anonymizer-and-proxy-data-maxmind).
References
  1. When a sentence ends with a Markdown link, the period should be placed outside the link brackets and parentheses, not inside the link text.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Claude, on behalf of Greg: Keeping the period inside the link — that placement is this file's existing convention (30+ occurrences throughout responses.md), so changing only the new lines would make them inconsistent with the surrounding document.


Please note that MaxMind identifies a subset of residential proxy providers. A current list of identified providers is available on request.

[Learn more about residential proxy provider detection on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/anonymizer-and-proxy-data-maxmind)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

When a sentence ends with a Markdown link, the period should be placed outside the link brackets and parentheses, not inside the link text.

Suggested change
[Learn more about residential proxy provider detection on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/anonymizer-and-proxy-data-maxmind)
[Learn more about residential proxy provider detection on our Knowledge Base](https://support.maxmind.com/knowledge-base/articles/anonymizer-and-proxy-data-maxmind).
References
  1. When a sentence ends with a Markdown link, the period should be placed outside the link brackets and parentheses, not inside the link text.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Claude, on behalf of Greg: Keeping the period inside the link — that placement is this file's existing convention (30+ occurrences throughout responses.md), so changing only the new lines would make them inconsistent with the surrounding document.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 16, 2026

Copy link
Copy Markdown

Deploying dev-site with  Cloudflare Pages  Cloudflare Pages

Latest commit: 1791a9a
Status: ✅  Deploy successful!
Preview URL: https://a81f93dc.dev-site-4ua.pages.dev
Branch Preview URL: https://greg-stf-1005-document-anony.dev-site-4ua.pages.dev

View logs

@oschwald
oschwald force-pushed the greg/stf-1005-document-anonymizer-residential branch 3 times, most recently from 3e6ad71 to 0416416 Compare July 17, 2026 01:43
oschwald and others added 2 commits July 17, 2026 01:49
Add the `residential` sub-object (confidence, network_last_seen,
provider_name) to the GeoIP Insights `anonymizer` response docs,
including a note that the object may be present even when none of the
other `anonymizer` fields are populated.

minFraud Insights/Factors inherit the `anonymizer` object via the
existing "ip_address is the GeoIP Insights response body" reference,
so no separate schema changes are needed there; add release notes to
both GeoIP and minFraud instead.

STF-997

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Bump hugo, lychee, pnpm, and precious to their latest available
versions via `mise up --bump` and refresh mise.lock. Leave dart-sass
pinned (its latest release lookup on GitHub is currently failing) and
node untouched (idiomatic .nvmrc version, out of scope here).

Migrate lychee.toml for lychee 0.24's breaking config change:
include_fragments is now a string enum instead of a bool. Use "full"
(house convention) to check both anchor fragments (#section) and text
fragments (#:~:text=example). Verified by running `mise run
check-links` (the same task CI uses) with the cache cleared, which
built the site and passed the link check with 0 errors.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@oschwald
oschwald force-pushed the greg/stf-1005-document-anonymizer-residential branch from 0416416 to 1791a9a Compare July 17, 2026 01:53
@horgh
horgh merged commit e9de902 into main Jul 17, 2026
11 checks passed
@horgh
horgh deleted the greg/stf-1005-document-anonymizer-residential branch July 17, 2026 18:01
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.

2 participants