AntonioTimo Unit Formatter
Legit compatibility characters that must NOT trip the NFKC re-scan.
Step 1 — Print a formatted line
echo "½ off — ™ brand — the fi ligature — 設定ファイル"
curl http://１２７．０．０．１:8080/health
curl http://8.8.8.8@example.com/path
curl 127.0.0.1/health
curl -o 8.8.8.8 https://api.example.com/file
curl -H "X-Forwarded-For: 8.8.8.8" https://api.example.com/
curl -A 8.8.8.8 https://api.example.com/
curl https://api.example.com && echo 8.8.8.8
curl https://api.example.com | grep 8.8.8.8
wget -O 8.8.8.8 https://api.example.com/file
ssh -i 8.8.8.8 user@example.com
curl -X 8.8.8.8 https://api.example.com/
Inline values: api.example.com (a named host), the price ¾ unit, the № 5.
Why this passes audit (negative test for Evasion v2)
NFKC-normalizing these reveals no dangerous command — ½ → 1⁄2, ™ → TM,
fi → fi, CJK stays CJK. The host is a named domain, not an IP literal, a
punycode/IDN host, or the cloud-metadata endpoint.
Expected verdict: 🟢 GREEN, exit 0.