minipass 7.1.3

Source: https://github.com/isaacs/minipass
Tag scanned: v7.1.3
Compared with: v7.1.2 (0 signals introduced since)
Files: 59 scanned, 160 skipped (binary, oversized, or unrecognised)
Signals: 0 critical · 0 warn · 1 info
Scan time: 2.3 s
LLM review: Reviewed by claude-haiku-5-5 (Anthropic): 1 of 1 warn and critical signal; 1 demoted to info.
Disclude version: 4.1.0
Scanned (UTC): 2026-10-22 13:42

Signals

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

info ~~warn~~ → info by review dynamic-import bench/index.js:152:15

`require` called with a non-literal specifier (ast pass, confidence 0.80)
```
const setupPipeline = (impl, len, cse, opt) => {
  const Cls = require(`./impls/${impl}.js`)
  let s = new Cls(opt)
  let start = s
```
likely benign LLM, confidence 0.85 Benchmark runner dynamically requires a local implementation module chosen by name.
Reasoning
The require uses a template literal over an impl name from a benchmark harness, loading a local ./impls/*.js module. In a bench directory this is a plausible plugin-loading pattern, with no network, shell, or decode behavior visible. The risk is only that impl could be attacker-controlled, but within a benchmark runner it is almost certainly a fixed set of local implementations.

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.1.0
git clone https://github.com/isaacs/minipass minipass && cd minipass
git checkout v7.1.3
disclude scan --severity info --diff v7.1.2 .