Summary
Togoder Security scanned the npm package @img/sharp-linuxmusl-x64@0.35.5 on Oct 6, 2026. An AI review of 1 source file produced 1 low severity finding. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings 1
Native module loading
NPS-B67E063201DB
The code attempts to resolve an optional binary package and loads a native .node addon. This is standard for platform-specific native bindings (like sharp/libvips) and does not indicate malicious behavior.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| index.cjs | safe | Standard platform-specific native module loader with no malicious patterns detected. |
Scanned versions of @img/sharp-linuxmusl-x64
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 0.35.5 | No issues | 1 | Oct 6, 2026 |
Frequently asked questions
Is @img/sharp-linuxmusl-x64 safe to use?
Our AI source review of @img/sharp-linuxmusl-x64@0.35.5 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @img/sharp-linuxmusl-x64 contain malware?
No malware was identified in @img/sharp-linuxmusl-x64@0.35.5 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 @img/sharp-linuxmusl-x64 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 @img/sharp-linuxmusl-x64 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 @img/sharp-linuxmusl-x64@0.35.5, cost nothing.