goldset

One function

verdict in leeguooooo/claude-code-usage-bar

The author described this change as “fix(ip_score): ban-risk 阈值 67→70,与 crit band 对齐”. It counts as a record because the check below fails on the code as it stood at 6393539b4 and passes on a2a87b82e, with nothing else changed between the two runs.

Projectleeguooooo/claude-code-usage-bar
Fix saved2026-07-03
Sharing licenceMIT · LICENSE
Change size+4 −1

What the code was meant to do, written into the code itself as a docstring

Claude-account decision. Region first (the documented trigger), then anonymizer egress, then plain datacenter (a softer caution).

The change

22 """Claude-account decision. Region first (the documented trigger), then
33 anonymizer egress, then plain datacenter (a softer caution)."""
44 cc = (country or "").upper()
5- ip_is_ban = risk >= 67 or typ in _BAN_TYPES
5+ # 70 = the classify() crit-band cutoff. Was 67, which disagreed with the
6+ # band (risk 67-69 would read as ban-risk here but only 中度 there); keep
7+ # them aligned, matching the ip-check service fix.
8+ ip_is_ban = risk >= 70 or typ in _BAN_TYPES
69
710 if cc in _SANCTIONED:
811 return {"verdict": "ban-risk", "region": True}

The check that tells the two apart

fail→pass·tests/test_ip_score.py::test_ban_threshold_aligns_with_crit_band

Check file tests/test_ip_score.py, taken without changes from the fix and copied onto the older code, so the exact same check runs against both versions.

Origin and history

The fixa2a87b82e28f2027f036594dc9dc19d65a2c3308
The code before it6393539b416a55a83ea9fee5218d8d2d35b563f9
Broken version dated2026-07-03
Moduleclaude_statusbar.ip_score
Units changedverdict
Fingerprinta03bdbffedb1a7b7
Checked2026-08-18 by goldset/0.1

Every field above is generated by our program. None of it is written by hand.

Other bugs found in leeguooooo/claude-code-usage-bar