npm / tslib / 2.8.1

tslib 2.8.1

Source

https://github.com/Microsoft/tslib

Tag scanned

v2.8.1

Compared with

v2.8.0 (0 signals introduced since)

Files

29 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:03

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/runTests.js:25:19

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

   
     const pgkJSON = require(path.join(__dirname, test, "package.json"));
   
     // Allow skipping things which need a minimum of node 14 (es modules)

   likely benign LLM, confidence 0.90 A test runner loads a package.json fixture via require with a path built from __dirname and a test directory name.

   Reasoning

   The require call builds a path from __dirname and a test directory name to load a package.json fixture. This is a common test-runner pattern for reading per-test metadata. The specifier is a local path, not attacker-controlled network content, and the surrounding comment shows ordinary test-harness logic. Flagging it as dynamic-import is a low-risk AST signal with no evidence of malicious intent.

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/Microsoft/tslib tslib && cd tslib
git checkout v2.8.1
disclude scan --severity info --diff v2.8.0 .