miniz_oxide 0.9.1

Source: https://github.com/Frommi/miniz_oxide
Commit scanned: 4e582392df3a (recorded by crates.io)
Directory: miniz_oxide (only this part of the repository was scanned)
Compared with: 86d92e8d284b (0 signals introduced since)
Files: 22 scanned, 9 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 21:03

Signals

Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.

info ~~warn~~ → info by review narrow-file-charset miniz_oxide/tests/test_data/numbers.txt:1:1

file uses only 10 distinct printable characters ("0123456789") — JSF*ck-style or character-constrained obfuscation (raw pass, confidence 0.90)
```
0001
0002
0003
```
dismissed LLM, confidence 0.97 A plain-text test data file of sequential zero-padded numbers, using only digit characters.
Reasoning
The file is a plain text test fixture containing only digits and newlines, as the snippet shows sequential numbers 0001, 0002, 0003. A narrow character set in a numeric data file is expected, not JSF*ck-style obfuscation, since JSF*ck produces executable JavaScript, not sequential numbers in a .txt test fixture. Raw-pass charset heuristics have a high false-positive rate on data files like this.

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.

cargo install disclude --version 4.0.0
git clone https://github.com/Frommi/miniz_oxide miniz_oxide && cd miniz_oxide
git checkout 4e582392df3a739d2b0dfd2c537dc33e8942be38
disclude scan --severity info --diff 86d92e8d284b0acd451e7b6db6bdef41ae9c9db4 miniz_oxide