msgpack 1.2.3
- Source
- https://github.com/msgpack/msgpack-python
- Tag scanned
v1.2.3- Compared with
v1.2.2(0 signals introduced since)- Files
- 44 scanned, 9 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 11 info
- Scan time
- 6.0 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 5 of 5 warn and critical signals; 5 demoted to info.
- Disclude version
- 4.0.0
- Scanned (UTC)
- 2026-10-14 18:38
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
DOCKER_DIR=""likely benign Build script sources shared.env relative to its own directory.Reasoning
Sourcing a shared env file via a path derived from the script's own directory is a standard build-script idiom; no remote fetch or decoding is involved.
-
-
DOCKER_DIR=""likely benign Bash script sources shared.env located relative to its own directory.Reasoning
Sourcing a script path derived from the script's own directory via BASH_SOURCE is a common, benign build-script idiom; the path is not attacker-controlled input and shared.env is a sibling config file.
-
PYBIN=/opt/python//bin -
-
-
-
-
, b, ),likely benign Test fixture bytes encoding a msgpack-like sequence in a serialization test.Reasoning
The byte string is a sequence of sequential hex bytes 0x00..0x0e preceded by 0x9f, which is a deliberate test vector for a msgpack-style serialization library. Sequential counting bytes are typical test data, not obfuscated payload.
-
, b, ), ,likely benign Test fixture bytes for a msgpack array header followed by sequential data.Reasoning
The bytes are a msgpack header (0xdc, 16-bit length 0x0010) followed by sequential counter bytes, a clear hand-written encoding test vector in a serialization test file.
-
likely benign Test case byte literal representing msgpack-encoded data passed to a format check.
Reasoning
The concatenated bytes literal is a msgpack format test vector (0x96 fixarray, 0xde map16 headers) inside a test check call; binary-shaped content is expected for a serialization format test and there is no execution or decoding of it.
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.
&&