packaging 26.3
- Source
- https://github.com/pypa/packaging
- Tag scanned
26.3- Compared with
26.2(1 signals introduced since)- Files
- 105 scanned, 23 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 25 info
- Scan time
- 21.2 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 25 of 25 warn and critical signals; 25 demoted to info.
- Disclude version
- 4.1.0
- Scanned (UTC)
- 2026-10-21 20:02
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
info
warn→ info by reviewpayload-bytes-literaltests/test_requirements.py:954:5new in this release=likely benign Prerelease Requirement pickle fixture for compatibility testing.Reasoning
A pickled Requirement with prerelease handling, saved from an older packaging version to test compatibility. It is a fixed test artifact, not code that is executed at runtime.
-
# -- General configuration ----------------------------------------------------likely benign Docs config execs the packaging package's __init__.py to load version metadata.Reasoning
Sphinx configuration reads the package's own __init__.py to populate the ABOUT metadata dict for the docs build. Executing a version file this way is a common, self-contained pattern with no network or shell activity.
-
= flikely benign Validates a license expression by compiling it and catching SyntaxError.Reasoning
compile() in eval mode is used only to validate a license expression string for syntax and raise a friendly error on SyntaxError. It does not run the expression, so the risk is minimal.
-
likely benign Test build helper runs a docker command passed in as its first argument.
Reasoning
The function invokes a caller-supplied docker command from $1 in a test build script for musllinux wheels. The dispatch is local and the target paths are fixed test paths, so this is ordinary test-harness indirection.
-
likely benign Test build helper for Alpine that takes the docker command as $1.
Reasoning
Same pattern as the glibc helper: $1 selects the container runner for an Alpine build in a test script. It is a benign indirection without obfuscation.
-
if ; thenlikely benign Dispatcher that calls build_one_in_<name> based on the CLI argument.Reasoning
The script dispatches to build_one_in_<arg> based on its first argument, a simple test-driver pattern. The function names are fixed and the set of targets is limited to the defined helpers.
-
=likely benign Pickled packaging.markers.Marker fixture used in compatibility tests.Reasoning
The bytes literal is a pickle of a packaging Marker object, kept as a backwards-compatibility fixture for unpickling data written by older packaging versions. Pickle fixtures of this kind are expected in a library test suite; the escapes are just the serialized byte representation.
-
=likely benign Legacy pickled Marker fixture for compatibility testing.Reasoning
This is another pickle fixture for a Marker object from an older packaging release, used to test loading of legacy serialized data. It matches the expected shape for a compatibility test.
-
=likely benign Legacy pickled Marker fixture in the markers test module.Reasoning
The bytes are a pickled packaging Marker serialized by a past version, included to verify unpickling still works. It is a test fixture for a known serialization format.
-
=likely benign Pickled Requirement fixture used to test legacy deserialization.Reasoning
This is a pickled packaging Requirement fixture, which includes standard pickle opcodes such as the set global reference. It is test data for backwards compatibility with older pickles, not a live payload.
-
=likely benign Legacy Requirement pickle fixture for compatibility tests.Reasoning
A pickled Requirement object from an earlier packaging release, kept to check that old serialized requirements still load. The fixture is consistent with a test suite and has no execution logic around it.
-
=likely benign Serialized Requirement fixture in the requirements tests.Reasoning
Pickle bytes representing a Requirement object for an older version, used as a regression fixture. The byte layout matches standard pickle protocol output for the packaging class.
-
=likely benign Pickled SpecifierSet test fixture for packaging 25.0 compatibility.Reasoning
The bytes literal is a protocol-2 pickle of packaging.specifiers.SpecifierSet objects, a fixture for checking that pickled specifiers still unpickle across packaging versions. It sits in a test file for the packaging library, so the escape density reflects pickle opcodes, not a hidden payload. The pass is ast, but nothing in the snippet executes or decodes the bytes.
-
=likely benign Pickled Specifier test fixture for packaging 26.0.Reasoning
This is a protocol-2 pickle of a packaging Specifier object, used as a backward-compatibility fixture in the packaging test suite. The binary shape is expected for pickle data. Nothing in the snippet loads or executes it.
-
=likely benign Pickled SpecifierSet fixture for packaging 26.0 compatibility tests.Reasoning
The literal is a pickled SpecifierSet with a frozenset of Specifier entries, a standard pickle compatibility fixture in packaging's tests. Its byte-level structure matches pickle opcodes, and the surrounding file is a test module for specifiers.
-
=likely benign Pickled Specifier fixture for packaging 26.1 tests.Reasoning
The bytes are a pickle of a packaging Specifier with _prereleases, _ranges and _spec attributes. This is a serialized test fixture for checking cross-version unpickling inside the packaging test suite, with no execution path in the snippet.
-
=likely benign Pickled SpecifierSet regression fixture for packaging 26.1.Reasoning
This is a pickled SpecifierSet with canonicalization and satisfiability flags, serialized as a regression fixture. The file is packaging's own test suite and the literal is only data.
-
=likely benign Pickled nested SpecifierSet fixture for packaging 26.2 tests.Reasoning
The literal is a protocol-2 pickle of nested SpecifierSet and Specifier objects, a compatibility fixture in packaging's tests. The high escape ratio is the normal shape of pickle opcodes and does not indicate an obfuscated dropper.
-
=likely benign Pickled packaging Tag fixture for cp39 tests.Reasoning
This is a pickled packaging.tags.Tag object with abi, interpreter and hash fields, used as a serialization fixture in packaging's tag tests. The binary content is expected for a pickle, and the file is a test module.
-
=likely benign Pickled packaging Tag fixture for cp39 under packaging 26.0.Reasoning
The bytes are a pickled packaging.tags.Tag for cp39, a serialization compatibility fixture. The raw bytes are pickle data inside a test module and are not executed.
-
=likely benign Pickled packaging Tag fixture for cp39 under packaging 25.0.Reasoning
This is a pickled Tag object with a hash field and interpreter metadata, a standard fixture for checking unpickling of packaging tags. The file is packaging's test suite and the literal is inert data.
-
=likely benign Pickled packaging Version fixture for 1.2.3 in the test suite.Reasoning
The bytes are a protocol-2 pickle of a packaging Version object with release tuple data, a compatibility fixture in the packaging version tests. The surrounding file is a test module and the snippet shows no loading or execution.
-
=likely benign Pickled packaging Version fixture for 2.0a1 in the test suite.Reasoning
This is a pickled packaging Version object for 2.0a1, a serialization fixture for test coverage of pickle compatibility. The binary structure is consistent with pickle output and the file is a test module.
-
=likely benign A pickled packaging.version.Version byte-string test fixture in the packaging library's test suite.Reasoning
The file is a test module for the packaging library, and the variable name and pickle protocol header (\x80\x02, cpackaging.version.Version) show a serialized packaging Version object used as a regression fixture for unpickling compatibility. Binary-looking escapes are the expected shape of a pickle test vector. No execution or network behavior appears in the snippet, and a test fixture of this kind is a normal pattern.
-
=likely benign A pickled packaging Version tuple test vector in the packaging test suite, encoded as a bytes literal.Reasoning
The snippet is a pickle protocol 2 byte string for a packaging Version tuple (release segments, pre, post and dev fields), in the same test file and with the same naming convention as the other fixture. It is a compatibility test vector for version parsing and pickling. Nothing in the snippet runs code or reaches out to the network.
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.
&&