npm / graceful-fs / 4.2.11

graceful-fs 4.2.11

Source

https://github.com/isaacs/node-graceful-fs

Tag scanned

v4.2.11

Compared with

v4.2.10 (0 signals introduced since)

Files

25 scanned, 2 skipped (binary, oversized, or unrecognised)

Signals

0 critical · 0 warn · 1 info

Scan time

2.2 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:26

Signals

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

1. info warn → info by review dynamic-import test/close.js:4:11

   `require` called with a non-literal specifier (ast pass, confidence 0.60)

   var gfsPath = path.resolve(__dirname, '..', 'graceful-fs.js')
   var gfs = require(gfsPath)
   var importFresh = require('import-fresh')
   var fs$close = fs.close

   likely benign LLM, confidence 0.93 Test file requires the package's own graceful-fs.js via a path resolved from __dirname.

   Reasoning

   The require call loads a path computed from __dirname and '..' pointing to the package's own graceful-fs.js, a local test helper. This is a standard test pattern for loading the module under test, with no encoding, remote fetch, or obfuscation involved. The non-literal specifier is flagged by the generic rule but is benign here.

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/isaacs/node-graceful-fs node-graceful-fs && cd node-graceful-fs
git checkout v4.2.11
disclude scan --severity info --diff v4.2.10 .