Summary
Togoder Security scanned the npm package resolve@2.0.0-next.7 on Oct 6, 2026. An AI review of 17 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings
No findings. The reviewer saw nothing malicious or risky in this version.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| async.js | safe | Cleared by Jev triage; no further analysis needed |
| eslint.config.mjs | 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 |
| index.mjs | safe | Cleared by Jev triage; no further analysis needed |
| lib/async.js | safe | This is a legitimate Node.js module resolution implementation (resolve/async.js) with no malicious patterns such as data exfiltration, credential harvesting, obfuscation, backdoors, or process spawning. |
| lib/caller.js | safe | No malicious patterns detected; the code is a standard utility for capturing the caller's filename via stack traces. |
| lib/exports-resolve.js | safe | No malicious patterns detected; the code is a legitimate implementation of Node.js package exports resolution with proper path traversal validation. |
| lib/get-exports-category.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/homedir.js | safe | No malicious patterns detected; the code is a standard, safe homedir fallback implementation that only reads environment variables for path resolution. |
| lib/node-modules-paths.js | safe | No malicious patterns detected; the code only computes node_modules directory paths using standard path operations and optional caller-provided hooks. |
| lib/normalize-options.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/parse-package-specifier.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/select-most-restrictive.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/sync.js | safe | No malicious patterns detected; the code is a standard synchronous module resolver similar to resolve package, with no network, credential, obfuscation, or process execution concerns. |
| 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@2.0.0-next.7 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@2.0.0-next.7 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 17 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@2.0.0-next.7, cost nothing.