xxhash 3.6.1
- Source
- https://github.com/ifduyue/python-xxhash
- Artifact scanned
xxhash-3.6.1.tar.gz- Compared with
xxhash-3.6.0.tar.gz(12 signals introduced since)- Files
- 80 scanned, 34 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 24 info
- Scan time
- 13.6 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 15 of 15 warn and critical signals; 15 demoted to info.
- Disclude version
- 4.3.0
- Scanned (UTC)
- 2026-10-23 14:14
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
info
warn→ info by reviewdynamic-executiondeps/xxhash/.github/workflows/ci.yml:121:42new in this release&& && && && && && && &&likely benign CI step echoing the configured C compiler version using the $CC variable.Reasoning
Standard CI step printing compiler version via $CC; the variable is set by the workflow matrix/env, a common and benign pattern in xxhash's CI.
-
info
warn→ info by reviewdynamic-executiondeps/xxhash/.github/workflows/ci.yml:122:44new in this release&& && && && && && && && && ||likely benign CI step printing compiler and CPU diagnostics using $CXX.Reasoning
Same benign pattern as the $CC line: prints the C++ compiler configured via $CXX and checks /proc/cpuinfo for diagnostics.
-
info
critical→ info by reviewdynamic-executiondeps/xxhash/.github/workflows/ci.yml:204:171new in this release# Run "make check" if /proc/cpuinfo has flags for avx512. && CPPFLAGS="-mavx512f -DXXH_VECTOR=XXH_AVX512" || ( && )likely benign Conditional AVX512 test runner logic using a no-op command substitution fallback.Reasoning
The $(exit 0) and $(exit 1) substitutions are inert no-op constructs used as fallback in a shell chain; the grep for avx512 flags is legitimate test-selection logic. Flagged only because the scanner cannot resolve the command name.
-
info
warn→ info by reviewdynamic-executiondeps/xxhash/.github/workflows/ci.yml:436:17new in this release&& && && &&likely benign CI step reporting cross-compiler version via $XCC.Reasoning
Compiler version reporting using $XCC set by the build matrix for cross-compilation toolchains; routine in CI.
-
info
warn→ info by reviewdynamic-executiondeps/xxhash/.github/workflows/ci.yml:437:17new in this release&& && && &&likely benign CI step printing cross-compiler version and specs via $XCC.Reasoning
Routine version/spec output for the cross-compiler variable $XCC in a CI job.
-
info
warn→ info by reviewdynamic-executiondeps/xxhash/.github/workflows/ci.yml:439:17new in this release&& &&likely benign CI step checking the emulator binary configured via $XEMU.Reasoning
Routine emulator presence/version check using $XEMU in a cross-compilation CI job.
-
info
warn→ info by reviewobfuscated-command-namedeps/xxhash/.github/workflows/ci.yml:544:9new in this releaselikely benign Runs the freshly built Windows xxhsum.exe benchmark via a backslash path.Reasoning
Backslashes are Windows path separators in a PowerShell/cmd invocation of the locally built xxhsum.exe; not obfuscation.
-
info
warn→ info by reviewobfuscated-command-namedeps/xxhash/.github/workflows/ci.yml:559:9new in this releaselikely benign Runs the clang-cl built xxhsum.exe with Windows path separators.Reasoning
Windows path separators to a locally built binary in a CI benchmark step; benign.
-
info
warn→ info by reviewobfuscated-command-namedeps/xxhash/.github/workflows/ci.yml:575:9new in this release|likely benign Runs the dispatch-built xxhsum.exe from a Windows build directory.Reasoning
Windows backslash paths to the locally built dispatch binary in CI; the flagged signal is a false positive from path syntax.
-
info
warn→ info by reviewobfuscated-command-namedeps/xxhash/.github/workflows/ci.yml:576:9new in this release|likely benign Runs the dispatch-built xxhsum.exe from a Windows build directory.Reasoning
Duplicate of the adjacent step with the same Windows path syntax; benign.
-
info
critical→ info by reviewdynamic-executiondeps/xxhash/.github/workflows/ci.yml:619:51new in this release# Expected output is "./xxhsum.exe: PE32+ executable (console) x86-64, for MS Windows" | ||likely benign Verifies the built xxhsum.exe architecture with file and fails via a no-op substitution.Reasoning
Uses $(exit 1) as an inert failure fallback after a file-type check on the built binary; the file command verifies architecture. No malicious payload.
-
info
critical→ info by reviewdynamic-executiondeps/xxhash/.github/workflows/ci.yml:629:50new in this release# Expected output is "./xxhsum.exe: PE32 executable (console) Intel 80386, for MS Windows" | ||likely benign Verifies the 32-bit xxhsum.exe architecture with file and fails via a no-op substitution.Reasoning
Same architecture-check pattern for the 32-bit Windows binary; benign CI verification.
-
-
-
-
-
-
-
-
-
|| /* WASM SIMD128 via SIMDe */likely benign Temporarily redefines inline to __inline__ while including arm_neon.h to work around a clang bug.Reasoning
Temporary #define inline around an arm_neon.h include is a known workaround for a clang bug, immediately undone with #undef. Not malicious, though it is a legitimate macro-keyword override.
-
;likely benign Vendored xxHash C header with local variables bitflip1 and bitflip2 whose names trigger a visual-confusability heuristic.Reasoning
The skeleton collision comes from ordinary local names like bitflip1 and bitflip2 in the vendored, well-known xxHash header. The confusable-name heuristic fires on a digit-versus-letter lookalike in normal arithmetic code, and the snippet shows no obfuscation or malicious behaviour. This is a token-pass finding, which has a higher false-positive rate.
-
= =likely benign setup.py executes the package's own xxhash/version.py to read the VERSION string during build.Reasoning
setup.py reads xxhash/version.py from the project's own source tree and executes it into a dict to extract VERSION, a common single-source version pattern. The exec runs only when setup.py is executed for build or install, not at import time of the package. The source is a local project file, not a remote or encoded payload, so the non-literal argument is not by itself malicious. Residual doubt remains because the flagged exec is at module scope in a build script.
Reproduce This Scan
Run disclude locally to verify. These commands scan the published file; the "new in this release" marks come from comparing it with the previous release's file, which they don't repeat. Add --format sarif for SARIF output. Add --llm (with an API key in the environment) to include the LLM review.
|
&&