npm / fast-json-stable-stringify / 2.1.0

fast-json-stable-stringify 2.1.0

Source: https://github.com/epoberezkin/fast-json-stable-stringify
Tag scanned: v2.1.0
Compared with: v2.0.0 (0 signals introduced since)
Files: 13 scanned, 2 skipped (binary, oversized, or unrecognised)
Signals: 0 critical · 0 warn · 1 info
Scan time: 2.5 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 20:07

Signals

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

info ~~warn~~ → info by review dynamic-import benchmark/index.js:19:29

`require` called with a non-literal specifier (ast pass, confidence 0.60)
```
  let func = stringifyPackages[name];
  if (func === true) func = require(name);

  suite.add(name, function() {
```
likely benign LLM, confidence 0.90 A benchmark runner dynamically requires a known list of stringify packages by name.
Reasoning
The require call takes a variable name, but the surrounding code is a benchmark harness that iterates over a fixed set of stringify packages defined in the same file and requires them by name for comparison. This is a common, benign pattern in benchmark suites with no network, shell, or encoded payload involvement.

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/epoberezkin/fast-json-stable-stringify fast-json-stable-stringify && cd fast-json-stable-stringify
git checkout v2.1.0
disclude scan --severity info --diff v2.0.0 .