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

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

## Summary

Togoder Security scanned the npm package @img/sharp-linux-arm@0.35.5 on Oct 6, 2026. An AI review of 1 source file produced 1 medium, 2 low severity findings. 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] Dynamic native module loading

Finding ID: `NPS-DF6D13B75D15`

File: `index.cjs:2`

The file loads a platform-specific native binary (sharp-linux-arm-0.35.5.node) at import time. While this is standard for the 'sharp' image processing library's prebuilt binary distribution, loading native modules carries inherent risk because the binary cannot be audited as JavaScript and executes with full process privileges.

### [low] Conditional optional dependency resolution

Finding ID: `NPS-A2235740F0FD`

File: `index.cjs:1`

The try/catch block attempts to resolve '@img/sharp-libvips-linux-arm/binary' but silently swallows any errors. This is a common pattern for optional platform-specific dependencies, but silently ignoring resolution failures can mask tampering or missing dependency issues.

### [low] Top-level code execution at import

Finding ID: `NPS-48C84512760D`

File: `index.cjs:1`

Both the require.resolve call and the native module load execute at import time (top-level code). The native binary is loaded immediately when the module is required, meaning any consumer of this package triggers binary execution without explicit opt-in.

## Files reviewed

- `index.cjs` (medium): This appears to be a standard platform-specific entry point for the 'sharp' image library that loads a native ARM binary at import time; no overt malicious patterns (exfiltration, shell spawning, obfuscation) are present, but native binary loading warrants moderate caution.

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