Summary
Togoder Security scanned the npm package which-command@0.1.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 |
|---|---|---|
| cli.js | safe | No malicious patterns detected; the CLI tool only parses arguments, reads its own package.json for version info, and delegates command lookup to local helper functions without any exfiltration, obfuscation, or process spawning. |
| index.js | safe | No malicious patterns detected; the code is a legitimate cross-platform 'which' command implementation using only filesystem checks and environment variables. |
Scanned versions of which-command
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 0.1.0 | No issues | 2 | Oct 6, 2026 |
Frequently asked questions
Is which-command safe to use?
Our AI source review of which-command@0.1.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does which-command contain malware?
No malware was identified in which-command@0.1.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 which-command 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 which-command 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 which-command@0.1.0, cost nothing.