chokidar 6.0.0

Source: https://github.com/paulmillr/chokidar
Tag scanned: 6.0.0
Compared with: 5.0.0 (1 signals introduced since)
Files: 17 scanned, 3 skipped (binary, oversized, or unrecognised)
Signals: 0 critical · 0 warn · 1 info
Scan time: 2.7 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 15:57

Signals

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

info ~~warn~~ → info by review dynamic-import benchmark/bench.mjs:215:26 new in this release

dynamic `import(...)` with a non-literal specifier (ast pass, confidence 0.65)
```
  await resetRuntimePaths(root);
  const chokidar = await import(CHOKIDAR);
  const options = watcherOptions(root, mode, config);
  global.gc?.();
```
likely benign LLM, confidence 0.85 A benchmark script dynamically imports the chokidar watcher library via a constant specifier before running watcher options setup.
Reasoning
The dynamic import specifier CHOKIDAR is a constant that a benchmark script would normally set to a local or installed package path. The surrounding code is ordinary benchmark setup (resetting runtime paths, building watcher options, calling global.gc). Dynamic import of a configurable module is a common legitimate pattern in benchmarks comparing watcher libraries, and nothing here decodes or hides a payload.

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/paulmillr/chokidar chokidar && cd chokidar
git checkout 6.0.0
disclude scan --severity info --diff 5.0.0 .