# tombcato/clash-ip-checker

🤖Automated node IP risk checking and tagging tool for Clash (适用于 Clash 代理的自动化节点 IP 风险检查并重命名标记工具)

Repository: https://github.com/tombcato/clash-ip-checker
Canonical: https://ross.abutalabs.com/products/clash-ip-checker
Homepage: https://tombcato.github.io/clash-ip-checker/
Language: Python
License: GPL-3.0
License Family: copyleft
Topics: automation, clash, clash-verge, iprisk, playwright, python, ippure
Last push: 2026-01-30T16:38:01+00:00

## Health v2 (maintenance only)
Score: 44/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 65, release rhythm 33, longevity 18
- inputs: {"age_days": 264, "days_push": 215, "days_rel": 235, "gap_med": null, "n_releases_24m": 1}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1052, forks 69 (observed 2026-08-28T04:03:23.335353+00:00)

## What it is
A Python automation tool for Clash proxy users that iterates through proxy nodes, checks each node's IP purity, bot ratio, and IP type via IPPure or Ping0, and rewrites the Clash config with risk tags appended to node names. It offers a Web UI, fast API mode, fallback between detection sources, and Docker deployment.

## Use cases
- check if my clash proxy nodes are clean residential IPs
- automatically tag clash nodes with IP risk scores
- find which proxy nodes are datacenter IPs before registering accounts
- rename clash subscription nodes with purity and bot ratio metrics
- batch test proxy node IP quality without manual switching
- detect shared or blacklisted IPs in my clash config
- run IP purity checks on a NAS via docker for clash nodes

## When to choose
- you use Clash or a compatible core and want automated, hands-off node IP quality auditing
- you want results written directly back into a usable Clash config with visual risk tags
- you prefer a self-hosted, open-source tool that keeps subscription data local

## When to avoid
- you use a proxy client other than Clash or its compatible cores
- you need a one-off manual IP lookup rather than bulk node checking
- you cannot run Python or Docker in your environment

## Facets
- artifact type: cli-tool
- maturity: active
- function: workflow-automation, web-scraping, developer-tools
- domain: networking, privacy, developer-tools
- platform: python, cross-platform, cli, self-hosted
- tags: clash, proxy, ip-purity, node-checking, playwright, proxy-config, risk-assessment, automation, docker

## Member repositories
- tombcato/clash-ip-checker (main) score 44

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:03:23.335353+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:59:46.158606+00:00, confidence not recorded.
  - readme: https://github.com/tombcato/clash-ip-checker (fetched 2026-08-28T04:03:23.335353+00:00, sha ac493e7060fb)
  - homepage: https://tombcato.github.io/clash-ip-checker/ (fetched 2026-08-29T13:01:27.790042+00:00, sha 83efb2d27f75)
- Data as of 2026-08-30T08:39:29.467469+00:00.