# import-meta-resolve@4.2.0 security report (npm)

- Verdict: **No issues** (risk level: safe)
- Scanned: 2026-10-06T14:16:56.000Z
- Files reviewed: 6
- Findings: 1 low severity finding
- Report: https://security.togoder.click/npm/import-meta-resolve
- Source: Togoder Security (https://security.togoder.click), AI source-code review

## 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

### [low] filesystem_read

Finding ID: `NPS-07D12F8B9AE3`

File: `lib/package-json-reader.js:52`

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

- `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

AI analysis is guidance, not a guarantee. Methodology: https://security.togoder.click/methodology