npm / globals / 17.13.0

globals 17.13.0

Source

https://github.com/sindresorhus/globals

Tag scanned

v17.13.0

Compared with

v17.12.0 (0 signals introduced since)

Files

87 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.0.0

Scanned (UTC)

2026-10-14 19:16

Signals

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

1. info warn → info by review dynamic-import utilities.mjs:10:28

   dynamic `import(...)` with a non-literal specifier (ast pass, confidence 0.65)

   	try {
   		({default: data} = await import(file));
   	} catch (error) {
   		if (ignoreNonExits && error.code === 'ERR_MODULE_NOT_FOUND') {

   likely benign LLM, confidence 0.80 A utility loads a module from a variable path via dynamic import and tolerates missing-module errors.

   Reasoning

   The snippet shows a dynamic import with a variable specifier, wrapped in try/catch that specifically handles ERR_MODULE_NOT_FOUND. This is a common pattern in loader utilities that import user-supplied or discovered module files, and the error handling indicates a tolerant file-loading helper rather than hidden execution. The non-literal specifier is the only concern; the surrounding code shows no obfuscation or encoded payload. Without seeing where file comes from, arbitrary-path import is a plausible risk, but the pattern itself is benign.

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/sindresorhus/globals globals && cd globals
git checkout v17.13.0
disclude scan --severity info --diff v17.12.0 .