Togoder security

npm package security report

npm-run-path@6.0.0 security report

No malicious code found.

No issues Version 6.0.0 Files reviewed 1 Size 1.4 KB Scanned

Summary

Togoder Security scanned the npm package npm-run-path@6.0.0 on Oct 6, 2026. An AI review of 1 source file produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.

0
critical
0
high
0
medium
0
low

Findings

No findings. The reviewer saw nothing malicious or risky in this version.

Files reviewed

FileVerdictWhat the reviewer saw
index.js safe The code is a legitimate utility for constructing PATH environment variables for npm scripts, with no malicious patterns, network activity, credential harvesting, or command execution.

Affected version ranges

None of the 2 scanned versions of npm-run-path are flagged high or critical. The latest scanned version, 6.0.0, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.

2.0.26.0.0
VersionsVerdictCountRangeTop findings
5.3.0 – 6.0.0 No issues 2 >=5.3.0 <=6.0.0
2.0.2 – 4.0.1 Not scanned 2 >=2.0.2 <=4.0.1

Full list, including published versions not scanned yet: version ranges API.

Scanned versions of npm-run-path

VersionVerdictFilesScanned
6.0.0 No issues 1 Oct 6, 2026
5.3.0 No issues 1 Oct 6, 2026

Frequently asked questions

Is npm-run-path safe to use?

Our AI source review of npm-run-path@6.0.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.

Does npm-run-path contain malware?

No malware was identified in npm-run-path@6.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 npm-run-path checked?

Togoder Security downloaded the published npm package and had an AI model read its 1 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 npm-run-path 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 npm-run-path@6.0.0, cost nothing.

Related security reports