npm / baseline-browser-mapping / 2.11.29

baseline-browser-mapping 2.11.29

Source: https://github.com/web-platform-dx/baseline-browser-mapping
Tag scanned: v2.11.29
Compared with: v2.11.28 (0 signals introduced since)
Files: 23 scanned, 16 skipped (binary, oversized, or unrecognised)
Signals: 0 critical · 0 warn · 1 info
Scan time: 1.9 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-16 09:25

Signals

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

info ~~warn~~ → info by review dynamic-import spec/legacy-tests/legacy-test.cjs:7:13

`require` called with a non-literal specifier (ast pass, confidence 0.60)
```
  var lib = require(distPath);
  var getCompatibleVersions = lib.getCompatibleVersions;
```
likely benign LLM, confidence 0.85 A legacy test file requires a built library from a computed distPath variable.
Reasoning
The require uses a variable path, which is a dynamic-import signal, but the file is a legacy test in a spec directory loading a local dist build via a computed path. This is a common test-harness pattern, with no encoding, shell execution, or network activity visible in the snippet. Benign-looking, though the distPath origin 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.

cargo install disclude --version 4.0.0
git clone https://github.com/web-platform-dx/baseline-browser-mapping baseline-browser-mapping && cd baseline-browser-mapping
git checkout v2.11.29
disclude scan --severity info --diff v2.11.28 .