Summary
Togoder Security scanned the npm package @sindresorhus/is@4.6.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.js | safe | The code is a legitimate type-checking library with no malicious patterns, network activity, or dynamic code execution. |
| dist/types.js | safe | No malicious patterns detected in the provided file. |
Scanned versions of @sindresorhus/is
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 4.6.0 | No issues | 2 | Oct 6, 2026 |
Frequently asked questions
Is @sindresorhus/is safe to use?
Our AI source review of @sindresorhus/is@4.6.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @sindresorhus/is contain malware?
No malware was identified in @sindresorhus/is@4.6.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 @sindresorhus/is 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 @sindresorhus/is 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 @sindresorhus/is@4.6.0, cost nothing.