tqdm 4.70.1
- Source
- https://github.com/tqdm/tqdm
- Tag scanned
v4.70.1- Compared with
v4.70.0(0 signals introduced since)- Files
- 72 scanned, 11 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 1 info
- Scan time
- 2.2 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 1 of 1 warn and critical signal; 1 demoted to info.
- Disclude version
- 4.0.0
- Scanned (UTC)
- 2026-10-14 18:18
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
⟨U+00A0⟩⟨U+00A0⟩⟨U+00A0⟩⟨U+00A0⟩ 100%|#########################################|⟨U+00A0⟩100/100⟨U+00A0⟩[00:10<00:00,⟨U+00A0⟩⟨U+00A0⟩9.95it/s] ```likely benign A markdown example showing a tqdm progress loop, where a non-breaking space appears in the indentation of an embedded Python snippet.Reasoning
The finding is a raw-pass whitespace anomaly (non-breaking space U+00A0) inside an embedded Python code block in a markdown document. The snippet is a tqdm progress-bar demo with a sleep loop and its printed output; there is no execution, network, or encoded payload. The NBSP is most likely a copy-paste artifact from a rendered document, a common cosmetic issue in prose-embedded code. Raw-pass findings have a higher false-positive rate, and this one is benign.
Reproduce This Scan
Run disclude locally to verify. Add --format sarif for SARIF output. Add --llm (with an API key in the environment) to include the LLM review.
&&