Summary
Togoder Security scanned the npm package import-meta-resolve@4.2.0 on Oct 6, 2026. An AI review of 6 source files produced 1 low severity finding. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings 1
filesystem_read
NPS-07D12F8B9AE3
The code reads package.json files from the filesystem via fs.readFileSync to determine package type and metadata. This is expected behavior for a package.json reader utility and is limited to locating and parsing package.json files in the module resolution path, not arbitrary or sensitive files.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| index.js | safe | No malicious patterns detected; the code is a straightforward ES module resolver with no network, filesystem, process, or obfuscation concerns. |
| lib/errors.js | safe | No malicious patterns detected |
| lib/get-format.js | safe | The code is a legitimate implementation of Node.js module format detection with no malicious patterns such as data exfiltration, credential harvesting, dynamic code execution, or backdoor installation. |
| lib/package-json-reader.js | safe | The file is a legitimate tree-shaken extraction of Node.js's internal package_json_reader module with no malicious patterns, only expected filesystem reads of package.json for module resolution. |
| lib/resolve.js | safe | This is a legitimate tree-shaken copy of Node.js's internal ESM module resolution logic with no malicious patterns detected. |
| lib/utils.js | safe | Cleared by Jev triage; no further analysis needed |
Scanned versions of import-meta-resolve
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 4.2.0 | No issues | 6 | Oct 6, 2026 |
Frequently asked questions
Is import-meta-resolve safe to use?
Our AI source review of import-meta-resolve@4.2.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does import-meta-resolve contain malware?
No malware was identified in import-meta-resolve@4.2.0 when Togoder Security scanned it on Oct 6, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was import-meta-resolve checked?
Togoder Security downloaded the published npm package and had an AI model read its 6 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.
How do I scan import-meta-resolve together with the rest of my dependencies?
Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in import-meta-resolve@4.2.0, cost nothing.