# @img/sharp-wasm32@0.35.5 security report (npm)

- Verdict: **Needs review** (risk level: medium)
- Scanned: 2026-10-06T14:11:13.000Z
- Files reviewed: 1
- Findings: 1 medium severity finding
- Report: https://security.togoder.click/npm/@img/sharp-wasm32
- Source: Togoder Security (https://security.togoder.click), AI source-code review

## Summary

Togoder Security scanned the npm package @img/sharp-wasm32@0.35.5 on Oct 6, 2026. An AI review of 1 source file produced 1 medium severity finding. The overall verdict is medium: the findings flag risky but common patterns (dynamic code, unsafe defaults, broad file or network access) rather than confirmed malware.

## Findings

### [medium] Native binary loading

Finding ID: `NPS-513BC60AA08C`

File: `index.cjs:1`

The module directly requires a prebuilt native binary ('./lib/sharp-wasm32-0.35.5.node') without any validation, checksum verification, or integrity check. While this is a common pattern for native addons, loading an opaque binary means the actual executed code is not auditable from the JavaScript source. If the .node file were tampered with or fetched from an untrusted source, it could contain arbitrary native code (exfiltration, backdoors, etc.) that bypasses JavaScript-level analysis. The version-suffixed filename (sharp-wasm32-0.35.5.node) is also unusual: 'sharp' is a known image-processing library, but this is a WASM-targeted .node binary rather than the typical platform-specific native addon, which is inconsistent with normal sharp packaging.

## Files reviewed

- `index.cjs` (medium): The file only re-exports a prebuilt native .node binary, which is unauditable at the JS level and warrants verification of the binary's origin and integrity.

AI analysis is guidance, not a guarantee. Methodology: https://security.togoder.click/methodology