crates.io / crc32fast / 1.5.2

crc32fast 1.5.2

Source

https://github.com/srijs/rust-crc32fast

Tag scanned

v1.5.2

Compared with

v1.5.1 (0 signals introduced since)

Files

13 scanned, 4 skipped (binary, oversized, or unrecognised)

Signals

0 critical · 0 warn · 1 info

Scan time

2.0 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:19

Signals

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

1. info warn → info by review encoding-escape-soup src/baseline.rs:103:44

   32 consecutive `\xNN` escapes (entropy 5.0 bits/byte) (raw pass, confidence 0.80)

           assert_eq!(super::update_slow(0, b"\x00\x01\x02\x03\x04\x05\x06\x07\x08\x09\x0A\x0B\x0C\x0D\x0E\x0F\x10\x11\x12\x13\x14\x15\x16\x17\x18\x19\x1A\x1B\x1C\x1D\x1E\x1F"), 0x91267E8A);
       }

   dismissed LLM, confidence 0.95 A unit test in a Rust checksum module uses a sequential byte-string test vector (0x00 to 0x1F) to verify update_slow against an expected hash value.

   Reasoning

   The finding is a raw-pass escape-soup match on a Rust unit test. The byte string is the sequential sequence \x00 through \x1F, a classic test vector for a checksum/CRC update function, and it is asserted against a known expected constant (0x91267E8A). This is a legitimate test fixture, not an obfuscated payload or dropper. Raw-pass findings have a high false-positive rate, and this one is clearly benign.

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/srijs/rust-crc32fast rust-crc32fast && cd rust-crc32fast
git checkout v1.5.2
disclude scan --severity info --diff v1.5.1 .