object 0.40.0

Source: https://github.com/gimli-rs/object
Tag scanned: v0.40.0
Compared with: v0.39.1 (0 signals introduced since)
Files: 148 scanned, 140 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:22

Signals

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

info ~~warn~~ → info by review encoding-hex tests/read/elf.rs:45:11

20 consecutive `\xNN` escapes (entropy 4.3 bits/byte) (raw pass, confidence 0.65)
```
        buildid,
        b"\xf9\xc0\xc6\x05\xd3\x76\xbb\xa5\x7e\x02\xf5\x74\x50\x9d\x16\xcc\xe9\x9c\x1b\xf1"
    );
}
```
dismissed LLM, confidence 0.95 A test in an ELF parsing crate compares against a 20-byte build-id literal written as hex escapes.
Reasoning
The finding is a raw-pass hex-escape signal on a byte-string literal in a test file. The bytes look like a 20-byte ELF build-id, passed as an expected value to an assertion alongside buildid. This is ordinary test fixture data, not obfuscated or malicious code. Raw-pass findings have a high false-positive rate, and nothing here executes or hides behavior.

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/gimli-rs/object object && cd object
git checkout v0.40.0
disclude scan --severity info --diff v0.39.1 .