Summary
Togoder Security scanned the npm package resolve-pkg-maps@1.0.0 on Oct 6, 2026. An AI review of 2 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 |
|---|---|---|
| dist/index.cjs | safe | The analyzed code implements Node.js package exports/imports resolution logic with no malicious patterns such as data exfiltration, credential harvesting, obfuscated payloads, dynamic code execution, or process spawning. |
| dist/index.mjs | safe | This file is a minified implementation of Node.js package exports/imports resolution logic with no malicious patterns, network activity, or system-level access. |
Frequently asked questions
Is resolve-pkg-maps safe to use?
Our AI source review of resolve-pkg-maps@1.0.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does resolve-pkg-maps contain malware?
No malware was identified in resolve-pkg-maps@1.0.0 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-pkg-maps checked?
Togoder Security downloaded the published npm package and had an AI model read its 2 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-pkg-maps 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-pkg-maps@1.0.0, cost nothing.