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.4 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 19:22
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
constlikely benign A benchmark script dynamically requires a local implementation module chosen by name from ./impls/.Reasoning
The file is a benchmark harness. The require uses a template literal with an impl name to load one of several local implementation modules under ./impls/. This is a common plugin/benchmark pattern. The specifier is not attacker-controlled input in a normal run, and the snippet shows no network, encoding, or shell activity. Only a dynamic-require warning remains, so this is most likely benign, though the specifier's source is not shown.
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.
&&