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 1
Legitimate module resolution
NPS-754FA0D7F87F
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
| File | Verdict | What the reviewer saw |
|---|---|---|
| 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 |
Affected 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.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 2.0.0-next.7 | No issues | 1 | 2.0.0-next.7 | |
| 1.22.12 – 2.0.0-next.5 | Not scanned | 2 | >=1.22.12 <=2.0.0-next.5 | |
| 1.22.11 | No issues | 1 | 1.22.11 | |
| 1.7.1 – 1.22.10 | Not scanned | 2 | >=1.7.1 <=1.22.10 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of resolve
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 1.22.11 | No issues | 13 | Oct 6, 2026 |
| 2.0.0-next.7 | No issues | 17 | Oct 6, 2026 |
Frequently asked questions
Is resolve safe to use?
Our AI source review of resolve@1.22.11 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does resolve contain malware?
No malware was identified in resolve@1.22.11 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 resolve checked?
Togoder Security downloaded the published npm package and had an AI model read its 13 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 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 resolve@1.22.11, cost nothing.