# resolve@2.0.0-next.7 security report (npm)

- Verdict: **No issues** (risk level: safe)
- Scanned: 2026-10-06T14:16:28.000Z
- Files reviewed: 17
- Findings: no findings
- Report: https://security.togoder.click/npm/resolve@2.0.0-next.7
- Source: Togoder Security (https://security.togoder.click), AI source-code review

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

## Files reviewed

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

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