npm / mime-db / 1.54.0

mime-db 1.54.0

Source

https://github.com/jshttp/mime-db

Tag scanned

v1.54.0

Compared with

v1.53.0 (0 signals introduced since)

Files

13 scanned, 7 skipped (binary, oversized, or unrecognised)

Signals

0 critical · 0 warn · 1 info

Scan time

3.0 s

LLM review

Reviewed by claude-haiku-5-5 (Anthropic): 1 of 1 warn and critical signal; 1 demoted to info.

Disclude version

4.1.0

Scanned (UTC)

2026-10-22 12: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 test/index.js:17:43

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

         if (!/-types\.json$/.test(file)) return
         types.push.apply(types, Object.keys(require(path + '/' + file)))
       })

   likely benign LLM, confidence 0.85 A test file loads every *-types.json file from a directory with a dynamically built require path and collects their keys.

   Reasoning

   The require call builds its path from a directory listing and only loads files whose names end in -types.json, then reads their keys into an array. This is a common test-fixture pattern for loading JSON data files. It is a dynamic specifier, but the snippet shows no decoding, network access, or code execution, and the file is in a test directory. Nothing points to 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.1.0
git clone https://github.com/jshttp/mime-db mime-db && cd mime-db
git checkout v1.54.0
disclude scan --severity info --diff v1.53.0 .