harden: a holders_count that is not plain digits is unknown, not read in part #445

Merged
clawbot merged 1 commits from issue-251-holders-count-parse into next 2026-10-05 02:59:16 +02:00
1 Commits
Author SHA1 Message Date
sneak 57e5b7c0ba harden: a holders_count that is not plain digits is unknown, not read in part (closes #251)
check / check (push) Failing after 3s
e2e / e2e-chrome (push) Failing after 3s
e2e / e2e-firefox (push) Failing after 2s
parseHoldersCount used parseInt, which reads "1,000" as 1, "0x10" as 0 and
"1e3" as 1: a reported low count, which hides the token in the transaction
history and the send-screen token selector. It now accepts only a whole
number of zero or more, or a string of digits alone, no larger than
Number.MAX_SAFE_INTEGER, and returns null for anything else. The balance
list's holders !== null check did nothing, since null >= 1000 is already
false, and is dropped. README.md and docs/README.md say how each filter
treats an unknown count and that the token screen then leaves out its
Holders row; README.md lists src/shared/holders.js.

Model: opus-5-5
2026-10-05 00:29:01 +00:00