npm / brace-expansion / 5.0.12

brace-expansion 5.0.12

Source

https://github.com/juliangruber/brace-expansion

Tag scanned

v5.0.12

Compared with

v5.0.11 (0 signals introduced since)

Files

8 scanned, 4 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 09:42

Signals

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

1. info warn → info by review dynamic-execution test/generate.sh:21:10

   command name is a variable (`$BASH`) not set in this file — the caller or environment decides what runs (ast pass, confidence 0.70)

       fi;
       b="$($BASH -c 'for c in '"$case"'; do echo ["$c"]; done')"
       echo "$case"
       echo -n "$b><><><><";

   likely benign LLM, confidence 0.90 A test-generation script runs the current bash binary via the BASH variable to compute expansion outputs.

   Reasoning

   The flagged command is $BASH, the shell's own built-in variable pointing to the currently running bash binary, used to run a small brace/glob expansion test generator. This is a standard idiom in shell test scripts and not an attacker-controlled command. The finding fires only because the variable is not set in the file, which is normal for BASH.

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/juliangruber/brace-expansion brace-expansion && cd brace-expansion
git checkout v5.0.12
disclude scan --severity info --diff v5.0.11 .