# resolve@1.22.11 security report (npm)

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

## Summary

Togoder Security scanned the npm package resolve@1.22.11 on Oct 6, 2026. An AI review of 13 source files produced 1 low severity finding. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.

## Findings

### [low] Legitimate module resolution

Finding ID: `NPS-754FA0D7F87F`

File: `lib/sync.js`

This file is a reimplementation of Node's CommonJS module resolution algorithm (resolve.sync). It reads package.json files, resolves paths, checks file/directory existence, and applies user-supplied options. It performs no network requests, no process spawning, no environment variable harvesting of credentials, no dynamic code execution, and no file writes. Reference to homedir is only used for legacy .node_modules and .node_libraries fallback paths, which is standard legacy Node behavior in the resolve package.

## Files reviewed

- `async.js` (safe): Cleared by Jev triage; no further analysis needed
- `example/async.js` (safe): No malicious patterns detected; the example simply calls a local resolve function and logs output.
- `example/sync.js` (safe): No malicious patterns detected
- `index.js` (safe): Cleared by Jev triage; no further analysis needed
- `lib/async.js` (safe): No malicious patterns detected; this is a standard Node.js module resolution library (resolve) with no exfiltration, credential harvesting, obfuscation, or shell execution.
- `lib/caller.js` (safe): No malicious patterns detected
- `lib/core.js` (safe): No malicious patterns detected
- `lib/homedir.js` (safe): The code is a standard implementation for determining the user's home directory and contains no malicious patterns.
- `lib/is-core.js` (safe): No malicious patterns detected
- `lib/node-modules-paths.js` (safe): The code is a legitimate utility for resolving node_modules paths and contains no malicious patterns such as data exfiltration, credential harvesting, obfuscation, or process spawning.
- `lib/normalize-options.js` (safe): Cleared by Jev triage; no further analysis needed
- `lib/sync.js` (safe): Code is a legitimate implementation of Node module resolution with no malicious patterns detected.
- `sync.js` (safe): Cleared by Jev triage; no further analysis needed

## Version ranges

None of the 2 scanned versions of resolve are flagged high or critical. The latest scanned version, 1.22.12, is not scanned. Only versions we have scanned are listed; unscanned versions between them are not covered.

- 2.0.0-next.7 (`2.0.0-next.7`): clean
- 1.22.12 – 2.0.0-next.5 (`>=1.22.12 <=2.0.0-next.5`): not scanned
- 1.22.11 (`1.22.11`): clean
- 1.7.1 – 1.22.10 (`>=1.7.1 <=1.22.10`): not scanned

## Scanned versions

- [1.22.11](https://security.togoder.click/npm/resolve@1.22.11): safe, 2026-10-06T14:24:20.000Z
- [2.0.0-next.7](https://security.togoder.click/npm/resolve@2.0.0-next.7): safe, 2026-10-06T14:16:28.000Z

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