Summary
Togoder Security scanned the npm package cmdk@0.2.1 on Oct 6, 2026. An AI review of 5 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/chunk-XJATAMEX.mjs | safe | No malicious patterns detected; the code is a fuzzy string matching algorithm with no network, filesystem, process, or dynamic execution capabilities. |
| dist/command-score.js | safe | No malicious patterns detected; the code is a minified fuzzy string matching library with no network, filesystem, process, or credential access. |
| dist/command-score.mjs | safe | The file only re-exports a named binding from a local chunk module; no malicious patterns detected. |
| dist/index.js | safe | No malicious patterns detected; the code is the well-known 'cmdk' React command menu library with no data exfiltration, credential harvesting, obfuscated payloads, network calls, process spawning, or install-time scripts. |
| dist/index.mjs | safe | No malicious patterns detected; the code is a standard UI component library (cmdk) with only benign dependencies and no data exfiltration, credential harvesting, or execution of untrusted code. |
Scanned versions of cmdk
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 0.2.1 | No issues | 5 | Oct 6, 2026 |
Frequently asked questions
Is cmdk safe to use?
Our AI source review of cmdk@0.2.1 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does cmdk contain malware?
No malware was identified in cmdk@0.2.1 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 cmdk checked?
Togoder Security downloaded the published npm package and had an AI model read its 5 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 cmdk 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 cmdk@0.2.1, cost nothing.